From owner-freebsd-current Sun Oct 29 01:15:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA08106 for current-outgoing; Sun, 29 Oct 1995 01:15:12 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA08075 for ; Sun, 29 Oct 1995 01:15:01 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id BAA00244; Sun, 29 Oct 1995 01:14:56 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id BAA03454; Sun, 29 Oct 1995 01:14:19 -0800 Message-Id: <199510290914.BAA03454@corbin.Root.COM> To: uhclem%nemesis@fw.ast.com (Frank Durda IV) cc: current@freebsd.org Subject: Re: Support for WD8003E abandoned? In-reply-to: Your message of "Sat, 28 Oct 95 17:04:00 +0700." From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 29 Oct 1995 01:14:19 -0800 Sender: owner-current@freebsd.org Precedence: bulk >I have a site that has been trying to install 2.0.5, toying >with a migration from Linux. However, the WD8003E card he has >is not detected under FreeBSD, despite carefully setting all >the parameters in UserConfig. > >I plan to visit the site today, but since this guy installs hardware >for ISPs, I think he knows what he is doing. > > >I tried the same thing on 2.1.0-951026-SNAP on three WD8003EB boards >I have around here. They are all detected, but none work! I'm surprised to hear this, but it has been a long time since I specifically tested 8bit wd8003e's. Still, I can't think of any changes to the driver that could have broken this. It sounds like an interrupt conflict with another card - the driver doesn't even initialize the irq for those cards since they don't have soft configuration - the irq is hard strapped on the card. ...So I'm at a loss to understand how it could be missing the interrupt. I suppose that problem could be elsewhere in the driver, however... -DG From owner-freebsd-current Sun Oct 29 03:57:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA16121 for current-outgoing; Sun, 29 Oct 1995 03:57:11 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id DAA16115 ; Sun, 29 Oct 1995 03:57:06 -0800 Received: by sovcom.kiae.su id AA11857 (5.65.kiae-1 ); Sun, 29 Oct 1995 14:55:35 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 29 Oct 95 14:55:35 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id OAA00183; Sun, 29 Oct 1995 14:54:32 +0300 To: current@freebsd.org Cc: David Greenman Message-Id: Organization: Olahm Ha-Yetzirah Date: Sun, 29 Oct 1995 14:54:32 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: stable general protection fault in last kernel Lines: 24 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 631 Sender: owner-current@freebsd.org Precedence: bulk Building from today's sources I can easily got Fatal trap 9: GPF while in kernel mode immideately by simple call /usr/sbin/mixer (I have PAS16 and soundriver enabled). Stack trace says: _trap_msg(...) _vn_ioctl(...) _ioctl(...) _syscall(...) It seems that vn_ioctl becomes broken somehow. Kernel builded few days ago works right. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sun Oct 29 04:03:15 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA16773 for current-outgoing; Sun, 29 Oct 1995 04:03:15 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id EAA16760 for ; Sun, 29 Oct 1995 04:03:11 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id EAA00426; Sun, 29 Oct 1995 04:03:04 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id EAA12109; Sun, 29 Oct 1995 04:02:06 -0800 Message-Id: <199510291202.EAA12109@corbin.Root.COM> To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) cc: current@freebsd.org Subject: Re: stable general protection fault in last kernel In-reply-to: Your message of "Sun, 29 Oct 95 14:54:32 +0300." From: David Greenman Reply-To: davidg@Root.COM Date: Sun, 29 Oct 1995 04:02:06 -0800 Sender: owner-current@freebsd.org Precedence: bulk >Building from today's sources I can easily got > >Fatal trap 9: GPF while in kernel mode > >immideately by simple call >/usr/sbin/mixer (I have PAS16 and soundriver enabled). > >Stack trace says: > >_trap_msg(...) >_vn_ioctl(...) >_ioctl(...) >_syscall(...) > > >It seems that vn_ioctl becomes broken somehow. > >Kernel builded few days ago works right. If you are refering to -current and NOT -stable, then it's caused by a bug in the DEVRANDOM changes and was just fixed by Bruce. Otherwise I really have no idea since there haven't been any commits in this area or even related areas. In fact, there have only been two or three commits in the past week and they have nothing to do with this... -DG From owner-freebsd-current Sun Oct 29 04:33:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id EAA18675 for current-outgoing; Sun, 29 Oct 1995 04:33:46 -0800 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id EAA18612 for ; Sun, 29 Oct 1995 04:33:38 -0800 Received: by sequent.kiae.su id AA13180 (5.65.kiae-2 ); Sun, 29 Oct 1995 15:31:08 +0300 Received: by sequent.KIAE.su (UUMAIL/2.0); Sun, 29 Oct 95 15:31:07 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id PAA00211; Sun, 29 Oct 1995 15:25:39 +0300 To: davidg@Root.COM Cc: current@freebsd.org References: <199510291202.EAA12109@corbin.Root.COM> In-Reply-To: <199510291202.EAA12109@corbin.Root.COM>; from David Greenman at Sun, 29 Oct 1995 04:02:06 -0800 Message-Id: Organization: Olahm Ha-Yetzirah Date: Sun, 29 Oct 1995 15:25:39 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: stable general protection fault in last kernel (/dev/null broken) Lines: 27 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1065 Sender: owner-current@freebsd.org Precedence: bulk In message <199510291202.EAA12109@corbin.Root.COM> David Greenman writes: >>Building from today's sources I can easily got >> >>Fatal trap 9: GPF while in kernel mode >> > If you are refering to -current and NOT -stable, then it's caused by a bug >in the DEVRANDOM changes and was just fixed by Bruce. Otherwise I really have >no idea since there haven't been any commits in this area or even related >areas. In fact, there have only been two or three commits in the past week and >they have nothing to do with this... I refer to -current (I mean "stable" bug :-). Original command was: "mixer vol 80 > /dev/null" Moreover, it seems that any output to /dev/null is broken, i.e. sh echo kkk > /dev/null produce the same error. I'll take Bruce's changes, thanx. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sun Oct 29 05:12:51 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA21360 for current-outgoing; Sun, 29 Oct 1995 05:12:51 -0800 Received: from sunny.bog.msu.su (dima@sunny.bog.msu.su [158.250.20.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA21354 for ; Sun, 29 Oct 1995 05:12:42 -0800 Received: (from dima@localhost) by sunny.bog.msu.su (8.6.12/8.6.12) id QAA29991; Sun, 29 Oct 1995 16:12:09 +0300 Date: Sun, 29 Oct 1995 16:12:08 +0300 (????) From: Dmitry Khrustalev To: current@freefall.freebsd.org cc: uhclem%nemesis@fw.ast.com Subject: Re: Support for WD8003E abandoned? In-Reply-To: <199510291203.EAA16789@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk It works for me. WD8003EB or EBT, not sure. -Dima From owner-freebsd-current Sun Oct 29 05:19:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA21662 for current-outgoing; Sun, 29 Oct 1995 05:19:02 -0800 Received: from nanolon.gun.de (nanolon.gun.de [192.109.159.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA21647 ; Sun, 29 Oct 1995 05:18:44 -0800 Received: (from uucp@localhost) by nanolon.gun.de (8.6.8.1/8.6.6) id NAA27340; Sun, 29 Oct 1995 13:42:26 +0100 Received: (from andreas@localhost) by knobel.gun.de (8.6.12/8.6.12) id MAA00781; Sun, 29 Oct 1995 12:57:48 +0100 From: Andreas Klemm Message-Id: <199510291157.MAA00781@knobel.gun.de> Subject: time -l, floating point exeption, division through '0'. trace + FIX ! To: hackers@freebsd.org, current@freebsd.org, jkh@freebsd.org Date: Sun, 29 Oct 1995 12:57:47 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME7] Content-Type: text Content-Length: 4628 Sender: owner-current@freebsd.org Precedence: bulk Hi ! The problem is, that calling '/usr/bin/time -l' often results in a floating point exception, caused by a division through zero (long ticks) ! This works seems to be, that the value computed for ticks is ok here (>=1). knobel# /usr/bin/time -l du 1 ./.tin/.news 1 ./.tin/.save 14 ./.tin 1 ./Mail 1 ./News 1 ./.elm 62 . 0.06 real 0.00 user 0.02 sys 508 maximum resident set size 12 average shared memory size 20 average unshared data size 192 average unshared stack size 96 page reclaims 0 page faults 0 swaps 6 block input operations 0 block output operations 0 messages sent 0 messages received 0 signals received 6 voluntary context switches 5 involuntary context switches But look at the following: knobel# /usr/bin/time -l /bin/ls .cshrc .history .newsrc Mail .elm .klogin .profile News .gopherrc .login .tin xxx .gopherrc~ .ncrecent .xboing-scores xxx.c 0.01 real 0.00 user 0.00 sys 216 maximum resident set size Floating exception (core dumped) Here what happens: Program terminated with signal 8, Floating point exception. #0 0x1af0 in main (argc=1, argv=0xefbfd9f8) at /local/FreeBSD/src-stable/usr.bin/time/time.c:112 112 fprintf(stderr, "%10ld %s\n", (gdb) list 107 108 ticks = hz * (ru.ru_utime.tv_sec + ru.ru_stime.tv_sec) + 109 hz * (ru.ru_utime.tv_usec + ru.ru_stime.tv_usec) / 1000000; 110 fprintf(stderr, "%10ld %s\n", 111 ru.ru_maxrss, "maximum resident set size"); 112 fprintf(stderr, "%10ld %s\n", 113 ru.ru_ixrss / ticks, "average shared memory size"); 114 fprintf(stderr, "%10ld %s\n", 115 ru.ru_idrss / ticks, "average unshared data size"); 116 fprintf(stderr, "%10ld %s\n", (gdb) r -l /bin/ls Starting program: /usr/bin/time -l /bin/ls .cshrc .history .newsrc Mail xxx.c .elm .klogin .profile News .gopherrc .login .tin time.core .gopherrc~ .ncrecent .xboing-scores xxx 0.02 real 0.00 user 0.00 sys 0 maximum resident set size Program received signal SIGFPE, Arithmetic exception. 0x1af0 in main (argc=1, argv=0xefbfd9f8) at /local/FreeBSD/src-stable/usr.bin/time/time.c:112 112 fprintf(stderr, "%10ld %s\n", (gdb) display ru.ru_ixrss, ticks 1: ru.ru_ixrss, ticks = 0 (gdb) display ru.ru_ixrss 2: ru.ru_ixrss = 0 (gdb) display ticks 3: ticks = 0 When ticks is equal to zero, then the program dumps core.... ticks (long) will be computed as follows: ticks = hz * (ru.ru_utime.tv_sec + ru.ru_stime.tv_sec) + hz * (ru.ru_utime.tv_usec + ru.ru_stime.tv_usec) / 1000000; ticks = 100 * ( 0 + 0 ) + 100 * ( 0 + 7415 ) / 1000000; In this case ticks would be 0.74, but because of long ticks -> 0. A simple hack would be, to force ticks to be at least '1'. This could be done by simply adding '1'.... What do you think ????? *** time.c.orig Fri May 27 14:32:52 1994 --- time.c Sun Oct 29 12:50:26 1995 *************** *** 105,112 **** int hz = 100; /* XXX */ long ticks; ! ticks = hz * (ru.ru_utime.tv_sec + ru.ru_stime.tv_sec) + ! hz * (ru.ru_utime.tv_usec + ru.ru_stime.tv_usec) / 1000000; fprintf(stderr, "%10ld %s\n", ru.ru_maxrss, "maximum resident set size"); fprintf(stderr, "%10ld %s\n", --- 105,113 ---- int hz = 100; /* XXX */ long ticks; ! ticks = hz * (ru.ru_utime.tv_sec + ru.ru_stime.tv_sec) ! + hz * (ru.ru_utime.tv_usec + ru.ru_stime.tv_usec) ! / 1000000 + 1; /* XXX avoid division through zero */ fprintf(stderr, "%10ld %s\n", ru.ru_maxrss, "maximum resident set size"); fprintf(stderr, "%10ld %s\n", -- $$ apsfilter - magic print filter 4lpd @home : andreas@knobel.gun.de $$ ftp://sunsite.unc.edu @work : andreas@sunny.wup.de $$ /pub/Linux/system/Printing/aps-491.tgz knobel: >>> powered by FreeBSD <<< From owner-freebsd-current Sun Oct 29 05:21:59 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA21819 for current-outgoing; Sun, 29 Oct 1995 05:21:59 -0800 Received: from nanolon.gun.de (nanolon.gun.de [192.109.159.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA21806 ; Sun, 29 Oct 1995 05:21:45 -0800 Received: (from uucp@localhost) by nanolon.gun.de (8.6.8.1/8.6.6) id NAA27361; Sun, 29 Oct 1995 13:42:30 +0100 Received: from knobel.gun.de (localhost [127.0.0.1]) by knobel.gun.de (8.6.12/8.6.12) with SMTP id VAA03343; Sat, 28 Oct 1995 21:06:00 +0100 Date: Sat, 28 Oct 1995 21:06:00 +0100 (MET) From: Andreas Klemm To: hackers@freebsd.org, current@freebsd.org cc: jkh@freebsd.org, rb@gtn.com, mg@gtn.com, mlc@wup.de Subject: several diffs for dump(8) to display write throughput and such...c Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk Hi ! The dump utility in Solaris 2.4 has the nice feature, to show the write throughput, when dumping to tape. I missed this one in FreeBSD's dump utility. Therefore I added this feature and am really satisfied with the result ;-) Look this dump using a 5GB Sun DAT (Archive Python with data compression): DUMP: Date of this level 0 dump: Sat Oct 28 20:28:29 1995 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rsd0s3d (/local) to /dev/nrst0 DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 687051 tape blocks on 0.14 tape(s). DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 18.62% done, finished in 0:21 DUMP: 40.41% done, finished in 0:14 DUMP: 63.04% done, finished in 0:08 DUMP: 83.35% done, finished in 0:03 DUMP: DUMP: 688558 tape blocks on 1 volumes(s) >>DUMP: DUMP: finished in 1451 seconds, throughput 474 KBytes/sec DUMP: level 0 dump on Sat Oct 28 20:28:29 1995 DUMP: Closing /dev/nrst0 DUMP: DUMP IS DONE I hope you like this feature, too. Please, could someone apply these diffs to FreeBSD-current and FreeBSD-stable (2.1) if you should agree with me, that it's worth to add these changes ?! Some other things that I changed in the hope, it's useful to everybody: o changed the default tape from /dev/rmt8 to /dev/nrst0 Since rmt8 doesn't exist anymore and /dev/nrst0 is the first tape device. I choosed the no rewind device, since it's the default in nowadays, to write multiple volumes to one large DAT or Tape or whatelse. And updated the manpage o changed the example in the manpage. Choosed /dev/nrst0 instead of /dev/nrst1. Not important, but why not use the first SCSI tape drive ? I think most people only have one main backup device... o added a note in the manpage, that the blocksize has to be equal or less 32 Kbyte (b option). Using values over 32 is ok, too. dump runs without problems, BUT YOU ARE UNABLE TO RESTORE THAT BACKUP, since when using restore, the scsi tape subsystem (st(4)) reports to you the following message, if you try to read a dump with blocksizes over 32K: "st0: 33792-byte record too big" Perhaps dump should report an error directly ?!?! What do you think of this ?! I could add this feature, if you like. BTW, who can tell me the reason for that limitation concerning st(4) ?! I don't understand it. When using Suns dump/restore and ufsdump/ufsrestore commands, then I can use blocksizes up to 96 (recommended from Sun for DAT's) and 128 for Exabytes (if I remember right)... Why only 32K in FreeBSD ??? It's a message from the st(4) driver.... Best regards Andreas /// *** main.c.orig Sat Oct 28 18:53:47 1995 --- main.c Sat Oct 28 20:08:38 1995 *************** *** 440,445 **** --- 440,446 ---- (void)dumpino(dp, ino); } + (void)time((time_t *)&(tend_writing)); /* AKL end time */ spcl.c_type = TS_END; for (i = 0; i < ntrec; i++) writeheader(maxino - 1); *************** *** 448,453 **** --- 449,457 ---- else msg("DUMP: %ld tape blocks on %d volumes(s)\n", spcl.c_tapea, spcl.c_volume); + msg("DUMP: finished in %d seconds, throughput %d KBytes/sec\n", + tend_writing-tstart_writing, + spcl.c_tapea/(tend_writing-tstart_writing)); /* AKL */ putdumptime(); trewind(); broadcast("DUMP IS DONE!\7\7\n"); *** pathnames.h.orig Thu May 26 08:34:04 1994 --- pathnames.h Sat Oct 28 20:08:54 1995 *************** *** 35,41 **** #include ! #define _PATH_DEFTAPE "/dev/rmt8" #define _PATH_DTMP "/etc/dtmp" #define _PATH_DUMPDATES "/etc/dumpdates" #define _PATH_LOCK "/tmp/dumplockXXXXXX" --- 35,41 ---- #include ! #define _PATH_DEFTAPE "/dev/nrst0" /* AKL */ #define _PATH_DTMP "/etc/dtmp" #define _PATH_DUMPDATES "/etc/dumpdates" #define _PATH_LOCK "/tmp/dumplockXXXXXX" *** dump.h.orig Tue May 30 08:08:52 1995 --- dump.h Sat Oct 28 18:57:58 1995 *************** *** 79,84 **** --- 79,85 ---- int blockswritten; /* number of blocks written on current tape */ int tapeno; /* current tape number */ time_t tstart_writing; /* when started writing the first tape block */ + time_t tend_writing; /* after writing the last tape block AKL */ struct fs *sblock; /* the file system super block */ char sblock_buf[MAXBSIZE]; long dev_bsize; /* block size of underlying disk device */ *** dump.8.orig Sat Jul 15 16:46:33 1995 --- dump.8 Sat Oct 28 20:22:30 1995 *************** *** 85,91 **** This option overrides the calculation of tape size based on length and density. .It Cm b Ar blocksize ! The number of kilobytes per dump record. .It Cm h Ar level Honor the user .Dq nodump --- 85,92 ---- This option overrides the calculation of tape size based on length and density. .It Cm b Ar blocksize ! The number of kilobytes per dump record. The maximum value ! is 32. .It Cm h Ar level Honor the user .Dq nodump *************** *** 102,108 **** .Ar file may be a special device file like ! .Pa /dev/rmt12 (a tape drive), .Pa /dev/rsd1c (a disk drive), --- 103,109 ---- .Ar file may be a special device file like ! .Pa /dev/rst0 (a tape drive), .Pa /dev/rsd1c (a disk drive), *************** *** 256,262 **** .It Always start with a level 0 backup, for example: .Bd -literal -offset indent ! /sbin/dump 0uf /dev/nrst1 /usr/src .Ed .Pp This should be done at set intervals, say once a month or once every two months, --- 257,263 ---- .It Always start with a level 0 backup, for example: .Bd -literal -offset indent ! /sbin/dump 0uf /dev/nrst0 /usr/src .Ed .Pp This should be done at set intervals, say once a month or once every two months, *************** *** 282,288 **** rotated out of the dump cycle and fresh tapes brought in. .Sh FILES .Bl -tag -width /etc/dumpdates -compact ! .It Pa /dev/rmt8 default tape unit to dump to .It Pa /etc/dumpdates dump date records --- 283,289 ---- rotated out of the dump cycle and fresh tapes brought in. .Sh FILES .Bl -tag -width /etc/dumpdates -compact ! .It Pa /dev/nrst0 default tape unit to dump to .It Pa /etc/dumpdates dump date records *************** *** 334,336 **** --- 335,346 ---- A .Nm dump command appeared in Version 6 AT&T UNIX. + .Pp + Additional dump message (similar to Solaris 2) + by Andreas Klemm reporting + .Nm backup time + in seconds and + .Nm write performance + in Kbytes per second. Changed default dump device from + the old fashioned rmt8 device to /dev/nrst0. + Appeared first in FreeBSD 2.2. -- $$ apsfilter - magic print filter 4lpd @home : andreas@knobel.gun.de $$ ftp://sunsite.unc.edu @work : andreas@sunny.wup.de $$ /pub/Linux/system/Printing/aps-491.tgz knobel: >>> powered by FreeBSD <<< From owner-freebsd-current Sun Oct 29 06:12:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA23682 for current-outgoing; Sun, 29 Oct 1995 06:12:05 -0800 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id GAA23677 for ; Sun, 29 Oct 1995 06:12:01 -0800 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA28296 (5.65c8/HUTCS-S 1.4 for ); Sun, 29 Oct 1995 16:07:40 +0200 Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id QAA09219; Sun, 29 Oct 1995 16:07:52 +0200 Date: Sun, 29 Oct 1995 16:07:52 +0200 Message-Id: <199510291407.QAA09219@shadows.cs.hut.fi> From: Heikki Suonsivu To: michael butler Cc: freebsd-current@freebsd.org In-Reply-To: michael butler's message of 28 Oct 1995 19:46:06 +0200 Subject: load related problem or my compilation ? Sender: owner-current@freebsd.org Precedence: bulk Unfortunately, this machine is also the most heavily loaded (with PPP dial-ins) and continues to stop dead .. no reboot .. nothing :-( Yet none of my other machines do this. It's a UMC 486DX/33, 16 meg of RAM, a gig of SCSI, all serial ports are 16550AFN .. however, the kernel is compiled with "-O2 -m486 -fno-strength-reduce" .. is this compilation likely to cause me this much pain or should I start looking more closely at the hardware ? I've already tried adding wait states to the cache, to main memory, reduced the BusLogic's DMA rate .. it's now slower than my 386DX/40 and I'm running out of options .. :-( Make sure external cache is write through. We are seeing similar effects on -STABLE, but also get panics (dumps available as ftp://clinet.fi/pub/FreeBSD/crashdumps/*.[2-8]. Maybe ppp is releasing a mbuf which has already been freed (the contents are 0xdeadc0de and such)? The lockups vary, either it just locks up, or it panics but does not get far enough after dumping to reset. Probably all this is because of wild pointers generated by access to freed data? If someone needs more dumps, our terminal servers generate them at rate of 1-2 dumps per day :-( I haven't had time to PR this but I'll try to get it done today. I'm trying going back to -current, as I did not have this problem before (but we didn't get this much PPP dialin load before). -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-current Sun Oct 29 06:39:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA25165 for current-outgoing; Sun, 29 Oct 1995 06:39:13 -0800 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA25160 for ; Sun, 29 Oct 1995 06:39:06 -0800 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD-4.4) id BAA09021; Mon, 30 Oct 1995 01:38:40 +1100 From: michael butler Message-Id: <199510291438.BAA09021@asstdc.scgt.oz.au> Subject: Re: load related problem or my compilation ? To: hsu@cs.hut.fi (Heikki Suonsivu) Date: Mon, 30 Oct 1995 01:38:38 +1100 (EST) Cc: freebsd-current@freebsd.org In-Reply-To: <199510291407.QAA09219@shadows.cs.hut.fi> from "Heikki Suonsivu" at Oct 29, 95 04:07:52 pm X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2114 Sender: owner-current@freebsd.org Precedence: bulk > Make sure external cache is write through. The machine is sufficiently old so as not to have this optional .. i.e. I assume it can only be write-through. > We are seeing similar effects on -STABLE, but also get panics (dumps > available as ftp://clinet.fi/pub/FreeBSD/crashdumps/*.[2-8]. Maybe ppp is > releasing a mbuf which has already been freed (the contents are 0xdeadc0de > and such)? The lockups vary, either it just locks up, or it panics but > does not get far enough after dumping to reset. Probably all this is > because of wild pointers generated by access to freed data? I recompiled with "-O -pipe -m486". Now, with only two 28k8 modems being fed as fast as a Cisco with stacker compression enabled will allow (~3000cps each), it will now mostly just spontaneously reboot. One modem alone won't do it .. two running flat out will inside half an hour :-( Both modem links are running with an MTU/MRU of 552, so there is some (hopefully small) amount of fragmentation going on. Watching the mbuf clusters, I see no more than ~120k allocated in ~40-50 clusters so there doesn't seem to be any shortage .. I did another compile with NMBCLUSTERS=2048 but, as expected, nothing different happened. It still dies without logging anything at all about the failure event. I have a feeling (more than actual observation as the machine's 4km from here) that it may be dying when one of the modems drops the link whilst in full flight .. ~16k of data in the PPP send queue with more rapidly arriving .. but I haven't been able to catch it doing it whilst I'm actually there and watching it. Another possibility is that this one is a relatively slow machine with only 16 meg of RAM, so it's also vaguely possible that it's finding a kernel memory allocation problem that doesn't worry faster ones. > I'm trying going back to -current, as I did not have this problem before > (but we didn't get this much PPP dialin load before). Mine is -current as of ~7am, Oct 15th .. a week or so after the VM stuff got fixed .. has anyone changed anything else since then that might affect/fix this ? michael From owner-freebsd-current Sun Oct 29 06:41:49 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA25259 for current-outgoing; Sun, 29 Oct 1995 06:41:49 -0800 Received: from madonna.ic.net (root@[152.160.131.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA25254 for ; Sun, 29 Oct 1995 06:41:44 -0800 Received: (from rob@localhost) by madonna.ic.net (8.6.12/8.6.9) id JAA00240 for current@freebsd.org; Sun, 29 Oct 1995 09:40:03 -0500 Posted-Date: Sun, 29 Oct 1995 09:40:03 -0500 Message-Id: <199510291440.JAA00240@madonna.ic.net> Subject: X with today's current To: current@freebsd.org Date: Sun, 29 Oct 1995 09:40:01 -0500 (EST) From: "Rob Misiak" Reply-To: rdm@ic.net X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 527 Sender: owner-current@freebsd.org Precedence: bulk I sup'ed around 30 minutes ago (9:00am EST). I try to start X, and the window manager (ctwm) will be loaded, then it just hangs, I can't even move the mouse. Also, I have it set to automatically open an xterm, but it doesn't get to this either. Then I tried switching to a vt, and the system restarted. It's strange. :) Anyone else having this problem? (I made a lot of changes to my configuration yesterday and I'm worried that is what's causing it, though it probably isn't since I can use X fine with an older kernel.) Rob From owner-freebsd-current Sun Oct 29 06:44:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA25365 for current-outgoing; Sun, 29 Oct 1995 06:44:30 -0800 Received: from eikon.e-technik.tu-muenchen.de (root@eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA25353 ; Sun, 29 Oct 1995 06:44:22 -0800 Received: from vector.eikon.e-technik.tu-muenchen.de (vector.eikon.e-technik.tu-muenchen.de [129.187.142.36]) by eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) with ESMTP id PAA03269; Sun, 29 Oct 1995 15:43:49 +0100 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.12/8.6.9) id PAA08745; Sun, 29 Oct 1995 15:43:49 +0100 Date: Sun, 29 Oct 1995 15:43:49 +0100 From: "Julian Stacey jhs@freebsd.org" Message-Id: <199510291443.PAA08745@vector.eikon.e-technik.tu-muenchen.de> To: current@freebsd.org Subject: http://www.freebsd.org/~jhs/freebsd_people.html Cc: jhs@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk To the guy who's name ive forgotten, who wanted to drop a gif in my incoming/ for addition to http://www.freebsd.org/~jhs/freebsd_people.html I guoted: ftp freebsd.org:~jhs/incoming I've just discovered ftp doesnt support ~jhs syntax, use: freebsd.org:/a/jhs/incoming Julian S From owner-freebsd-current Sun Oct 29 07:06:03 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA26326 for current-outgoing; Sun, 29 Oct 1995 07:06:03 -0800 Received: from ess.harris.com (su15a.ess.harris.com [130.41.1.251]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA26321 for ; Sun, 29 Oct 1995 07:05:57 -0800 Received: from borg.ess.harris.com (suw2k.ess.harris.com) by ess.harris.com (5.x/SMI-SVR4) id AA04667; Sun, 29 Oct 1995 10:05:51 -0500 Received: by borg.ess.harris.com (4.1/SMI-4.1) id AA02574; Sun, 29 Oct 95 10:03:03 EST Date: Sun, 29 Oct 95 10:03:03 EST From: jleppek@suw2k.ess.harris.com (James Leppek) Message-Id: <9510291503.AA02574@borg.ess.harris.com> To: freebsd-current@freefall.FreeBSD.org Subject: broken LKMs Sender: owner-current@FreeBSD.org Precedence: bulk I saw a commit go by to remove the LKMs that fail from the makefile however I just did a sup and LKM is still does not work. The makefile does not have the broken modules (ie. atapi) removed. Did it get lost or still pending??? Jim From owner-freebsd-current Sun Oct 29 07:45:36 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA28074 for current-outgoing; Sun, 29 Oct 1995 07:45:36 -0800 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA28066 for ; Sun, 29 Oct 1995 07:45:31 -0800 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA29304 (5.65c8/HUTCS-S 1.4 for ); Sun, 29 Oct 1995 17:45:26 +0200 Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id RAA09345; Sun, 29 Oct 1995 17:45:38 +0200 Date: Sun, 29 Oct 1995 17:45:38 +0200 Message-Id: <199510291545.RAA09345@shadows.cs.hut.fi> From: Heikki Suonsivu To: michael butler Cc: hsu@cs.hut.fi (Heikki Suonsivu), freebsd-current@freebsd.org Subject: Re: load related problem or my compilation ? In-Reply-To: <199510291438.BAA09021@asstdc.scgt.oz.au> References: <199510291407.QAA09219@shadows.cs.hut.fi> <199510291438.BAA09021@asstdc.scgt.oz.au> Sender: owner-current@freebsd.org Precedence: bulk michael butler writes: > Watching the mbuf clusters, I see no more than ~120k allocated in ~40-50 > clusters so there doesn't seem to be any shortage .. I did another compile > with NMBCLUSTERS=2048 but, as expected, nothing different happened. It still > dies without logging anything at all about the failure event. > > I have a feeling (more than actual observation as the machine's 4km from > here) that it may be dying when one of the modems drops the link whilst in > full flight .. ~16k of data in the PPP send queue with more rapidly arriving > .. but I haven't been able to catch it doing it whilst I'm actually there > and watching it. The panics I get are almost always in the same place, and it could be something like this, but also it could be just getting a freed mbuf mid-fligth. I have had similar panic problems with a slow (38.4k) leased line which certainly does not loose carrier, and it panics sometimes, usually when a load peak suddenly arrives after idling (start up a heavy X program or like). Increasing TTYHOG and RS_IBUF_SIZE considerably reduces the number of panics I kept having, with the additional bonus of increased serial performance and no more data loss on non-flow-controlled leased lines. The 38.4k link was unusable without patching them to 4 times as big. All my systems are dedicated routing/terminal server setups, nothing else is done with them but routing. A workaround seems to be to increase TTYHOG and RS_IBUF_SIZE (I have 4k and 1k). It helps a bit, but does not fix the problem. > Another possibility is that this one is a relatively slow machine with only > 16 meg of RAM, so it's also vaguely possible that it's finding a kernel > memory allocation problem that doesn't worry faster ones. We have 486DX100 and 486DX120 machines, and they hardly ever have more than 10% CPU loads, even when all 32 ports are full. > Mine is -current as of ~7am, Oct 15th .. a week or so after the VM stuff got > fixed .. has anyone changed anything else since then that might affect/fix > this ? I'm now running -current on one machine and will switch the other two to -current to see how it works. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-current Sun Oct 29 07:53:39 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA28576 for current-outgoing; Sun, 29 Oct 1995 07:53:39 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA28569 for ; Sun, 29 Oct 1995 07:53:34 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id CAA12043; Mon, 30 Oct 1995 02:48:35 +1100 Date: Mon, 30 Oct 1995 02:48:35 +1100 From: Bruce Evans Message-Id: <199510291548.CAA12043@godzilla.zeta.org.au> To: ache@astral.msk.su, davidg@Root.COM Subject: Re: stable general protection fault in last kernel (/dev/null broken) Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk >Original command was: "mixer vol 80 > /dev/null" >Moreover, it seems that any output to /dev/null is broken, >i.e. sh echo kkk > /dev/null produce the same error. >I'll take Bruce's changes, thanx. ioctls to /dev/null were fatal. There's not much point in doing an ioctl on /dev/null, but isatty() does one to see if TIOCGETA works. Bruce From owner-freebsd-current Sun Oct 29 08:14:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA29472 for current-outgoing; Sun, 29 Oct 1995 08:14:12 -0800 Received: from grunt.grondar.za (grunt.grondar.za [196.7.18.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA29458 for ; Sun, 29 Oct 1995 08:13:56 -0800 Received: from grumble.grondar.za (grumble.grondar.za [196.7.18.130]) by grunt.grondar.za (8.6.12/8.6.9) with ESMTP id SAA07172; Sun, 29 Oct 1995 18:13:47 +0200 Received: from localhost (localhost [127.0.0.1]) by grumble.grondar.za (8.6.12/8.6.9) with SMTP id SAA00567; Sun, 29 Oct 1995 18:13:47 +0200 Message-Id: <199510291613.SAA00567@grumble.grondar.za> X-Authentication-Warning: grumble.grondar.za: Host localhost didn't use HELO protocol To: Bruce Evans cc: ache@astral.msk.su, davidg@Root.COM, current@FreeBSD.org Subject: Re: stable general protection fault in last kernel (/dev/null broken) Date: Sun, 29 Oct 1995 18:13:46 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org Precedence: bulk > >Original command was: "mixer vol 80 > /dev/null" > > >Moreover, it seems that any output to /dev/null is broken, > >i.e. sh echo kkk > /dev/null produce the same error. > >I'll take Bruce's changes, thanx. > > ioctls to /dev/null were fatal. There's not much point in > doing an ioctl on /dev/null, but isatty() does one to see > if TIOCGETA works. Thanks a lot for picking this one up, folks. I had a high temperature at the time I did this commit, and had I problem concentrating for more than 5mins. As a result, I comitted the wrong patch :-( I did not relish having to think my way through this one.... M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grumble.grondar.za for PGP key From owner-freebsd-current Sun Oct 29 08:34:54 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA00736 for current-outgoing; Sun, 29 Oct 1995 08:34:54 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id IAA00714 for ; Sun, 29 Oct 1995 08:34:35 -0800 Received: from fw.ast.com by ast.com with SMTP id AA09037 (5.67b/IDA-1.5 for ); Sun, 29 Oct 1995 08:35:08 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0t9aU3-00008FC; Sun, 29 Oct 95 10:21 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0t9aS1-000J13C; Sun, 29 Oct 95 10:19 WET Message-Id: Date: Sun, 29 Oct 95 10:19 WET To: davidg@root.com From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Sun Oct 29 1995, 10:19:13 CST Subject: Re: Support for WD8003E abandoned? Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk [0] I'm surprised to hear this, but it has been a long time since I [0]specifically tested 8bit wd8003e's. Still, I can't think of any changes [0]to the driver that could have broken this. It sounds like an interrupt [0]conflict with another card - the driver doesn't even initialize the irq [0]for those cards since they don't have soft configuration [0]- the irq is hard strapped on the card. No, that is not true. WD8003EB cards do have EEPROM and the IRQ can be set via software to 2, 3, 4, or 7. There is a "INIT" strap that forces the I/O port to 0x280, but that is about it. You have to go to 8013-class boards before you have straps that set group-choices of memory/port/irq. You run EZSETUP on WD8003EB cards just like you do on 8013 cards. You just get fewer choices in the menus (like no IRQ 5). (In fact, there was a problem back when these cards were popular with people running old versions of EZSETUP on their boards and ruining them.) As to it being an interrupt conflict, on my system I removed a working (it just downloaded the latest SNAP) 8013 card that was set to 0x280, 0xd4000, and irq 2, and replaced with three different WD8003EB cards, and all of them were SOFT configured (INIT strap removed) to 0x280, 0xd4000, and irq 2. So there was no conflict. Just to be safe, I also removed *all* other cards (except for video), and it had no effect. (HD is an IDE.) I have used these 8003 cards in DOS machines on IRQ 2 and that works fine. Later I also tried the WD8003EB cards on IRQ 7 and IRQ 3 on 1026. IRQ7 and IRQ3 also did not work. (Yes, I did disable the on-board ports or move them to other IRQs.) Now someone suggested that the problem was caused because I didn't have the WD8003EB card in an 8-bit slot. This is true, the system I was testing on is an EISA, and there are *no* 8-bit slots. The other site where the WD8003EB isn't detected at all (which I have now visited) is an ISA box but it has no 8-bit slots either. Are we saying that this card *must* go in a 8-bit slot? I knew the 8013-ELITE had problems with this (requiring a full 128K memory map), but I have never heard of a restriction like this on 8003 boards. If so, a FAQ entry is recommended. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Sun Oct 29 08:38:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA01223 for current-outgoing; Sun, 29 Oct 1995 08:38:52 -0800 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA01212 for ; Sun, 29 Oct 1995 08:38:48 -0800 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id JAA02110; Sun, 29 Oct 1995 09:29:03 -0800 Message-Id: <199510291729.JAA02110@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: rdm@ic.net cc: current@freebsd.org Subject: Re: X with today's current In-reply-to: Your message of "Sun, 29 Oct 1995 09:40:01 EST." <199510291440.JAA00240@madonna.ic.net> Date: Sun, 29 Oct 1995 09:29:03 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org Precedence: bulk >I sup'ed around 30 minutes ago (9:00am EST). I try to start X, and the window >manager (ctwm) will be loaded, then it just hangs, I can't even move the >mouse. Also, I have it set to automatically open an xterm, but it doesn't >get to this either. Then I tried switching to a vt, and the system restarted. >It's strange. :) Anyone else having this problem? (I made a lot of changes >to my configuration yesterday and I'm worried that is what's causing it, >though it probably isn't since I can use X fine with an older kernel.) > >Rob You need Bruce's DEVRANDOM fixes. You must have just missed them since I saw his commit mail before yours. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sun Oct 29 10:34:10 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA11987 for current-outgoing; Sun, 29 Oct 1995 10:34:10 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA11977 ; Sun, 29 Oct 1995 10:34:07 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id KAA08317; Sun, 29 Oct 1995 10:33:39 -0800 To: Andreas Klemm cc: hackers@freebsd.org, current@freebsd.org, jkh@freebsd.org, rb@gtn.com, mg@gtn.com, mlc@wup.de Subject: Re: several diffs for dump(8) to display write throughput and such...c In-reply-to: Your message of "Sat, 28 Oct 1995 21:06:00 BST." Date: Sun, 29 Oct 1995 10:33:39 -0800 Message-ID: <8315.814991619@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > >>DUMP: DUMP: finished in 1451 seconds, throughput 474 KBytes/sec Neat! I like it. However, we're already in feature freeze for 2.1 so this would definitely be -current fodder only, I'm afraid! Jordan From owner-freebsd-current Sun Oct 29 11:16:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA13531 for current-outgoing; Sun, 29 Oct 1995 11:16:33 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id LAA13526 for ; Sun, 29 Oct 1995 11:16:31 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA26418; Sun, 29 Oct 1995 14:16:24 -0500 Date: Sun, 29 Oct 1995 14:16:24 -0500 From: "Garrett A. Wollman" Message-Id: <9510291916.AA26418@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: chuckr@glue.umd.edu, roberto@keltia.freenix.fr, FreeBSD-current@freebsd.org Subject: Re: Make world falling over In-Reply-To: <199510290621.RAA26602@godzilla.zeta.org.au> References: <199510290621.RAA26602@godzilla.zeta.org.au> Sender: owner-current@freebsd.org Precedence: bulk < said: > Right. I forgot to say in my previous mail that is now > almost self contained so the synopsis in sysctl.3 is now almost correct. > It is still necessary to include before > because sysctl.h uses u_int (which should never be used) and size_t > (which is too much trouble to declare in yet another place). It's fairly well-established that you have to include before including any other sys/ header file, and has been that way for as long as I can remember. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Sun Oct 29 12:17:57 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA16029 for current-outgoing; Sun, 29 Oct 1995 12:17:57 -0800 Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA16010 for ; Sun, 29 Oct 1995 12:17:49 -0800 Received: (from news@localhost) by haywire.DIALix.COM (sendmail) id EAA08588 for freebsd-current@freebsd.org; Mon, 30 Oct 1995 04:17:40 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 30 Oct 1995 04:17:33 +0800 From: peter@haywire.dialix.com (Peter Wemm) Message-ID: <470ngt$8c6$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <199510291438.BAA09021@asstdc.scgt.oz.au>, <199510291545.RAA09345@shadows.cs.hut.fi> Subject: Re: load related problem or my compilation ? Sender: owner-current@freebsd.org Precedence: bulk hsu@cs.hut.fi (Heikki Suonsivu) writes: >michael butler writes: > > Watching the mbuf clusters, I see no more than ~120k allocated in ~40-50 > > clusters so there doesn't seem to be any shortage .. I did another compile > > with NMBCLUSTERS=2048 but, as expected, nothing different happened. It still > > dies without logging anything at all about the failure event. > > > > I have a feeling (more than actual observation as the machine's 4km from > > here) that it may be dying when one of the modems drops the link whilst in > > full flight .. ~16k of data in the PPP send queue with more rapidly arriving > > .. but I haven't been able to catch it doing it whilst I'm actually there > > and watching it. >The panics I get are almost always in the same place, and it could be >something like this, but also it could be just getting a freed mbuf >mid-fligth. I have had similar panic problems with a slow (38.4k) leased >line which certainly does not loose carrier, and it panics sometimes, >usually when a load peak suddenly arrives after idling (start up a heavy X >program or like). Hmm.. Are you using Bruce's cy driver? I have this vague recollection that his cypoll and siopoll hooks are launching into the tty sybsystem code at splsofttty(). I am not sure, but I dont think that splsofttty() would mask the networking code, which could mean that it might be possible for the networking code to be started up on the return from some hardware interrupt that had preempted the tty code. I wonder if what you are seeing is the cypoll() call to pppstart() being interrupted by networking code, which is manipulating the mbuf pointers? I've not looked at the old ppp-2.1.2 code for quite some time now, as I've been working on getting ppp-2.2 up and running. I remember having this discussion with Bruce a few weeks ago, but I can't find his answer and I can't for the life of me remember exactly what he said. Just thinking about the lengths that had been gone to in getting ppp-2.2 up without totally interlocking spltty() and splimp() makes my brain turn back to mush. -Peter From owner-freebsd-current Sun Oct 29 12:31:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA16474 for current-outgoing; Sun, 29 Oct 1995 12:31:46 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA16469 for ; Sun, 29 Oct 1995 12:31:42 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.12/8.6.12) id NAA17426 for current@FreeBSD.org; Sun, 29 Oct 1995 13:31:33 -0700 Message-Id: <199510292031.NAA17426@trout.sri.MT.net> From: nate@trout.sri.MT.net (Nate Williams) Date: Sun, 29 Oct 1995 13:31:32 WET X-Mailer: Mail User's Shell (7.2.6 (dynamic) alpha(3) 7/19/95) To: current@FreeBSD.org Subject: Cronjob error Sender: owner-current@FreeBSD.org Precedence: bulk > Subject: trout weekly run output > > Rotating messages: > Rotating cron log: > > Rebuilding locate database: > stty: stdin isn't a terminal > TERM: Undefined variable. ^^^^^^^^^^^^^^^^^^^^^^^^^^ What's causing this, and is anyone else experiencing it? Nate From owner-freebsd-current Sun Oct 29 12:34:31 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA16567 for current-outgoing; Sun, 29 Oct 1995 12:34:31 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id MAA16557 for ; Sun, 29 Oct 1995 12:34:24 -0800 Received: from fw.ast.com by ast.com with SMTP id AA09619 (5.67b/IDA-1.5 for ); Sun, 29 Oct 1995 12:35:29 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0t9e73-00008FC; Sun, 29 Oct 95 14:13 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0t9e4S-000ItnC; Sun, 29 Oct 95 14:11 WET Message-Id: Date: Sun, 29 Oct 95 14:11 WET To: current@freebsd.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Sun Oct 29 1995, 14:11:07 CST Subject: Ports - What is the standard for "ported"? Sender: owner-current@freebsd.org Precedence: bulk I recently (and am still) going through a rather agonizing migration of a SCO UNIX system to FreeBSD 2.0.5. Apart from lots of issues with SCSI hardware that SCO took in stride and FreeBSD hated ("unknown board" errors for an Adaptec 1540A, which is one of the non-thru-hole, 2nd generation surface-mount boards, and dealing with a WangDAT tape drive that under 2.0.5 won't let you remove the media until you reboot the system, OR you can issue a mt offline, remove the media, and then reboot to get the drive to load new media - that really stinks and didn't happen under SCO and I hope it is fixed in 2.1.0), I ran into a lot of application issues. My big problem came with some of the ports. I really haven't had the opportunity to use or rely on these or the associated mechanisms before, but in the past 72 hours I have and found them to be a tad "uneven". The worst offender was smail. I had to manually locate the files since the site was not operating under its final IP address yet (so that the neighbors would not try to send mail yet), and the pkg system tried to get the package first from ftp.uu.net, which refuses all requests from sites with no reverse DNS look-up. Nice deadly embrace. 99% of the desktops where I work would fail in the same way because the security guys won't list them in the DNS tables that are visible outside the firewall. Make then went on to Walnut Creek, and failed with an error that looked like it was unable to find the files on that system. If it was supposed to try additional locations at this point, that doesn't work. Later I discovered that WC was "full" at the time, and the code that performs the downloads doesn't put out a real good message describing what is really going on. So now I have smail down and I do the "make". BOOM! Oh, you have to have bash installed (a different port) before you can build smail. This "other package first" requirement was not listed anywhere I noted, and it seems curious that we would include a port installation that relied on a shell that we don't distribute by default. Ok, I got bash and installed it. Re-ran the smail install, and it decided it had better download everything again. (Why?). Then it started building, WITHOUT giving me a chance to update the EDITME file. Ok, I assume EDITME must be set-up perfectly for FreeBSD. (Foolish) The compile goes with numerous warnings, and finally succeeds. So I install. I send a test message to myself. It is not delivered. Run the queue manually. It is not delivered. The mail is in the queue, but smail complains about having to defer delivery. I update the config file to indicate a local "smart" mailer and try off-site mail. That works fine! I try sending mail from a remote system to my account. It is placed in the queue and eventually delivered. I try local mail again from me to me (or from root to root). Local mail just sits in the queue endlessly. After a few days of investigation, it appears that the "os/freebsd2.0" file for smail and the patches for FreeBSD for smail are not quite compatible, with the result you have to comment-out all of the local: stuff in transports if you ever want to see mail from yourself or any other local account again. The EDITME and os items seem to be out of date on system capabilities as well, turning on features FreeBSD doesn't have and not turning on some that it has now. Maybe these files were correct at FreeBSD 2.0, but they are not correct now. So I went to make changes to conf/EDITME, and cd .. and then did a "make clean" "make". Guess what? It fails because of some "bashisms", even if I run "bash" before doing the makes. The only way I could get it to compile at this point was to cd ../.., remove the .build_complete (or whatever it was called) file, cd .. again and then do a make up here. You have to be careful because once it decided the best thing to do was re-extract the entire distribution and erase the changes I just made. Grrr. Oh, and don't do the "make clean" at this higher level, because it WILL erase the EDITME file, and re-extracts everything from the distribution tar. That isn't my idea of a "make clean" action. Again, I found no README that mentioned that you have to anything out of the ordinary to make and/or configure smail. The EDITME also dictated some locations for directories and files that did not match where they already are on a FreeBSD, particularly if you are planning on completely replacing sendmail with smail. Where it looks for spool, aliases and paths spring to mind. This makes me wonder: is the requirement for a "port" that it just compiles and links? Someone needs to look at smail and see if things need updating. Also, if a port requires some other non-included item (like BASH), it should state this somewhere, like in a README. I can see where this stuff would drive a newbie totally nuts. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Sun Oct 29 12:55:03 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA17105 for current-outgoing; Sun, 29 Oct 1995 12:55:03 -0800 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA17087 for ; Sun, 29 Oct 1995 12:54:56 -0800 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id PAA03176; Sun, 29 Oct 1995 15:42:53 -0500 Date: Sun, 29 Oct 1995 15:42:52 -0500 (EST) From: "Jonathan M. Bresler" Subject: Re: Ports - What is the standard for "ported"? To: Frank Durda IV cc: current@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Sun, 29 Oct 1995, Frank Durda IV wrote: > a WangDAT tape drive that under 2.0.5 won't let you remove the media until > you reboot the system, OR you can issue a mt offline, remove the media, and > then reboot to get the drive to load new media - that really stinks and this problem must be unique to WangDAT or at least non-exabyte 4mm tape drives. i use a 4mm for daily backup. unload the tape with "/usr/bin/mt -f /dev/rst0 rewoffl". load a new tape every morning and haev no problems at all. here is my dump.4mm script (the rewind gets the tape started, should not be needed but is, alas) #!/bin/sh echo "" >> dump.log echo "" >> dump.log echo "" >> dump.log /usr/bin/mt -f /dev/rst0 rewind /sbin/dump 0unBbf 1200000 10 /dev/nrst0 /dev/sd1a 2>&1 | tee -a /root/dump.log /sbin/dump 0unBbf 1200000 10 /dev/nrst0 /dev/sd1e 2>&1 | tee -a /root/dump.log /sbin/dump 0unBbf 1200000 10 /dev/rst0 /dev/sd1f 2>&1 | tee -a /root/dump.log /usr/bin/mt -f /dev/rst0 rewoffl Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Sun Oct 29 13:07:04 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA17546 for current-outgoing; Sun, 29 Oct 1995 13:07:04 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA17534 for ; Sun, 29 Oct 1995 13:06:59 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id IAA18433; Mon, 30 Oct 1995 08:03:59 +1100 Date: Mon, 30 Oct 1995 08:03:59 +1100 From: Bruce Evans Message-Id: <199510292103.IAA18433@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@lcs.mit.edu Subject: Re: Make world falling over Cc: FreeBSD-current@freebsd.org, chuckr@glue.umd.edu, roberto@keltia.freenix.fr Sender: owner-current@freebsd.org Precedence: bulk >> Right. I forgot to say in my previous mail that is now >> almost self contained so the synopsis in sysctl.3 is now almost correct. >> It is still necessary to include before >It's fairly well-established that you have to include >before including any other sys/ header file, and has been that way for >as long as I can remember. This (bogus) requirement is usually documented (e.g., in stat.2). POSIX requires applications to include before all POSIX headers, including before ones in /usr/include that traditionally don't require it, e.g., , and . FreeBSD includes in some of these headers for convenience. uses explicit (wrong) types instead of uid_t and gid_t, perhaps to avoid including . uses explicit (wrong) types instead of uid_t and gid_t, although it includes . Bruce From owner-freebsd-current Sun Oct 29 14:46:54 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA22600 for current-outgoing; Sun, 29 Oct 1995 14:46:54 -0800 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id OAA22592 for ; Sun, 29 Oct 1995 14:46:50 -0800 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA01682 (5.65c8/HUTCS-S 1.4 for ); Mon, 30 Oct 1995 00:46:46 +0200 Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id AAA09796; Mon, 30 Oct 1995 00:46:46 +0200 Date: Mon, 30 Oct 1995 00:46:46 +0200 Message-Id: <199510292246.AAA09796@shadows.cs.hut.fi> From: Heikki Suonsivu To: peter@haywire.dialix.com (Peter Wemm) Cc: freebsd-current@freebsd.org In-Reply-To: peter@haywire.dialix.com's message of 29 Oct 1995 22:23:18 +0200 Subject: Re: load related problem or my compilation ? Sender: owner-current@freebsd.org Precedence: bulk >mid-fligth. I have had similar panic problems with a slow (38.4k) leased >line which certainly does not loose carrier, and it panics sometimes, >usually when a load peak suddenly arrives after idling (start up a heavy X >program or like). Hmm.. Are you using Bruce's cy driver? On the leased line no, on terminal servers yes. I don't know for sure if the problems are same. I have this vague recollection that his cypoll and siopoll hooks are launching into the tty sybsystem code at splsofttty(). I am not sure, but I dont think that splsofttty() would mask the networking code, which could mean that it might be possible for the networking code to be started up on the return from some hardware interrupt that had preempted the tty code. The mbuf is taken within splimp(), and then accessed outside it after taking it (in ppp_dequeue). I don't have the kernel experience to tell what should be done. I wonder if what you are seeing is the cypoll() call to pppstart() being interrupted by networking code, which is manipulating the mbuf pointers? Check out the dumps, they will probably tell you more than I can tell you :-) -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-current Sun Oct 29 16:22:00 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA10759 for current-outgoing; Sun, 29 Oct 1995 16:22:00 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA10736 for ; Sun, 29 Oct 1995 16:21:57 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by precipice.shockwave.com (8.6.12/8.6.12) with SMTP id QAA02769; Sun, 29 Oct 1995 16:20:48 -0800 Message-ID: <30941A60.167EB0E7@shockwave.com> Date: Sun, 29 Oct 1995 16:20:48 -0800 From: Paul Traina X-Mailer: Mozilla 2.0b1 (X11; I; FreeBSD 2.1-STABLE i386) MIME-Version: 1.0 To: Andreas Klemm CC: current@freebsd.org Subject: Re: time -l, floating point exeption, division through '0'. trace + FIX ! References: <199510291157.MAA00781@knobel.gun.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org Precedence: bulk I made a similar change just yesterday. From owner-freebsd-current Sun Oct 29 16:41:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA16860 for current-outgoing; Sun, 29 Oct 1995 16:41:16 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id QAA16829 for ; Sun, 29 Oct 1995 16:41:11 -0800 Received: by sovcom.kiae.su id AA17049 (5.65.kiae-1 ); Mon, 30 Oct 1995 03:35:21 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 30 Oct 95 03:35:20 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id DAA01618; Mon, 30 Oct 1995 03:26:27 +0300 To: current@FreeBSD.org, Nate Williams References: <199510292031.NAA17426@trout.sri.MT.net> In-Reply-To: <199510292031.NAA17426@trout.sri.MT.net>; from Nate Williams at Sun, 29 Oct 1995 13:31:32 WET Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 30 Oct 1995 03:26:27 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: Cronjob error Lines: 22 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 684 Sender: owner-current@FreeBSD.org Precedence: bulk In message <199510292031.NAA17426@trout.sri.MT.net> Nate Williams writes: >> Subject: trout weekly run output >> >> Rotating messages: >> Rotating cron log: >> >> Rebuilding locate database: >> stty: stdin isn't a terminal >> TERM: Undefined variable. > ^^^^^^^^^^^^^^^^^^^^^^^^^^ >What's causing this, and is anyone else experiencing it? Check root startup files, .cshrc maybe... -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sun Oct 29 16:44:23 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA18055 for current-outgoing; Sun, 29 Oct 1995 16:44:23 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA18008 for ; Sun, 29 Oct 1995 16:44:14 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.12/8.6.12) id RAA17636; Sun, 29 Oct 1995 17:43:57 -0700 Message-Id: <199510300043.RAA17636@trout.sri.MT.net> From: nate@trout.sri.MT.net (Nate Williams) Date: Sun, 29 Oct 1995 17:43:56 WET In-Reply-To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) "Re: Cronjob error" (Oct 30, 3:26am) X-Mailer: Mail User's Shell (7.2.6 (dynamic) alpha(3) 7/19/95) To: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) , current@FreeBSD.org Subject: Re: Cronjob error Sender: owner-current@FreeBSD.org Precedence: bulk > >> Subject: trout weekly run output > >> > >> Rotating messages: > >> Rotating cron log: > >> > >> Rebuilding locate database: > >> stty: stdin isn't a terminal > >> TERM: Undefined variable. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > > >What's causing this, and is anyone else experiencing it? > > Check root startup files, .cshrc maybe... Nope, everything's protected as far as I know. Here's the relevant lines that aren't. set autolist set autologout=0 set history=100 set notify if ($?prompt) then ... I suppose I could move the lines from above inside, but I wouldn't think they would make a difference. Nate From owner-freebsd-current Sun Oct 29 16:54:59 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA20516 for current-outgoing; Sun, 29 Oct 1995 16:54:59 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id QAA20510 for ; Sun, 29 Oct 1995 16:54:51 -0800 Received: from fw.ast.com by ast.com with SMTP id AA10212 (5.67b/IDA-1.5 for ); Sun, 29 Oct 1995 16:55:56 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0t9hnN-00008GC; Sun, 29 Oct 95 18:09 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0t9hkn-000ItnC; Sun, 29 Oct 95 18:07 WET Message-Id: Date: Sun, 29 Oct 95 18:07 WET To: jmb@kryten.atinc.com, current@freebsd.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Sun Oct 29 1995, 18:07:04 CST Subject: Re: WANGDAT strangeness Sender: owner-current@freebsd.org Precedence: bulk [0]a WangDAT tape drive that under 2.0.5 won't let you remove the media until [0]you reboot the system, OR you can issue a mt offline, remove the media, and [0]then reboot to get the drive to load new media - that really stinks and [1] this problem must be unique to WangDAT or at least non-exabyte [1]4mm tape drives. i use a 4mm for daily backup. unload the tape with [1]"/usr/bin/mt -f /dev/rst0 rewoffl". load a new tape every morning and [1]haev no problems at all. I plan to try this drive on 2.1 1026 SNAP before I file a real bug report on it. This is an early WangDAT DAT drive, but it is new enough to have compression. It came out around late 1990 or early 1991. FYI, the 1540A host adapter was flagged as an "unknown board" during installation from the 2.0.5 boot floppy, but the driver seems to know what board it is once you get running off the SCSI hard disk. At least the "unknown board" complaint went away. Strange. The DAT drive has a READY and an ACCESS light. Under SCO, the READY light would blink yellow while loading/unloading, then remain green until the media is unmounted. The ACCESS light only blinked during commands/transfers, etc. So when the drive is idle (tape loaded or unloaded), the ACCESS light is dark. On 2.0.5-R, the ACCESS light is off until you touch the drive, then it goes on solid and remains on regardless of activity. Once the drive is touched, the front-panel eject button no longer works. (From external appearances, it acts like it is always in the middle of processing a command from the host.) If you issue a mt offline command, the ACCESS light goes out. Now you can press the front-panel EJECT button and get the media out of the drive. However if you try to insert any media, the READY light just blinks YELLOW and the loader refuses to grab the tape and take it inside. You must reboot to load the next tape. All of the mt commands fail once you issue a mt offline, even if you don't remove the media. The drive/driver also has a habit of locking up under 2.0.5. Because of the botched status light under 2.0.5, I can't tell what is going on with the drive. All I know is that the transfers appear to stop. After five minutes or so, I will get a timeout error from the driver, and the application aborts. This was a real pain as I tried to restore peoples' account data. I was never able to get a large blocksize (>1K) to work all the way through the cpio or tar (I happened to make both before migrating). Finally I used a tar with a blocksize of 1 (wow is that slow) and was able to get all the way through without incident but it took six hours. Of course I then had to reboot to get the media out of the drive, but that is another problem. I have been using the DAT drive for about four years under SCO UNIX with their standard driver, so I know that the drive works well. All these failures were with reads. I haven't tried any write operations (I'm almost afraid to attempt something that might stress the driver like running 'dump'), but that day is coming. I may be forced to start NFS, and do some sort of primitive backup of the 2.0.5 system over the network to a SCO machine. Yuck. This was certainly not one of the snags I told management we might encounter in migration. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Sun Oct 29 17:12:57 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA21137 for current-outgoing; Sun, 29 Oct 1995 17:12:57 -0800 Received: from sovcom.kiae.su (sovcom.kiae.su [144.206.136.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id RAA21127 for ; Sun, 29 Oct 1995 17:12:54 -0800 Received: by sovcom.kiae.su id AA18921 (5.65.kiae-1 ); Mon, 30 Oct 1995 04:08:15 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Mon, 30 Oct 95 04:08:15 +0300 Received: (from ache@localhost) by ache.dialup.demos.ru (8.6.11/8.6.9) id EAA01825; Mon, 30 Oct 1995 04:06:26 +0300 To: current@FreeBSD.org, Nate Williams References: <199510300043.RAA17636@trout.sri.MT.net> In-Reply-To: <199510300043.RAA17636@trout.sri.MT.net>; from Nate Williams at Sun, 29 Oct 1995 17:43:56 WET Message-Id: Organization: Olahm Ha-Yetzirah Date: Mon, 30 Oct 1995 04:06:26 +0300 (MSK) X-Mailer: Mail/@ [v2.40 FreeBSD] From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) X-Class: Fast Subject: Re: Cronjob error Lines: 30 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 983 Sender: owner-current@FreeBSD.org Precedence: bulk In message <199510300043.RAA17636@trout.sri.MT.net> Nate Williams writes: >> >> Subject: trout weekly run output >> >> >> >> Rotating messages: >> >> Rotating cron log: >> >> >> >> Rebuilding locate database: >> >> stty: stdin isn't a terminal >> >> TERM: Undefined variable. >> > ^^^^^^^^^^^^^^^^^^^^^^^^^^ >> >> >What's causing this, and is anyone else experiencing it? >> >> Check root startup files, .cshrc maybe... >Nope, everything's protected as far as I know. I suppose "nice -5 su -m nobody 2>&1" command cause it. Try to change it or remove it to check. Or remove all startup files including those from /etc and from root home directory to find what plays role here. -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - http://dt.demos.su/~ache : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sun Oct 29 17:38:19 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA21842 for current-outgoing; Sun, 29 Oct 1995 17:38:19 -0800 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA21834 for ; Sun, 29 Oct 1995 17:38:10 -0800 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id UAA10198; Sun, 29 Oct 1995 20:25:56 -0500 Date: Sun, 29 Oct 1995 20:25:55 -0500 (EST) From: "Jonathan M. Bresler" Subject: Re: WANGDAT strangeness To: Frank Durda IV cc: current@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Sun, 29 Oct 1995, Frank Durda IV wrote: > [0]a WangDAT tape drive that under 2.0.5 won't let you remove the media until > [0]you reboot the system, OR you can issue a mt offline, remove the media, and > [0]then reboot to get the drive to load new media - that really stinks and > > [1] this problem must be unique to WangDAT or at least non-exabyte > [1]4mm tape drives. i use a 4mm for daily backup. unload the tape with > [1]"/usr/bin/mt -f /dev/rst0 rewoffl". load a new tape every morning and > [1]haev no problems at all. > The DAT drive has a READY and an ACCESS light. Under SCO, the READY light > would blink yellow while loading/unloading, then remain green until the > media is unmounted. The ACCESS light only blinked during > commands/transfers, etc. So when the drive is idle (tape loaded or unloaded), > the ACCESS light is dark. > > On 2.0.5-R, the ACCESS light is off until you touch the drive, then it > goes on solid and remains on regardless of activity. Once the drive is > touched, the front-panel eject button no longer works. (From external > appearances, it acts like it is always in the middle of processing a > command from the host.) [snip] > I have been using the DAT drive for about four years under SCO UNIX with > their standard driver, so I know that the drive works well. the wangdat drive may have broken firmware...my toshiba cdrom does. i had to patch the kernel to overcome it...the drive claimed to be a hard disk! how about sending in the dmesg output, boot with -v, please. > > Frank Durda IV |"The Knights who say "LETNi" > or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" > ...letni!rwsys!nemesis!uhclem |"A what?" > ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 okay--so what is letni? i didnt find it as a vax opcode..though bbcci and bbssi look kinda net. > > Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Sun Oct 29 17:43:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA22364 for current-outgoing; Sun, 29 Oct 1995 17:43:28 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA22355 for ; Sun, 29 Oct 1995 17:43:25 -0800 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id RAA16841 for ; Sun, 29 Oct 1995 17:43:05 -0800 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id MAA00320; Mon, 30 Oct 1995 12:05:31 +1030 From: Michael Smith Message-Id: <199510300135.MAA00320@genesis.atrad.adelaide.edu.au> Subject: Re: Cronjob error To: nate@trout.sri.MT.net (Nate Williams) Date: Mon, 30 Oct 1995 12:05:30 +1030 (CST) Cc: ache@astral.msk.su, current@FreeBSD.org In-Reply-To: <199510300043.RAA17636@trout.sri.MT.net> from "Nate Williams" at Oct 29, 95 05:43:56 pm Content-Type: text Content-Length: 985 Sender: owner-current@FreeBSD.org Precedence: bulk Nate Williams stands accused of saying: > > >> Rotating messages: > > >> Rotating cron log: > > >> > > >> Rebuilding locate database: > > >> stty: stdin isn't a terminal > > >> TERM: Undefined variable. > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > >What's causing this, and is anyone else experiencing it? My guess is that you have /bin/mail symlinked to something else. A quick look through the locate stuff offers no clues. > I suppose I could move the lines from above inside, but I wouldn't think > they would make a difference. cron uses sh not csh, unless you've set SHELL in the crontab. > Nate -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Sun Oct 29 19:08:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA26560 for current-outgoing; Sun, 29 Oct 1995 19:08:46 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id TAA26555 for ; Sun, 29 Oct 1995 19:08:42 -0800 Received: from fw.ast.com by ast.com with SMTP id AA10686 (5.67b/IDA-1.5 for ); Sun, 29 Oct 1995 19:09:52 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0t9kOe-000089C; Sun, 29 Oct 95 20:56 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0t9kN5-000IwpC; Sun, 29 Oct 95 20:54 WET Message-Id: Date: Sun, 29 Oct 95 20:54 WET To: jmb@kryten.atinc.com From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Sun Oct 29 1995, 20:54:47 CST Subject: Re: WANGDAT strangeness Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk [0]a WangDAT tape drive that under 2.0.5 won't let you remove the media until [0]you reboot the system, OR you can issue a mt offline, remove the media, and [0]then reboot to get the drive to load new media - that really stinks and [1] this problem must be unique to WangDAT or at least non-exabyte [1]4mm tape drives. i use a 4mm for daily backup. unload the tape with [1]"/usr/bin/mt -f /dev/rst0 rewoffl". load a new tape every morning and [1]haev no problems at all. [2]The DAT drive has a READY and an ACCESS light. Under SCO, the READY light [2]would blink yellow while loading/unloading, then remain green until the [2]media is unmounted. The ACCESS light only blinked during [2]commands/transfers, etc. So when the drive is idle (tape loaded or [2]unloaded), the ACCESS light is dark. [2] [2]On 2.0.5-R, the ACCESS light is off until you touch the drive, then it [2]goes on solid and remains on regardless of activity. Once the drive is [2]touched, the front-panel eject button no longer works. (From external [2]appearances, it acts like it is always in the middle of processing a [2]command from the host.) [3][snip] [2]I have been using the DAT drive for about four years under SCO UNIX with [2]their standard driver, so I know that the drive works well. [3] the wangdat drive may have broken firmware...my toshiba cdrom [3]does. i had to patch the kernel to overcome it...the drive claimed to be [3]a hard disk! how about sending in the dmesg output, boot with -v, please. Note that I replaced the 1540A with a 1542C to see if it would reduce the lockups. It didn't make any difference in behavior. So here is the system as it stands now: (I can't do a -v tonight since I am not at the location, but I was able to do a plain reboot remotely. Looks like the drive is considered a sequential device.) Oct 29 20:23:11 trsvax /kernel: FreeBSD 2.0.5-RELEASE #0: Sat Jun 10 10:46:56 1995 Oct 29 20:23:11 trsvax /kernel: jkh@westhill.cdrom.com:/usr/src/sys/ compile/GENERIC Oct 29 20:23:11 trsvax /kernel: CPU: i486DX (486-class CPU) Oct 29 20:23:11 trsvax /kernel: real memory = 16384000 (4000 pages) Oct 29 20:23:12 trsvax /kernel: avail memory = 14807040 (3615 pages) Oct 29 20:23:12 trsvax /kernel: Probing for devices on the ISA bus: Oct 29 20:23:12 trsvax /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Oct 29 20:23:12 trsvax /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Oct 29 20:23:12 trsvax /kernel: ed0 at 0x280-0x29f irq 9 maddr 0xd4000 msize 16384 on isa Oct 29 20:23:13 trsvax /kernel: ed0: address 00:00:c0:1e:e9:5a, type WD8013EPC (16 bit) ... Oct 29 20:23:17 trsvax /kernel: aha0: AHA-1542CF BIOS v2.01-VF.0, enabling mailbox, enabling residuals Oct 29 20:23:18 trsvax /kernel: aha0: reading board settings, dma=5 int=11 (bus speed defaulted) Oct 29 20:23:18 trsvax /kernel: aha0 at 0x330-0x333 irq 11 drq 5 on isa Oct 29 20:23:18 trsvax /kernel: aha0 waiting for scsi devices to settle Oct 29 20:23:18 trsvax /kernel: (aha0:0:0): "SEAGATE2 ST1239NS 9215" type 0 fixed SCSI 1 Oct 29 20:23:19 trsvax /kernel: sd0(aha0:0:0): Direct-Access 194MB (398790 512 byte sectors) Oct 29 20:23:19 trsvax /kernel: (aha0:2:0): "WangDAT Model 2600 01.2" type 1 removable SCSI 1 Oct 29 20:23:19 trsvax /kernel: st0(aha0:2:0): Sequential-Access density code 0x93, drive empty Oct 29 20:23:19 trsvax /kernel: (aha0:6:0): "SEAGATE ST11200N 8334" type 0 fixed SCSI 2 Oct 29 20:23:19 trsvax /kernel: sd1(aha0:6:0): Direct-Access 1005MB (2059140 512 byte sectors) ... Oct 29 20:23:22 trsvax /kernel: npx0 on motherboard Oct 29 20:23:22 trsvax /kernel: npx0: INT 16 interface Oct 29 20:23:22 trsvax /kernel: changing root device to sd0a Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 [3]okay--so what is letni? i didnt find it as a vax opcode..though [3]bbcci and bbssi look kinda net. Read it backwards, like the architecture. :-( From owner-freebsd-current Sun Oct 29 19:26:38 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA27460 for current-outgoing; Sun, 29 Oct 1995 19:26:38 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA27447 for ; Sun, 29 Oct 1995 19:26:35 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id TAA09534; Sun, 29 Oct 1995 19:22:42 -0800 From: Julian Elischer Message-Id: <199510300322.TAA09534@ref.tfs.com> Subject: Re: WANGDAT strangeness To: uhclem%nemesis@fw.ast.com (Frank Durda IV) Date: Sun, 29 Oct 1995 19:22:41 -0800 (PST) Cc: jmb@kryten.atinc.com, current@freebsd.org In-Reply-To: from "Frank Durda IV" at Oct 29, 95 08:54:00 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2621 Sender: owner-current@freebsd.org Precedence: bulk > > [0]a WangDAT tape drive that under 2.0.5 won't let you remove the media until > [0]you reboot the system, OR you can issue a mt offline, remove the media, and > [0]then reboot to get the drive to load new media - that really stinks and > This is correct see later.. > [1] this problem must be unique to WangDAT or at least non-exabyte > [1]4mm tape drives. i use a 4mm for daily backup. unload the tape with > [1]"/usr/bin/mt -f /dev/rst0 rewoffl". load a new tape every morning and > [1]haev no problems at all. no he probably hasn't tried to do an mt offline yet. > > [2]The DAT drive has a READY and an ACCESS light. Under SCO, the READY light > [2]would blink yellow while loading/unloading, then remain green until the > [2]media is unmounted. The ACCESS light only blinked during > [2]commands/transfers, etc. So when the drive is idle (tape loaded or > [2]unloaded), the ACCESS light is dark. ok, so SCO is broken.. so? > [2] > [2]On 2.0.5-R, the ACCESS light is off until you touch the drive, then it > [2]goes on solid and remains on regardless of activity. Once the drive is > [2]touched, the front-panel eject button no longer works. (From external > [2]appearances, it acts like it is always in the middle of processing a > [2]command from the host.) no, it is stopping joe-random from pushing the eject button while you are part-way through your set of 'dump's . if you want to you can easily re-enable the button.. (try mt -f /dev/nrst0 offline) > [3][snip] > [2]I have been using the DAT drive for about four years under SCO UNIX with > [2]their standard driver, so I know that the drive works well. it's working ok, we just expect it to actidifferently than you do.. > > [3] the wangdat drive may have broken firmware...my toshiba cdrom > [3]does. i had to patch the kernel to overcome it...the drive claimed to be > [3]a hard disk! how about sending in the dmesg output, boot with -v, please. what devices are you using? read the man page for st ( man 4 st) read carefully about a 'mount session' and tapes. As long as a mount session is in progress the 'eject' button is dissabled This is as it should be End the mount session by: accessing /dev/rst0 (not nrst0) using the mt command to take the tape offline. +----------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / On assignment | / \ julian@ref.tfs.com +------>x USA \ in a very strange | ( OZ ) 300 lakeside Dr. oakland CA. \___ ___ | country ! +- X_.---._/ USA+(510) 645-3137(wk) \_/ \\ v From owner-freebsd-current Sun Oct 29 19:38:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA27978 for current-outgoing; Sun, 29 Oct 1995 19:38:24 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA27966 for ; Sun, 29 Oct 1995 19:38:20 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id TAA09564; Sun, 29 Oct 1995 19:34:38 -0800 From: Julian Elischer Message-Id: <199510300334.TAA09564@ref.tfs.com> Subject: Re: Ports - What is the standard for "ported"? To: jmb@kryten.atinc.com (Jonathan M. Bresler) Date: Sun, 29 Oct 1995 19:34:38 -0800 (PST) Cc: uhclem%nemesis@fw.ast.com, current@freebsd.org In-Reply-To: from "Jonathan M. Bresler" at Oct 29, 95 03:42:52 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1230 Sender: owner-current@freebsd.org Precedence: bulk > > On Sun, 29 Oct 1995, Frank Durda IV wrote: > > > a WangDAT tape drive that under 2.0.5 won't let you remove the media until > > you reboot the system, OR you can issue a mt offline, remove the media, and > > then reboot to get the drive to load new media - that really stinks and > > this problem must be unique to WangDAT or at least non-exabyte > 4mm tape drives. i use a 4mm for daily backup. unload the tape with > "/usr/bin/mt -f /dev/rst0 rewoffl". load a new tape every morning and > haev no problems at all. > > here is my dump.4mm script (the rewind gets the tape started, > should not be needed but is, alas) > > #!/bin/sh > echo "" >> dump.log > echo "" >> dump.log > echo "" >> dump.log > /usr/bin/mt -f /dev/rst0 rewind > /sbin/dump 0unBbf 1200000 10 /dev/nrst0 /dev/sd1a 2>&1 | tee -a ^^^^^^^^^^ this dissables the button > /root/dump.log > /sbin/dump 0unBbf 1200000 10 /dev/nrst0 /dev/sd1e 2>&1 | tee -a > /root/dump.log > /sbin/dump 0unBbf 1200000 10 /dev/rst0 /dev/sd1f 2>&1 | tee -a ^^^^^^^^ this enables it again (on close) > /root/dump.log > /usr/bin/mt -f /dev/rst0 rewoffl ^^^^^^^^ so does this > From owner-freebsd-current Sun Oct 29 19:43:17 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA28196 for current-outgoing; Sun, 29 Oct 1995 19:43:17 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA28188 for ; Sun, 29 Oct 1995 19:43:12 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id TAA09588; Sun, 29 Oct 1995 19:39:37 -0800 From: Julian Elischer Message-Id: <199510300339.TAA09588@ref.tfs.com> Subject: Re: Ports - What is the standard for "ported"? To: uhclem%nemesis@fw.ast.com (Frank Durda IV) Date: Sun, 29 Oct 1995 19:39:37 -0800 (PST) Cc: current@freebsd.org In-Reply-To: from "Frank Durda IV" at Oct 29, 95 02:11:00 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 902 Sender: owner-current@freebsd.org Precedence: bulk > > I recently (and am still) going through a rather agonizing migration > of a SCO UNIX system to FreeBSD 2.0.5. > > Apart from lots of issues with SCSI hardware that SCO took in stride and > FreeBSD hated ("unknown board" errors for an Adaptec 1540A, which is one > of the non-thru-hole, 2nd generation surface-mount boards, I BELIEVE this is fixed, they bumped the board-id code and we didn't recognise it (3 line fix). > dealing with > a WangDAT tape drive that under 2.0.5 won't let you remove the media until > you reboot the system, OR you can issue a mt offline, remove the media, and > then reboot to get the drive to load new media - that really stinks and > didn't happen under SCO and I hope it is fixed in 2.1.0), I ran into a lot > of application issues. Are you saying that a mt -f /dev/nrst0 offline stops the tape from ever working again? I've never heard that before.. julian From owner-freebsd-current Sun Oct 29 21:54:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA05136 for current-outgoing; Sun, 29 Oct 1995 21:54:16 -0800 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA05131 for ; Sun, 29 Oct 1995 21:54:10 -0800 Received: (from nate@localhost) by trout.sri.MT.net (8.6.12/8.6.12) id WAA17937; Sun, 29 Oct 1995 22:53:08 -0700 Message-Id: <199510300553.WAA17937@trout.sri.MT.net> From: nate@trout.sri.MT.net (Nate Williams) Date: Sun, 29 Oct 1995 22:53:07 WET In-Reply-To: Michael Smith "Re: Cronjob error" (Oct 30, 12:05pm) X-Mailer: Mail User's Shell (7.2.6 (dynamic) alpha(3) 7/19/95) To: Michael Smith Subject: Re: Cronjob error Cc: ache@astral.msk.su, current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk [ Weekly cron job ] > > > >> TERM: Undefined variable. > > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > > cron uses sh not csh, unless you've set SHELL in the crontab. Ahh, but the locate command uses csh. However, it doesn't read from ~/.cshrc. Weirder and weirder... Nate From owner-freebsd-current Sun Oct 29 22:15:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA06197 for current-outgoing; Sun, 29 Oct 1995 22:15:33 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id WAA06184 for ; Sun, 29 Oct 1995 22:15:29 -0800 Received: from fw.ast.com by ast.com with SMTP id AA11184 (5.67b/IDA-1.5 for ); Sun, 29 Oct 1995 22:16:33 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0t9n8q-000089C; Sun, 29 Oct 95 23:52 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0t9n5Z-000Ix6C; Sun, 29 Oct 95 23:48 WET Message-Id: Date: Sun, 29 Oct 95 23:48 WET To: julian@ref.tfs.com From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Sun Oct 29 1995, 23:48:52 CST Subject: Re: WangDAT & FreeBSD strangeness Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk [0]I recently (and am still) going through a rather agonizing migration [0]of a SCO UNIX system to FreeBSD 2.0.5. [0] [0]Apart from lots of issues with SCSI hardware that SCO took in stride and [0]FreeBSD hated ("unknown board" errors for an Adaptec 1540A, which is one [0]of the non-thru-hole, 2nd generation surface-mount boards, [1]julian@ref.tfs.com says: [1]I BELIEVE this is fixed, they bumped the board-id code and we didn't [1]recognise it (3 line fix). [0]dealing with [0]a WangDAT tape drive that under 2.0.5 won't let you remove the media until [0]you reboot the system, OR you can issue a mt offline, remove the media, and [0]then reboot to get the drive to load new media - that really stinks and [0]didn't happen under SCO and I hope it is fixed in 2.1.0), I ran into a lot [0]of application issues. [1]julian@ref.tfs.com says: [1]Are you saying that a [1]mt -f /dev/nrst0 offline [1]stops the tape from ever working again? YES! Once you do a mt offline, that is it! END OF GAME! You must reboot or it won't even let you insert media in the drive. The drive refuses to load any new cartridges you stick in the door. You get one tape per boot. Under SCO, this does not happen. You said in a letter just before this that the way SCO handled tapes was broken compared to FreeBSD, but I sure prefer the SCO feature of being able to load more than one tape per system boot.... :-) SCO lets you unload media once the dev is closed - that doesn't seem so awful. A lot of CD-ROM drives and other peripherals use the same rule. Please see other mail on this subject that gives far more detail on the WangDAT-FreeBSD strangeness.... Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Sun Oct 29 22:41:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA07123 for current-outgoing; Sun, 29 Oct 1995 22:41:30 -0800 Received: from gwydion.HNS.St-Louis.Mo.US (root@dialup-64.icon-stl.net [199.217.153.64]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA07118 ; Sun, 29 Oct 1995 22:41:26 -0800 Received: (from kenth@localhost) by gwydion.HNS.St-Louis.Mo.US (8.6.12/8.6.12) id AAA16262; Mon, 30 Oct 1995 00:41:10 -0600 From: Kent Hamilton Message-Id: <199510300641.AAA16262@gwydion.HNS.St-Louis.Mo.US> Subject: Re: stable general protection fault in last kernel To: ache@astral.msk.su (=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=) Date: Mon, 30 Oct 1995 00:41:09 -0600 (CST) Cc: current@freebsd.org, davidg@freebsd.org In-Reply-To: from "=?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=" at Oct 29, 95 02:54:32 pm Reply-To: Kent.Hamilton@HNS.St-Louis.Mo.US Organization: HNS Consulting X-Location: St. Peters, MO USA X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1072 Sender: owner-current@freebsd.org Precedence: bulk According to =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?=: > > Building from today's sources I can easily got > Well, I have been building about once a week so I'm not much help but I tried picking up -current Sat morning (*early*) and I haven't gotten a clean system since. I'm running on a kernel from a week ago right now. The one as of yesterday morning panics with a paging error in kadmind, or grep, or any of a bunch of other places. Also appears that the atapi/wcd support no longer works as either a module or static. Same with some of the other lkm stuff. (Screen savers, etc.) I know that there has been some cleanup being done in that area, but just thought I'd mention it. I didn't get a stack trace of the panic, I've spent all day just trying to get a running system again to try and sup the latest diffs to see if that fixes the problem. I'm doing a make world now so we'll see. -- Kent Hamilton Work: KHamilton@Hunter.COM URL: http://www.icon-stl.net/~khamilto Play: KentH@HNS.St-Louis.Mo.US From owner-freebsd-current Mon Oct 30 00:24:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA11640 for current-outgoing; Mon, 30 Oct 1995 00:24:16 -0800 Received: from dracos.teton.com (dracos.teton.com [198.68.174.67]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA11617 for ; Mon, 30 Oct 1995 00:24:10 -0800 Received: (from root@localhost) by dracos.teton.com (8.6.12/8.6.12) id QAA01680 for freebsd-current@freebsd.org; Sun, 29 Oct 1995 16:23:43 -0800 From: Dan Sherwin Message-Id: <199510300023.QAA01680@dracos.teton.com> Subject: Lost my LP driver for HP-LJ4L To: freebsd-current@freebsd.org Date: Sun, 29 Oct 1995 16:23:42 -0800 (PST) In-Reply-To: <199510300641.AAA16262@gwydion.HNS.St-Louis.Mo.US> from "Kent Hamilton" at Oct 30, 95 00:41:09 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 253 Sender: owner-current@freebsd.org Precedence: bulk Well, I did it again. I rebuilt my system with current, and I forgot to keep a copy of my lp driver that was given to me from this list, for my HP LJ-4L. I can't print anything to it without it. Does anyone have that driver readily available? }Dan From owner-freebsd-current Mon Oct 30 01:25:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA14299 for current-outgoing; Mon, 30 Oct 1995 01:25:24 -0800 Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id BAA14294 for ; Mon, 30 Oct 1995 01:25:21 -0800 Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0t9qT0-0003wuC; Mon, 30 Oct 95 01:25 PST Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id MAA11753; Sat, 28 Oct 1995 12:39:02 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: davidg@Root.COM cc: uhclem%nemesis@fw.ast.com (Frank Durda IV), current@freebsd.org Subject: Re: Support for WD8003E abandoned? In-reply-to: Your message of "Sun, 29 Oct 1995 01:14:19 PST." <199510290914.BAA03454@corbin.Root.COM> Date: Sat, 28 Oct 1995 12:38:59 +0100 Message-ID: <11751.814880339@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk > >I tried the same thing on 2.1.0-951026-SNAP on three WD8003EB boards > >I have around here. They are all detected, but none work! > > I'm surprised to hear this, but it has been a long time since I > specifically tested 8bit wd8003e's. Still, I can't think of any changes to I saw the same thing and only because I thought I might need the ability to install a custom BIOS-ROM in a system did I not toss the card... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Mon Oct 30 02:04:40 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA16059 for current-outgoing; Mon, 30 Oct 1995 02:04:40 -0800 Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id CAA16049 for ; Mon, 30 Oct 1995 02:04:38 -0800 Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0t9qRh-0003w9C; Mon, 30 Oct 95 01:23 PST Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id SAA12580 for ; Sat, 28 Oct 1995 18:33:09 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: current@freebsd.org Subject: math_emulate LKM ? Date: Sat, 28 Oct 1995 18:33:07 +0100 Message-ID: <12578.814901587@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org Precedence: bulk Who's going to make a math_emulate LKM ? -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Just that: dried leaves in boiling water ? From owner-freebsd-current Mon Oct 30 05:01:23 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id FAA21551 for current-outgoing; Mon, 30 Oct 1995 05:01:23 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id FAA21546 for ; Mon, 30 Oct 1995 05:01:18 -0800 Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id IAA17865; Mon, 30 Oct 1995 08:04:04 -0500 From: Peter Dufault Message-Id: <199510301304.IAA17865@hda.com> Subject: Should 1540A be de-supported? To: julian@ref.tfs.com (Julian Elischer) Date: Mon, 30 Oct 1995 08:04:04 -0500 (EST) Cc: uhclem%nemesis@fw.ast.com, current@freebsd.org In-Reply-To: <199510300339.TAA09588@ref.tfs.com> from "Julian Elischer" at Oct 29, 95 07:39:37 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1510 Sender: owner-current@freebsd.org Precedence: bulk > > Apart from lots of issues with SCSI hardware that SCO took in stride and > > FreeBSD hated ("unknown board" errors for an Adaptec 1540A, which is one > > of the non-thru-hole, 2nd generation surface-mount boards, > > I BELIEVE this is fixed, they bumped the board-id code and we didn't > recognise it (3 line fix). The 1540A should still not work as poorly as it has in recent (post clustering) kernels. I don't think the 1540A is usable without fixes, and should probably be de-supported until it works properly It doesn't support as many scatter gather pages (I'm a little fuzzy on this) as the other boards, and newer versions of the OS generate large transfers that fail. 2.1: probably it should be de-supported in 2.1, since if it is going to trash people they are better off just not having it work. Here is some of what we recognize directly: ... > case 0x31: return "AHA-1540"; /* '1' */ > case 0x41: return "AHA-154x[AB]"; /* 'A' */ > case 0x42: return "AHA-1640"; ... There is a hole between 0x31 and 0x41 where odd revs of the 1540A's could sneak in. (We now treat anything from 0x47 and 0x56 as probably some kind of a newly released 1542.) If Frank is willing it would be useful to recompile aha1542.c with AHADEBUG and then boot verbosely and see what is going on. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Mon Oct 30 07:45:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA26917 for current-outgoing; Mon, 30 Oct 1995 07:45:24 -0800 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA26904 for ; Mon, 30 Oct 1995 07:45:20 -0800 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id KAA04190; Mon, 30 Oct 1995 10:31:34 -0500 Date: Mon, 30 Oct 1995 10:31:33 -0500 (EST) From: "Jonathan M. Bresler" Subject: Re: WangDAT & FreeBSD strangeness To: Frank Durda IV cc: julian@ref.tfs.com, current@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Sun, 29 Oct 1995, Frank Durda IV wrote: > > [1]julian@ref.tfs.com says: > [1]Are you saying that a > [1]mt -f /dev/nrst0 offline > [1]stops the tape from ever working again? > > YES! Once you do a mt offline, that is it! END OF GAME! You must > reboot or it won't even let you insert media in the drive. The > drive refuses to load any new cartridges you stick in the door. You > get one tape per boot. Under SCO, this does not happen. if you use '/usr/bin/mt -f /dev/rst0 rewoffl'. you can load as many tapes as you like. Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Mon Oct 30 12:49:31 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA14962 for current-outgoing; Mon, 30 Oct 1995 12:49:31 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA14957 for ; Mon, 30 Oct 1995 12:49:22 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA06584 for current@freebsd.org; Mon, 30 Oct 1995 13:39:09 -0700 From: Terry Lambert Message-Id: <199510302039.NAA06584@phaeton.artisoft.com> Subject: *MORE* FS problems, please fix! To: current@freebsd.org Date: Mon, 30 Oct 1995 13:39:09 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1857 Sender: owner-current@freebsd.org Precedence: bulk Well, if I can't get patches committed, the least I can do is complain about problems and hope someone else can get their possibly identical patches committed instead. The spotlight this time is on file locking. The locking subsystem is *incorrectly* implementing locking via a call to vn_* from the file system specific lock code. The design says that the FS specific lock code is, in fact, advisory. This means that the locking should be implemented at a higher layer (in the system call implementations), and then the FS specific lock code called if the lock is granted at the higher layer. Basically, this means the for most file systems, the lock calls should be simple success returns. The exception is NFS, which must assert a lock remotely. For file systems where the FS spcific locking code is non-null, a failure return for the FS specific locking code means back off the already granted lock at the higher level. This has the decided advantage of causing the FS to not "go remote" if a local conflict exists: a local conflict will result in a remote conflict anyway. It also means that FS layering is possible without afailure in the lock case. Currently, a lock asserted at one layer would cause a failure on the assertion at a lower layer (worst case) or a duplicate assertion (best case). For remote file systems (DOS/NetWare/LanMan) where overlapping lock regions are not coelesced, either one is fatal. Whoever reimplements this change (my patches aren't "good enough") should note that it will be about as large in scope as the patches I already submitted for FS layering. This means that you probably don't stand a chance of success unless you have commit priveledges. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon Oct 30 20:19:58 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA10738 for current-outgoing; Mon, 30 Oct 1995 20:19:58 -0800 Received: from chrome.jdl.com (chrome.onramp.net [199.1.166.202]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA10727 for ; Mon, 30 Oct 1995 20:19:52 -0800 Received: from localhost.jdl.com (localhost.jdl.com [127.0.0.1]) by chrome.jdl.com (8.6.11/8.6.9) with SMTP id WAA19702; Mon, 30 Oct 1995 22:18:43 -0600 Message-Id: <199510310418.WAA19702@chrome.jdl.com> X-Authentication-Warning: chrome.jdl.com: Host localhost.jdl.com didn't use HELO protocol To: Terry Lambert cc: current@freebsd.org Subject: Re: *MORE* FS problems, please fix! In-reply-to: Your message of "Mon, 30 Oct 1995 13:39:09 MST." <199510302039.NAA06584@phaeton.artisoft.com> Reply-To: jdl@chromatic.com Clarity-Index: null Threat-Level: none Software-Engineering-Dead-Seriousness: There's no excuse for unreadable code. Net-thought: If you meet the Buddha on the net, put him in your Kill file. Date: Mon, 30 Oct 1995 22:18:42 -0600 From: Jon Loeliger Sender: owner-current@freebsd.org Precedence: bulk Apparently, Terry Lambert scribbled: > > Well, if I can't get patches committed, the least I can do is > complain about problems and hope someone else can get their possibly > identical patches committed instead. > > ... > > Whoever reimplements this change (my patches aren't "good enough") > should note that it will be about as large in scope as the patches > I already submitted for FS layering. This means that you probably > don't stand a chance of success unless you have commit priveledges. Wait. I don't get it. I've been using FreeBSD for a solid year. I've been watching this list for just under a year. I've personally noted that almost everything Terry has said has had some kernel of truth to it even if he had to argue his point *again* and *again*. And maybe some of it was tainted with personal agenda occasionally, but we all do that to a certain extent. Nevertheless, I'm quite at a loss to understand why either: 1) He feels his patches are "good enough", or 2) His patches *aren't* good enough. I confess to being a bit out of sorts on the technical aspects of File Systems. I know FS code to the level presented in, say, the XINU book. All I can see is that he consistently has a good grasp on the technical issues here. I further don't understand, or know enough history to know why certain other members of the FreeBSD team feel he shouldn't be given commit privs. I don't need to know; their reasons are probably sound -- if there was a "conflict of interest" reason, that's pretty sound. But I don't know why he's having problems getting patches or code accepted for general use. Am I missing something fundamental? I don't think should piss Terry off and have him leave the FreeBSD project in a huff. It just wouldn't be right. So where are the negative vibes coming from, Moriarty? jdl From owner-freebsd-current Mon Oct 30 20:56:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA13749 for current-outgoing; Mon, 30 Oct 1995 20:56:14 -0800 Received: (from dyson@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA13740 ; Mon, 30 Oct 1995 20:56:10 -0800 From: John Dyson Message-Id: <199510310456.UAA13740@freefall.freebsd.org> Subject: Re: *MORE* FS problems, please fix! To: jdl@chromatic.com Date: Mon, 30 Oct 1995 20:56:10 -0800 (PST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <199510310418.WAA19702@chrome.jdl.com> from "Jon Loeliger" at Oct 30, 95 10:18:42 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2993 Sender: owner-current@freebsd.org Precedence: bulk > > Apparently, Terry Lambert scribbled: > > > > Well, if I can't get patches committed, the least I can do is > > complain about problems and hope someone else can get their possibly > > identical patches committed instead. > > > > ... > > > > Whoever reimplements this change (my patches aren't "good enough") > > should note that it will be about as large in scope as the patches > > I already submitted for FS layering. This means that you probably > > don't stand a chance of success unless you have commit priveledges. > Such bitterness is not appropriate or called for. Any changes that are based upon Terrys' work will give him credit -- even if they are not identical!!! There is lots of stuff going on right now and I want to review the stuff before committing it. For the first two years that I was on the FreeBSD team, I did not commit any code at all. Everything was subject to review, in fact I demanded it -- and grossly overloaded David in the process. > > Wait. I don't get it. I've been using FreeBSD for a solid year. > I've been watching this list for just under a year. I've personally > noted that almost everything Terry has said has had some kernel of > truth to it even if he had to argue his point *again* and *again*. > And maybe some of it was tainted with personal agenda occasionally, > but we all do that to a certain extent. > Terry does have some very interesting ideas -- and sometimes I enjoy reading his discussions. Since one person on the team had problems testing the specific changes in question, I would like to verify and check them out. If I don't David would!!! Note that even though I respect him (and others on the team do also), sometimes various people don't always agree with his positions. That is okay though, David doesn't always agree with mine also!!! > > Nevertheless, I'm quite at a loss to understand why either: > > 1) He feels his patches are "good enough", or > > 2) His patches *aren't* good enough. > It looks like the patches might be out-of-date, but they are still interesting. > > Am I missing something fundamental? I don't think should piss > Terry off and have him leave the FreeBSD project in a huff. It > I don't want to "piss" Terry off either, but I haven't included any structural changes without peer-review, and I am not likely to either. You would not believe DG's and my phone bills. Mine has been as high as $600/mo talking to DG!!! Not because DG is "better" than me or more "experienced" than me (he isn't, he is different than me and can spend more time thinking about architectural issues than I can sometimes), but I do talk to him ALOT, keeping him up-to-date on proposed changes. > > just wkouldn't be right. So where are the negative vibes coming > from, Moriarty? > I think the problem is with mis-communication and mis-understanding on the part of the parties involved. IT will work out, because the parties do have the best intentions. John dyson@freebsd.org From owner-freebsd-current Mon Oct 30 23:22:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA25285 for current-outgoing; Mon, 30 Oct 1995 23:22:26 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA25275 for ; Mon, 30 Oct 1995 23:22:24 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id XAA14908; Mon, 30 Oct 1995 23:21:53 -0800 From: Julian Elischer Message-Id: <199510310721.XAA14908@ref.tfs.com> Subject: Re: *MORE* FS problems, please fix! To: terry@lambert.org (Terry Lambert) Date: Mon, 30 Oct 1995 23:21:53 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199510302039.NAA06584@phaeton.artisoft.com> from "Terry Lambert" at Oct 30, 95 01:39:09 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3829 Sender: owner-current@freebsd.org Precedence: bulk > > > Well, if I can't get patches committed, the least I can do is > complain about problems and hope someone else can get their possibly > identical patches committed instead. Actually terry, I am packratting your patches as are john and david.. I fully intend on getting either THEM or a variant into the tree. there are a couple of things in the way:A Bruce, and a couple of other people have asked that we not stir up that pot at the moment as there are various changes 'out' but pending, and changes applied now just make things harder. john has said to me and others that he wants to take your patches and integrate them into a larger set of patches he's scheming on.. As he's the prime heavy in that area I cede to him and his requests but please don't for one minute think we are ignoring you or your patches. I personally are tired of the "please hold off, I got patches outstanding appeal" and When I go back to OZ in 6 weeks I'm going to be active in the tree the likes of I can only dream of at the moment with this albatros of a project hanging around my neck at work.. don't give up on us yet.. we all hold you in enough esteem to not dismiss anything you say, (though you seem to be in so many OS's that sometimes you get confused about which does what..) :) > > > The spotlight this time is on file locking. > > The locking subsystem is *incorrectly* implementing locking via a > call to vn_* from the file system specific lock code. > > > The design says that the FS specific lock code is, in fact, advisory. > > This means that the locking should be implemented at a higher layer > (in the system call implementations), and then the FS specific lock > code called if the lock is granted at the higher layer. > > Basically, this means the for most file systems, the lock calls should > be simple success returns. > > The exception is NFS, which must assert a lock remotely. > > For file systems where the FS spcific locking code is non-null, a > failure return for the FS specific locking code means back off the > already granted lock at the higher level. > > This has the decided advantage of causing the FS to not "go remote" > if a local conflict exists: a local conflict will result in a remote > conflict anyway. > > It also means that FS layering is possible without afailure in the > lock case. Currently, a lock asserted at one layer would cause a > failure on the assertion at a lower layer (worst case) or a duplicate > assertion (best case). > > For remote file systems (DOS/NetWare/LanMan) where overlapping lock > regions are not coelesced, either one is fatal. > > > Whoever reimplements this change (my patches aren't "good enough") > should note that it will be about as large in scope as the patches > I already submitted for FS layering. This means that you probably > don't stand a chance of success unless you have commit priveledges. I don't thisnk that your patches aren't good enough terry.. the trouble is that we all try to not commit code that has not had a second set of eyes pass over it, and you tend to be submitting code that can't be looked at 'quickly'. You are hacking around in the most sensitive area of the system and 1/ it takes time to check your changes .. ( 2/ there aren't that many people who feel comfortable in claiming that they know enough about it to judge it.. basically the 2.1 release saga has got us pretty much on hold due to personnel shortage.. > > I DO understand how you feel about it and do think that what we really need is a way that we can ensure that these type sof things can be passed by the right people for comment and actually get the comments required.. > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > From owner-freebsd-current Mon Oct 30 23:26:39 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA25613 for current-outgoing; Mon, 30 Oct 1995 23:26:39 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA25604 for ; Mon, 30 Oct 1995 23:26:36 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id XAA14925; Mon, 30 Oct 1995 23:25:42 -0800 From: Julian Elischer Message-Id: <199510310725.XAA14925@ref.tfs.com> Subject: Re: *MORE* FS problems, please fix! To: dyson@freefall.freebsd.org (John Dyson) Date: Mon, 30 Oct 1995 23:25:42 -0800 (PST) Cc: jdl@chromatic.com, terry@lambert.org, current@freebsd.org In-Reply-To: <199510310456.UAA13740@freefall.freebsd.org> from "John Dyson" at Oct 30, 95 08:56:10 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 888 Sender: owner-current@freebsd.org Precedence: bulk > > > > > > I don't want to "piss" Terry off either, but I haven't included > any structural changes without peer-review, and I am not likely > to either. You would not believe DG's and my phone bills. Mine > has been as high as $600/mo talking to DG!!! Not because DG is > "better" than me or more "experienced" than me (he isn't, he is > different than me and can spend more time thinking about architectural > issues than I can sometimes), but I do talk to him ALOT, keeping him > up-to-date on proposed changes. I think this is what we need with terry sometimes. he seems 'out of the loop' too much > I think the problem is with mis-communication and mis-understanding > on the part of the parties involved. IT will work out, because the > parties do have the best intentions. well that's true.. I know I want terry on our team not working off on his own somewhere.. julian From owner-freebsd-current Mon Oct 30 23:27:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA25717 for current-outgoing; Mon, 30 Oct 1995 23:27:28 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA25705 for ; Mon, 30 Oct 1995 23:27:25 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id XAA12663; Mon, 30 Oct 1995 23:27:00 -0800 To: Julian Elischer cc: terry@lambert.org (Terry Lambert), current@freebsd.org Subject: Re: *MORE* FS problems, please fix! In-reply-to: Your message of "Mon, 30 Oct 1995 23:21:53 PST." <199510310721.XAA14908@ref.tfs.com> Date: Mon, 30 Oct 1995 23:27:00 -0800 Message-ID: <12661.815124420@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org Precedence: bulk > we all hold you in enough esteem to not dismiss anything you say, ^^^^^^^^ Ahem.. That's "everything", Julian.. :-) Jordan From owner-freebsd-current Tue Oct 31 06:25:51 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA15885 for current-outgoing; Tue, 31 Oct 1995 06:25:51 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id GAA15878 for ; Tue, 31 Oct 1995 06:25:48 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id GAA02483; Tue, 31 Oct 1995 06:25:47 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id GAA09530; Tue, 31 Oct 1995 06:21:27 -0800 Message-Id: <199510311421.GAA09530@corbin.Root.COM> To: Terry Lambert cc: current@freebsd.org Subject: Re: *MORE* FS problems, please fix! In-reply-to: Your message of "Mon, 30 Oct 95 13:39:09 MST." <199510302039.NAA06584@phaeton.artisoft.com> From: David Greenman Reply-To: davidg@Root.COM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 31 Oct 1995 06:21:27 -0800 Sender: owner-current@freebsd.org Precedence: bulk > The locking subsystem is *incorrectly* implementing locking via a > call to vn_* from the file system specific lock code. > > > The design says that the FS specific lock code is, in fact, advisory. Advisory locks *are* advisory. The advisory locking is implemented via VOP_ADVLOCK() in the appropriate system calls. Is this another case where you completely misunderstand, at the most fundamental level, how the code works? If you're looking at VOP_LOCK/VOP_UNLOCK and thinking that these have something to do with file locking, look again, they don't. -DG From owner-freebsd-current Tue Oct 31 09:24:54 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA08478 for current-outgoing; Tue, 31 Oct 1995 09:24:54 -0800 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA08473 ; Tue, 31 Oct 1995 09:24:51 -0800 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id JAA08504; Tue, 31 Oct 1995 09:59:53 -0800 Message-Id: <199510311759.JAA08504@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: current@FreeBSD.org cc: wollman@FreeBSD.org Subject: Time problems Date: Tue, 31 Oct 1995 09:59:53 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org Precedence: bulk >I have purchase a FreeBSD version 2.0.5. When I boot up my machine with >the boot floop, it couldn't found my SCSI hard disk. I am using a mother >board with build-in AHA-2940. I have tried to use the "Config" utility to >alter the setting of my SCSI controller, however, I couldn't found the >device "ahc0" in the listing.("ahc0" is the device name of AHA-2940 >specified in the file "hardware") What's wrong with my kernel? Am I >purchased a wrong version of FreeBSD? Please help me to fixed this >problem because I am hurry to install the FreeBSD, thanks a lot! > >Regards, > >Samuel Chan >(Hong Kong) Are you sure that you have an aic7870 based motherboard control? It sounds like you have an aic7850 on your motherboard which is not (as yet) supported. -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Oct 31 09:48:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA11235 for current-outgoing; Tue, 31 Oct 1995 09:48:14 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA11228 ; Tue, 31 Oct 1995 09:48:10 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA29686; Tue, 31 Oct 1995 12:47:55 -0500 Date: Tue, 31 Oct 1995 12:47:55 -0500 From: "Garrett A. Wollman" Message-Id: <9510311747.AA29686@halloran-eldar.lcs.mit.edu> To: "Justin T. Gibbs" Cc: current@FreeBSD.org, wollman@FreeBSD.org Subject: Time problems In-Reply-To: <199510311759.JAA08504@aslan.cdrom.com> References: <199510311759.JAA08504@aslan.cdrom.com> Sender: owner-current@FreeBSD.org Precedence: bulk < said: > I rebuilt my kernel a few days ago. I hadn't changed it for ~1 month. > Ever since, my system clock is running exceptionally fast (1 hour gained > every day). I know that this problem was brought up recently on the > lists, but I expected xntpd to over come the problem with Pentium > microtime. Unfortuantely that doesn't seem to be the case. Is anyone > working on fixing this problem or know why xntpd is ineffective? You must be one of the people who has a problem with the clock calibration. There are two possible sources of error involved here: 1) The part of your chipset that emulates the timer/counter is operating at the wrong rate (or the DELAY function isn't working right for it). 2) Your CPU's cycle counter is not operating at the nominal rate, or its rate in MHz is not close to an integer. In talking to David Greenman about this problem, we found that one of his machines which exhibits this problem suffers from (1). Other people have suggested (2) for their motherboards. (David's motherboard took about 12 seconds to perform a ten-second delay.) Here's one thing which you might try: In this function (in i386/isa/clock.c): ------------------------------------ calibrate_cyclecounter(void) { /* * Don't need volatile; should always use unsigned if 2's * complement arithmetic is desired. */ unsigned long long count; __asm __volatile(".byte 0x0f, 0x30" : : "A"(0LL), "c" (0x10)); DELAY(1000000); __asm __volatile(".byte 0xf,0x31" : "=A" (count)); /* * XX lose if the clock rate is not nearly a multiple of 1000000. */ pentium_mhz = (count + 500000) / 1000000; } ------------------------------------ Change the occurrences of `1000000' to `10000' and `500000' to `5000'. This will reduce the calibration time, which makes it more likely that the error in your clock will be small enough to get rounded off. If that doesn't work, then just #ifdef out the body of the function, which will cause the 8254-alike to act as the reference for timekeeping. Needless to say, on the three different motherboards we have here (60, 100, and 120-MHz CPUs), we have never seen this problem, so it's a bit hard to diagnose. For those machines on which the results are reasonable, I expect timekeeping to be rather better than it was. According to xntpd, my machine is within about 3 seconds per day, which is about the same as it was before. (It's the precision, rather than the accuracy, where this technique gives a benefit.) -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Oct 31 10:03:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA12510 for current-outgoing; Tue, 31 Oct 1995 10:03:53 -0800 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA12493 ; Tue, 31 Oct 1995 10:03:49 -0800 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id KAA08628; Tue, 31 Oct 1995 10:05:22 -0800 Message-Id: <199510311805.KAA08628@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: "Garrett A. Wollman" cc: "Justin T. Gibbs" , current@FreeBSD.org, wollman@FreeBSD.org Subject: Re: Time problems In-reply-to: Your message of "Tue, 31 Oct 1995 12:47:55 EST." <9510311747.AA29686@halloran-eldar.lcs.mit.edu> Date: Tue, 31 Oct 1995 10:05:22 -0800 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.org Precedence: bulk >If that doesn't work, then just #ifdef out the body of >the function, which will cause the 8254-alike to act as the reference >for timekeeping. Can we do occasional 8254 based sanity checking of the system time to either automatically revert to the 8254 on systems that the new code yields poor results, or simply to fix up the time occasionally? I thought the main reason for using this approach was to remove the overhead of going out to the 8254, so doing so only every once in a while gives the same type of reduction we have know, but should work on all systems that have a working 8254. >Needless to say, on the three different motherboards we have here >(60, 100, and 120-MHz CPUs), we have never seen this problem, so it's >a bit hard to diagnose. For those machines on which the results are >reasonable, I expect timekeeping to be rather better than it was. >According to xntpd, my machine is within about 3 seconds per day, >which is about the same as it was before. (It's the precision, rather >than the accuracy, where this technique gives a benefit.) > >-GAWollman Precision and overhead right? Why is it that xntpd doesn't either complain about my large offset (I started it just after using ntpdate), or keep my time in sync? >-- >Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... >wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. >Opinions not those of| It is a bond more powerful than absence. We like peopl >e >MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Tue Oct 31 10:07:07 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA13388 for current-outgoing; Tue, 31 Oct 1995 10:07:07 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA13294 for ; Tue, 31 Oct 1995 10:06:52 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA10220; Tue, 31 Oct 1995 10:55:22 -0700 From: Terry Lambert Message-Id: <199510311755.KAA10220@phaeton.artisoft.com> Subject: Re: *MORE* FS problems, please fix! To: davidg@root.com Date: Tue, 31 Oct 1995 10:55:21 -0700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: <199510311421.GAA09530@corbin.Root.COM> from "David Greenman" at Oct 31, 95 06:21:27 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 3002 Sender: owner-current@freebsd.org Precedence: bulk > > The locking subsystem is *incorrectly* implementing locking via a > > call to vn_* from the file system specific lock code. > > > > > > The design says that the FS specific lock code is, in fact, advisory. > > Advisory locks *are* advisory. The advisory locking is implemented via > VOP_ADVLOCK() in the appropriate system calls. Is this another case where > you completely misunderstand, at the most fundamental level, how the code > works? If you're looking at VOP_LOCK/VOP_UNLOCK and thinking that these have > something to do with file locking, look again, they don't. You are missing the distinction between "advisory locking" and "locking implementation is advisory in nature". The first is a given. The second, which is what I was talking about, is that the file locks implemented by ufs_lock/ufs_unlock and the advisory range locks that are implemented in ufs_advlock by calling lf_advlock are to be implemented using an assert/veto mechanism (and they are currently *not* implemented this way). Basically, in kern/vfs_syscalls and kern/kern_descrip.c: call underlying fs lock/unlock/getlock Needs to be changed to: switch(ap->a_op) { case F_SETLK: do lf_setlock if success call underlying fs lock if fail back out lf_setlock endif endif case F_UNLCK: verify existance using lf_getlock if exists call underlying fs unlock if success /* can not fail because of verification!*/ do lf_clearlock endif endif case F_GETLK: get lock using lf_getlock #ifdef REMOTE_RELEASE_ALLOWED get lock using underlying fs getlock if not_same force local coherency endif #endif /* REMOTE_RELEASE_ALLOWED*/ } The point being that for most of the "underlying fs's", the VOP_LOCK, VOP_UNLOCK, and VOP_ADVLOCK calls should always simply return success, unstead of relying on code that is potentially shared with other OS's (like Linux and SunOS) to implement locking using the same primitives. The underlying fs, though, does have the right to veto a lock, and though NFS does not support remote release coherency, some other FS or distributed computing environment might. Finally, the locks themselves should be hung off the vnode rather than the in core portion of the inode. This resolves the code duplication and coherency issues in asserting locking semantics uniformly across multiple disparate FS's. Tell me, does file and advisory locking work correctly in msdosfs, cd9660fs, ext2fs, etc.? It would if it used the same code even before the fs is called. Say we want to add support for mandatory locking because we want to run Xenix binaries. Should the support need to be added on a case by case basis to all underlying file systems? The answer, according to the Heidemann thesis, is "no". The same is true of the existing file and advisory locking implementation. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Oct 31 10:21:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA14312 for current-outgoing; Tue, 31 Oct 1995 10:21:33 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA14302 ; Tue, 31 Oct 1995 10:21:28 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA29851; Tue, 31 Oct 1995 13:21:08 -0500 Date: Tue, 31 Oct 1995 13:21:08 -0500 From: "Garrett A. Wollman" Message-Id: <9510311821.AA29851@halloran-eldar.lcs.mit.edu> To: "Justin T. Gibbs" Cc: "Garrett A. Wollman" , current@FreeBSD.org, wollman@FreeBSD.org Subject: Re: Time problems In-Reply-To: <199510311805.KAA08628@aslan.cdrom.com> References: <9510311747.AA29686@halloran-eldar.lcs.mit.edu> <199510311805.KAA08628@aslan.cdrom.com> Sender: owner-current@FreeBSD.org Precedence: bulk < said: > yields poor results, or simply to fix up the time occasionally? I > thought the main reason for using this approach was to remove the > overhead of going out to the 8254, No. The main reason for using this approach is to ensure that `time' is incremented at the right rate. Previously, if a clock interrupt was late, the system would make no attempt to correct for that fact. Now it does. (Yes, that's a fringe case, but it can be a significant source of jitter under the old mechanism.) I have considered a number of mechanisms which might automatically detect when this situation has occurred, but I still hold out hope that the underlying cause for the mis-diagnosis might be fixed and the extra overhead will not be necessary. Even under the `old' way the cycle counter was still being used for microtime(), and was still giving incorrect results on your machine. Now it's just a bit more obvious about it. You should have complained six months ago that your CPU speed was not being correctly diagnosed. > Precision and overhead right? No, just precision. The overhead is actually slightly increased, since before we never checked to see how much time really elapsed between timer ticks; now we do. > Why is it that xntpd doesn't either > complain about my large offset (I started it just after using ntpdate), > or keep my time in sync? xntpd won't complain about a large offset at any time other than startup, and your clock is off by so much that it exceeds the bounds of the correction mechanism (and may very well have xntpd completely confused). -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue Oct 31 10:33:31 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA15463 for current-outgoing; Tue, 31 Oct 1995 10:33:31 -0800 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA15432 ; Tue, 31 Oct 1995 10:33:17 -0800 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id NAA14659; Tue, 31 Oct 1995 13:33:01 -0500 Date: Tue, 31 Oct 1995 13:32:54 -0500 (EST) From: John Fieber X-Sender: jfieber@fieber-john.campusview.indiana.edu To: current@freebsd.org, stable@freebsd.org Subject: Make world tools target Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk I brought this up once before and it was not resolved and I think it will become a headache if it isn't resolved. For a variety of reasons, it is not possible generate and install the handbook and FAQ from either current or stable (2.1) on a 2.0.5 system. In fact, this will cause a make world to fall over. It was suggested that the generation of the docs be postponed to the install phase. This will not work because share/doc is installed before share/sgml and usr.bin/sgmlfmt. Until the processing procedures of sgml files stablizes, which I don't expect it will until after 2.2, I would recommend that usr.bin/sgmlfmt and share/sgml be installed in the tools target. (sgmlfmt is just a perl script, BTW.) This is important because a make world WILL FAIL for anyone anyone upgrading from 2.0.5 or earlier, to 2.1 (or current) by rebuilding from source. Once 2.1 hits the net, I expect a fair amount of mail will come in regarding this problem. -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-current Tue Oct 31 11:44:26 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA19581 for current-outgoing; Tue, 31 Oct 1995 11:44:26 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA19569 for ; Tue, 31 Oct 1995 11:44:13 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id MAA10342; Tue, 31 Oct 1995 12:30:03 -0700 From: Terry Lambert Message-Id: <199510311930.MAA10342@phaeton.artisoft.com> Subject: Re: *MORE* FS problems, please fix! To: dyson@freefall.freebsd.org (John Dyson) Date: Tue, 31 Oct 1995 12:30:02 -0700 (MST) Cc: jdl@chromatic.com, terry@lambert.org, current@freebsd.org In-Reply-To: <199510310456.UAA13740@freefall.freebsd.org> from "John Dyson" at Oct 30, 95 08:56:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 6875 Sender: owner-current@freebsd.org Precedence: bulk > > > Well, if I can't get patches committed, the least I can do is > > > complain about problems and hope someone else can get their possibly > > > identical patches committed instead. > > > > > > ... > > > > > > Whoever reimplements this change (my patches aren't "good enough") > > > should note that it will be about as large in scope as the patches > > > I already submitted for FS layering. This means that you probably > > > don't stand a chance of success unless you have commit priviledges. > > > Such bitterness is not appropriate or called for. Any changes > that are based upon Terrys' work will give him credit -- even if > they are not identical!!! There is lots of stuff going on right now > and I want to review the stuff before committing it. For the first two years > that I was on the FreeBSD team, I did not commit any code at all. Everything > was subject to review, in fact I demanded it -- and grossly overloaded > David in the process. The "bitterness" was conditional on the elided text. The phrasing of the parenthetical expression was intentional: it was meant to convey the point that if the patches were not "good enough" per the elided text's usage of the phrase, that something similar would have to be implemented anyway. Certainly eliding the text makes me seem more frustrated than I am. > > Wait. I don't get it. I've been using FreeBSD for a solid year. > > I've been watching this list for just under a year. I've personally > > noted that almost everything Terry has said has had some kernel of > > truth to it even if he had to argue his point *again* and *again*. > > And maybe some of it was tainted with personal agenda occasionally, > > but we all do that to a certain extent. > > Terry does have some very interesting ideas -- and sometimes I enjoy > reading his discussions. Since one person on the team had problems > testing the specific changes in question, I would like to verify and > check them out. If I don't David would!!! Note that even though I > respect him (and others on the team do also), sometimes various > people don't always agree with his positions. That is okay though, > David doesn't always agree with mine also!!! Paul was already doing this, at least at one time, thoguh it has several times gotten to the point of a one parenthesis or otherwise obvious change causing the full patch set to be rejected. I think that the correction of such minor things, especially if the review process is to be protracted as it has always been in the past, should not require rejecting the full patch set to the author. With -current, there is no hope of a patch set not based on the idea of a CVS merge being "correct" when it touches the system call interfaces and all of the underlying file systems. The addition of interfaces in the time between the production of the first set of patches and their "review" is what caused the initial failures. The reordering of read-only-file system rejection (actually, I think the reordering pushing it below the FS layer was correct: for union FS's, a union may comprise a RO FS and one or more RW FS's) was the reason for the second rejections. Part of the problem is that I can't run -current localy if I expect to be able to spend time coding instead of catching up. Probably the correct thing to do would be to have taken the patches vs. the revision tags, temporarily tagged a vendor branch, cvs ci'd the patched files into the branch, and merged the branch into the main line code. Either I'm considered responsible for checking in, or I'm considered responsible for keeping in sync with -current, but I can't do both. Part of my annoyance is that there is a 6-7 file threshold (easily overwhelmed by interface change patches like mine) after which it is impossible to keep -current with the update lag given the other activity in the tree. So I'm prepared to abdicate keeping up with -current in favor of allowing someone with commit privs to roll the changes forward in keeping with other peoples concurrent work in the affected areas. Before anyone goes off on a tear, this means I'm not willing to keep patches current over another six week period wherein they are constantly going out of date because of changes that don't undergo the same level of scrutiny. This doesn't mean that I won't keep hacking code, but it does mean that some of the stuff I do will be on a take-it-or-leave-it basis, and I don't care which you do. Instead, I'll probably concentrate on making sure the patches are applicable to any BSD 4.4 derived source base so that someone will use them somewhere. > It looks like the patches might be out-of-date, but they are still > interesting. It is impossible for patches to more than 3-4 files simultaneously to be anything *BUT* "out of date" without a CVS merge facility. I've been fighting a losing battle with demands that the patches apply cleanly to "this hours -current" when the revision tags should have been sufficient to "cvs merge" them in with a hell of a lot less effort than I've been expending. > > Am I missing something fundamental? I don't think should piss > > Terry off and have him leave the FreeBSD project in a huff. It > > I don't want to "piss" Terry off either, but I haven't included > any structural changes without peer-review, and I am not likely > to either. You would not believe DG's and my phone bills. Mine > has been as high as $600/mo talking to DG!!! Not because DG is > "better" than me or more "experienced" than me (he isn't, he is > different than me and can spend more time thinking about architectural > issues than I can sometimes), but I do talk to him ALOT, keeping him > up-to-date on proposed changes. I'm not pissed off. I'm just frustrated with a process that makes large scale contributions almost impossible to achieve for anyone without direct commit priviledges, through no lack of desire on my part. That's all. I'm not asking for commit priviledges, I'm asking for process change for patches from people without commit priviledges.. > > just wkouldn't be right. So where are the negative vibes coming > > from, Moriarty? > > I think the problem is with mis-communication and mis-understanding > on the part of the parties involved. IT will work out, because the > parties do have the best intentions. I've been chasing -current for six weeks now to get changes in that I require for additional work, which don't change the functionality directly, and which put the code in line with the FS design documents at ftp.cs.ucla.edu. I'm not going to hold additional work another six weeks. I agree with David, that it will work out one way or another; no one's intentions are in question. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Oct 31 13:22:01 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id NAA24624 for current-outgoing; Tue, 31 Oct 1995 13:22:01 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA24618 for ; Tue, 31 Oct 1995 13:21:57 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id NAA03286; Tue, 31 Oct 1995 13:20:21 -0800 Date: Tue, 31 Oct 1995 13:20:21 -0800 (PST) From: -Vince- To: current@FreeBSD.ORG Subject: FreeBSD 2.1 update Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk Greetings everyone, I was wondering what would need to be done to upgrade from FreeBSD -current to 2.1 and also, what is the proper and easiest way to compare the updated files in the /etc directory to my original /etc directory? Any help would be appreciated. Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Tue Oct 31 14:40:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA29056 for current-outgoing; Tue, 31 Oct 1995 14:40:52 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA29048 for ; Tue, 31 Oct 1995 14:40:48 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id OAA20598; Tue, 31 Oct 1995 14:39:51 -0800 From: Julian Elischer Message-Id: <199510312239.OAA20598@ref.tfs.com> Subject: Re: *MORE* FS problems, please fix! To: terry@lambert.org (Terry Lambert) Date: Tue, 31 Oct 1995 14:39:51 -0800 (PST) Cc: dyson@freefall.freebsd.org, jdl@chromatic.com, terry@lambert.org, current@freebsd.org In-Reply-To: <199510311930.MAA10342@phaeton.artisoft.com> from "Terry Lambert" at Oct 31, 95 12:30:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1477 Sender: owner-current@freebsd.org Precedence: bulk > Paul was already doing this, at least at one time, thoguh it has several > times gotten to the point of a one parenthesis or otherwise obvious > change causing the full patch set to be rejected. > > I think that the correction of such minor things, especially if the > review process is to be protracted as it has always been in the past, > should not require rejecting the full patch set to the author. > > With -current, there is no hope of a patch set not based on the idea > of a CVS merge being "correct" when it touches the system call interfaces > and all of the underlying file systems. [...] > > Before anyone goes off on a tear, this means I'm not willing to > keep patches current over another six week period wherein they are > constantly going out of date because of changes that don't undergo > the same level of scrutiny. terry If you wish I can give you a login on ref. ref has a cvs tree that is sync'd with freefall each night.. you can make as many trees as you want off that and use one for each set of changes.. that way you can be sure your changes are relative to -current (just do 'cvs update' before the 'cvs diff') It means that you will have a place to 'stage' your patches (or alternatively you could get the cvs tree yourself via ctm or sup, but I already have it set up) > > It is impossible for patches to more than 3-4 files simultaneously > to be anything *BUT* "out of date" without a CVS merge facility. which I'm offering julian From owner-freebsd-current Tue Oct 31 14:54:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA29520 for current-outgoing; Tue, 31 Oct 1995 14:54:52 -0800 Received: from cleat.irbs.com (cleat.irbs.com [199.182.75.131]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA29511 for ; Tue, 31 Oct 1995 14:54:47 -0800 Received: (from jc@localhost) by cleat.irbs.com (8.6.12/8.6.6) id RAA04214; Tue, 31 Oct 1995 17:53:24 -0500 From: John Capo Message-Id: <199510312253.RAA04214@cleat.irbs.com> Subject: Re: FreeBSD 2.1 update To: vince@apollo.COSC.GOV (-Vince-) Date: Tue, 31 Oct 1995 17:53:23 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: from "-Vince-" at Oct 31, 95 01:20:21 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 899 Sender: owner-current@FreeBSD.ORG Precedence: bulk -Vince- writes: > > Greetings everyone, > > I was wondering what would need to be done to upgrade from > FreeBSD -current to 2.1 and also, what is the proper and easiest way to > compare the updated files in the /etc directory to my original /etc > directory? Any help would be appreciated. > Just did that to two of my systems. Almost all -current utils work fine with a 2.1 kernel. mount_nfs was one that didn't. When I discovered that I built nfsiod and nfsd and booted the 2.1 kernel again. ps, pstat and top are some others that won't work. Once I had NFS going I just did a make world. diff -r /etc /usr/src/etc is one way. -current and 2.1 are pretty close /etc wise. John Capo jc@irbs.com IRBS Engineering High performance FreeBSD systems (305) 792-9551 Internet Consulting - ISP Solutions From owner-freebsd-current Tue Oct 31 15:34:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA02019 for current-outgoing; Tue, 31 Oct 1995 15:34:28 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA02008 for ; Tue, 31 Oct 1995 15:34:21 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id PAA05973; Tue, 31 Oct 1995 15:31:11 -0800 Date: Tue, 31 Oct 1995 15:31:10 -0800 (PST) From: -Vince- To: John Capo cc: current@FreeBSD.ORG Subject: Re: FreeBSD 2.1 update In-Reply-To: <199510312253.RAA04214@cleat.irbs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Tue, 31 Oct 1995, John Capo wrote: > -Vince- writes: > > > > Greetings everyone, > > > > I was wondering what would need to be done to upgrade from > > FreeBSD -current to 2.1 and also, what is the proper and easiest way to > > compare the updated files in the /etc directory to my original /etc > > directory? Any help would be appreciated. > > > > Just did that to two of my systems. Almost all -current utils > work fine with a 2.1 kernel. mount_nfs was one that didn't. When > I discovered that I built nfsiod and nfsd and booted the 2.1 kernel > again. ps, pstat and top are some others that won't work. Once > I had NFS going I just did a make world. Hmmm, so will sup actually upgrade the system to 2.1 sources? > diff -r /etc /usr/src/etc is one way. -current and 2.1 are pretty > close /etc wise. Hmmm, I mean like I noticed that -current had alot of updates on /etc which I am still using the 2.05R /etc files with a few updated but what do I do after the diff command? Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Tue Oct 31 16:09:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA03262 for current-outgoing; Tue, 31 Oct 1995 16:09:13 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA03233 for ; Tue, 31 Oct 1995 16:06:50 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id QAA10839; Tue, 31 Oct 1995 16:54:40 -0700 From: Terry Lambert Message-Id: <199510312354.QAA10839@phaeton.artisoft.com> Subject: Re: *MORE* FS problems, please fix! To: julian@ref.tfs.com (Julian Elischer) Date: Tue, 31 Oct 1995 16:54:39 -0700 (MST) Cc: terry@lambert.org, dyson@freefall.freebsd.org, jdl@chromatic.com, current@freebsd.org In-Reply-To: <199510312239.OAA20598@ref.tfs.com> from "Julian Elischer" at Oct 31, 95 02:39:51 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 383 Sender: owner-current@freebsd.org Precedence: bulk > (or alternatively you could get the cvs tree yourself via ctm or sup, > but I already have it set up) How do I sup the CVS tree? I don't lack disk space (I'm a file system geek, after all). I thought CTM was the only method, but it loses. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Oct 31 17:34:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA08241 for current-outgoing; Tue, 31 Oct 1995 17:34:46 -0800 Received: from eel.dataplex.net (EEL.DATAPLEX.NET [199.183.109.245]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA08226 for ; Tue, 31 Oct 1995 17:34:43 -0800 Received: from [199.183.109.242] (cod [199.183.109.242]) by eel.dataplex.net (8.6.11/8.6.9) with SMTP id TAA00895; Tue, 31 Oct 1995 19:34:17 -0600 X-Sender: rkw@shark.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 31 Oct 1995 19:34:17 -0600 To: Terry Lambert From: rkw@dataplex.net (Richard Wackerbarth) Subject: On the (lack of) reliability of CTM Cc: current@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk At 5:54 PM 10/31/95, Terry Lambert wrote: >How do I sup the CVS tree? I think they are in the process of fixing it so that you simply replace "release=current" with "release=cvs" in the sup files. At least that is the logical way to have it set up. Then someone in power will have to set up your permissions because the cvs tree is by invitation only. >I thought CTM was the only method, but it loses. I too, have noticed frequent lost updates (xxx-cur). What is the weak link that causes mail to get lost? Perhaps we need to add an ftp-by-mail daemon to allow those missing segments to be remailed. ---- Richard Wackerbarth rkw@dataplex.net From owner-freebsd-current Tue Oct 31 18:21:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA10339 for current-outgoing; Tue, 31 Oct 1995 18:21:29 -0800 Received: from irbs.irbs.com (irbs.com [199.182.75.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA10330 for ; Tue, 31 Oct 1995 18:21:23 -0800 Received: (from jc@localhost) by irbs.irbs.com (8.6.12/8.6.6) id VAA00668; Tue, 31 Oct 1995 21:20:06 -0500 From: John Capo Message-Id: <199511010220.VAA00668@irbs.irbs.com> Subject: Re: FreeBSD 2.1 update To: vince@apollo.COSC.GOV (-Vince-) Date: Tue, 31 Oct 1995 21:20:05 +1900 (EST) Cc: jc@irbs.com, current@FreeBSD.org In-Reply-To: from "-Vince-" at Oct 31, 95 03:31:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1784 Sender: owner-current@FreeBSD.org Precedence: bulk -Vince- writes: > > On Tue, 31 Oct 1995, John Capo wrote: > > > -Vince- writes: > > > > > > Greetings everyone, > > > > > > I was wondering what would need to be done to upgrade from > > > FreeBSD -current to 2.1 and also, what is the proper and easiest way to > > > compare the updated files in the /etc directory to my original /etc > > > directory? Any help would be appreciated. > > > > > > > Just did that to two of my systems. Almost all -current utils > > work fine with a 2.1 kernel. mount_nfs was one that didn't. When > > I discovered that I built nfsiod and nfsd and booted the 2.1 kernel > > again. ps, pstat and top are some others that won't work. Once > > I had NFS going I just did a make world. > > Hmmm, so will sup actually upgrade the system to 2.1 sources? The source tree for -stable is available via sup. -stable will be 2.1 very shortly. Look at /usr/src/share/examples/sup/*stable*. > > > diff -r /etc /usr/src/etc is one way. -current and 2.1 are pretty > > close /etc wise. > > Hmmm, I mean like I noticed that -current had alot of updates on > /etc which I am still using the 2.05R /etc files with a few updated but > what do I do after the diff command? > Yeah it does, more than I thought. Basically you have to merge in any changes you have made to your /etc files. Most likely candidates are passwd, group, rc, rc.local, sysconfig, sendmail.cf, and ttys. Save the files you have modified or the entire /etc direcctory. Update /etc by hand or look at the distribution target in /usr/src/etc/Makefile. John Capo jc@irbs.com IRBS Engineering High performance FreeBSD systems (305) 792-9551 Internet Consulting - ISP Solutions From owner-freebsd-current Tue Oct 31 19:51:05 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA14472 for current-outgoing; Tue, 31 Oct 1995 19:51:05 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA14458 for ; Tue, 31 Oct 1995 19:50:52 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id UAA11177; Tue, 31 Oct 1995 20:39:39 -0700 From: Terry Lambert Message-Id: <199511010339.UAA11177@phaeton.artisoft.com> Subject: Re: On the (lack of) reliability of CTM To: rkw@dataplex.net (Richard Wackerbarth) Date: Tue, 31 Oct 1995 20:39:39 +1700 (MST) Cc: terry@lambert.org, current@freebsd.org In-Reply-To: from "Richard Wackerbarth" at Oct 31, 95 07:34:17 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2078 Sender: owner-current@freebsd.org Precedence: bulk > At 5:54 PM 10/31/95, Terry Lambert wrote: > >How do I sup the CVS tree? > > I think they are in the process of fixing it so that you simply replace > "release=current" with "release=cvs" in the sup files. At least that is the > logical way to have it set up. > Then someone in power will have to set up your permissions because the cvs > tree is by invitation only. Well, I'm only interested in read-only access for a cvs diff -r tag -c for a tag on my branch vs. -current (the default tag) to automatically generate my diff's for me instead of having to do it by hand with several finds and awk and sed scripts. A CVS merge and/or cvs -n update would reduce my effort immensely, which would in turn make my diffs "fresher" and more likely to be rolled in. > >I thought CTM was the only method, but it loses. > > I too, have noticed frequent lost updates (xxx-cur). What is the weak link > that causes mail to get lost? > > Perhaps we need to add an ftp-by-mail daemon to allow those missing > segments to be remailed. My problem with CTM is that it doesn't do relative inserts instead of replacing parts of the tree. That means rather than a database merge, I get an updated database. The problem with that approach is that it puts me in exactly the same boat as sup'ping -current, since I will lose any locally generated branch tags. Sup'ping cvs actually is only marginally better, and requires me to keep a local branch. Using two staggered tags and a hellacious update with duplicate tree revisions locally, I could *almost* get the same functionality as a local vendor tag from sup'ping cvs. I really need local tag merge/diff. CTM would require a local rewrite to get the same functionality. 8-(. I think if you are losing updates, it's some other problem unrelated to my dislike of certain functional limitations of CTM. I've been using CVS for going on three years now -- it's not like I'm a newby or anything. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Oct 31 20:27:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA17182 for current-outgoing; Tue, 31 Oct 1995 20:27:53 -0800 Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA17171 for ; Tue, 31 Oct 1995 20:27:47 -0800 Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.10/8.6.9) with SMTP id WAA20859 for ; Tue, 31 Oct 1995 22:27:46 -0600 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Tue, 31 Oct 95 22:27 CST Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Tue, 31 Oct 95 22:27 CST Message-Id: Subject: xdrrec_getpos and xdrrec_setpos To: current@freebsd.org Date: Tue, 31 Oct 1995 22:27:44 +1800 (CST) From: "Lars Fredriksen" X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 351 Sender: owner-current@freebsd.org Precedence: bulk Hi, What is the side-effect by having these routines return off_t? They both mess with file offsets and call lseek, but currently they assume off_t is a long. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks.pr.mcs.net (home-home) fredriks@asiago.cs.wisc.edu From owner-freebsd-current Tue Oct 31 21:09:54 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA20291 for current-outgoing; Tue, 31 Oct 1995 21:09:54 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA20280 for ; Tue, 31 Oct 1995 21:09:50 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id VAA11192; Tue, 31 Oct 1995 21:07:13 -0800 Date: Tue, 31 Oct 1995 21:07:11 -0800 (PST) From: -Vince- To: John Capo cc: jc@irbs.com, current@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <199511010220.VAA00668@irbs.irbs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Tue, 31 Oct 1995, John Capo wrote: > -Vince- writes: > > > > On Tue, 31 Oct 1995, John Capo wrote: > > > > > -Vince- writes: > > > > > > > > Greetings everyone, > > > > > > > > I was wondering what would need to be done to upgrade from > > > > FreeBSD -current to 2.1 and also, what is the proper and easiest way to > > > > compare the updated files in the /etc directory to my original /etc > > > > directory? Any help would be appreciated. > > > > > > > > > > Just did that to two of my systems. Almost all -current utils > > > work fine with a 2.1 kernel. mount_nfs was one that didn't. When > > > I discovered that I built nfsiod and nfsd and booted the 2.1 kernel > > > again. ps, pstat and top are some others that won't work. Once > > > I had NFS going I just did a make world. > > > > Hmmm, so will sup actually upgrade the system to 2.1 sources? > > The source tree for -stable is available via sup. -stable will be 2.1 > very shortly. Look at /usr/src/share/examples/sup/*stable*. I'll take a look at that so I don't really need to reinstall from floppies? > > > > > diff -r /etc /usr/src/etc is one way. -current and 2.1 are pretty > > > close /etc wise. > > > > Hmmm, I mean like I noticed that -current had alot of updates on > > /etc which I am still using the 2.05R /etc files with a few updated but > > what do I do after the diff command? > > > > Yeah it does, more than I thought. Basically you have to merge in > any changes you have made to your /etc files. Most likely candidates > are passwd, group, rc, rc.local, sysconfig, sendmail.cf, and ttys. > Save the files you have modified or the entire /etc direcctory. > Update /etc by hand or look at the distribution target in > /usr/src/etc/Makefile. I know what you mean but what does the > and < and other stuff mean from the diff output? Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Tue Oct 31 21:22:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA21442 for current-outgoing; Tue, 31 Oct 1995 21:22:21 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA21422 for ; Tue, 31 Oct 1995 21:22:11 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA16021; Wed, 1 Nov 1995 16:18:58 +1100 Date: Wed, 1 Nov 1995 16:18:58 +1100 From: Bruce Evans Message-Id: <199511010518.QAA16021@godzilla.zeta.org.au> To: current@freebsd.org, fredriks@mcs.com Subject: Re: xdrrec_getpos and xdrrec_setpos Sender: owner-current@freebsd.org Precedence: bulk >Subject: xdrrec_getpos and xdrrec_setpos > What is the side-effect by having these routines return >off_t? They both mess with file offsets and call lseek, but currently >they assume off_t is a long. They also assume that sizeof(int) == sizeof_long(). I dont know about side effects. There may be some sign extension bugs from switching to a signed type. The mem and stdio getpos and setpos functions are also broken. The mem functions assume that size_t is u_int and ths stdio functions assume that fpos_t is u_int. The stdio functions might be impossible to implement if fpos_t is a hairy struct. Bruce From owner-freebsd-current Tue Oct 31 21:26:43 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA21650 for current-outgoing; Tue, 31 Oct 1995 21:26:43 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA21639 for ; Tue, 31 Oct 1995 21:26:38 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id VAA14130; Tue, 31 Oct 1995 21:24:02 -0800 Date: Tue, 31 Oct 1995 21:24:02 -0800 (PST) From: -Vince- To: John Capo cc: jc@irbs.com, current@FreeBSD.org Subject: Re: FreeBSD 2.1 update Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Tue, 31 Oct 1995, John Capo wrote: > -Vince- writes: > > > > On Tue, 31 Oct 1995, John Capo wrote: > > > > > -Vince- writes: > > > > > > > > Greetings everyone, > > > > > > > > I was wondering what would need to be done to upgrade from > > > > FreeBSD -current to 2.1 and also, what is the proper and easiest way to > > > > compare the updated files in the /etc directory to my original /etc > > > > directory? Any help would be appreciated. > > > > > > > > > > Just did that to two of my systems. Almost all -current utils > > > work fine with a 2.1 kernel. mount_nfs was one that didn't. When > > > I discovered that I built nfsiod and nfsd and booted the 2.1 kernel > > > again. ps, pstat and top are some others that won't work. Once > > > I had NFS going I just did a make world. > > > > Hmmm, so will sup actually upgrade the system to 2.1 sources? > > The source tree for -stable is available via sup. -stable will be 2.1 > very shortly. Look at /usr/src/share/examples/sup/*stable*. I'll take a look at that so I don't really need to reinstall from floppies? Isn't the -current tree supposed to be newer than the -stable tree and will the -current tree become atleast 2.1? > > > > > diff -r /etc /usr/src/etc is one way. -current and 2.1 are pretty > > > close /etc wise. > > > > Hmmm, I mean like I noticed that -current had alot of updates on > > /etc which I am still using the 2.05R /etc files with a few updated but > > what do I do after the diff command? > > > > Yeah it does, more than I thought. Basically you have to merge in > any changes you have made to your /etc files. Most likely candidates > are passwd, group, rc, rc.local, sysconfig, sendmail.cf, and ttys. > Save the files you have modified or the entire /etc direcctory. > Update /etc by hand or look at the distribution target in > /usr/src/etc/Makefile. I know what you mean but what does the > and < and other stuff mean from the diff output? Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Tue Oct 31 22:55:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA26784 for current-outgoing; Tue, 31 Oct 1995 22:55:28 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA26777 ; Tue, 31 Oct 1995 22:55:22 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA19686; Wed, 1 Nov 1995 17:47:36 +1100 Date: Wed, 1 Nov 1995 17:47:36 +1100 From: Bruce Evans Message-Id: <199511010647.RAA19686@godzilla.zeta.org.au> To: gibbs@freefall.freebsd.org, wollman@lcs.mit.edu Subject: Re: Time problems Cc: current@FreeBSD.org, wollman@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk >Needless to say, on the three different motherboards we have here >(60, 100, and 120-MHz CPUs), we have never seen this problem, so it's >a bit hard to diagnose. For those machines on which the results are >reasonable, I expect timekeeping to be rather better than it was. >According to xntpd, my machine is within about 3 seconds per day, >which is about the same as it was before. (It's the precision, rather >than the accuracy, where this technique gives a benefit.) There's no reason why the Pentium clock should have higher precision than the 8254 clock. The low precision that you observed for the 8254 clock may have been due to the buggy implementation of adjtime(). It is necessary to inform microtime() about the adjustment. Currently, a count of 11932 for the 8254 clock is assumed to corresond to a time of 10000 usec. It actually corresponds to a time of (10000 + tickdelta + fine_usec_adjustment()). The result is that microtime() has an average jitter of about tickdelta/2 if adjtime() is used. If adjtime() isn't used, then microtime() has less jitter and less accuracy. I'm not sure why you didn't notice the same problem for the Pentium clock. Perhaps you just happen to have more accurate Pentium clocks. Note that increased accuracy also gives higher precision. I don't use Pentiums or adjtime(). This results in a low accuracy (700 ppm) but, as far as I can tell, a high precision. Can xntpd be run in a mode where it reports the drift but doesn't try to fix it? Bruce From owner-freebsd-current Tue Oct 31 23:13:59 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA27656 for current-outgoing; Tue, 31 Oct 1995 23:13:59 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA27645 ; Tue, 31 Oct 1995 23:13:57 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id XAA21794; Tue, 31 Oct 1995 23:13:13 -0800 From: Julian Elischer Message-Id: <199511010713.XAA21794@ref.tfs.com> Subject: Re: FreeBSD 2.1 update To: vince@apollo.COSC.GOV (-Vince-) Date: Tue, 31 Oct 1995 23:13:13 +1600 (PST) Cc: jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org In-Reply-To: from "-Vince-" at Oct 31, 95 09:24:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 834 Sender: owner-current@FreeBSD.org Precedence: bulk > > On Tue, 31 Oct 1995, John Capo wrote: > > I'll take a look at that so I don't really need to reinstall from > floppies? Isn't the -current tree supposed to be newer than the -stable > tree and will the -current tree become atleast 2.1? think of it this way: /---->2.1 /->2.2 / / 1.0---->1.1---->1.1.5->X /---->2.0---->2.0.5---+----------+-->? ---- ^ BSD4.4--------------/ | | -current is presently HERE I'm not sure if the next 'stabel' release will be based on 2.1 or 2.2 but I draw it as being 2.2 here From owner-freebsd-current Tue Oct 31 23:16:06 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA27826 for current-outgoing; Tue, 31 Oct 1995 23:16:06 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA27819 ; Tue, 31 Oct 1995 23:16:03 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id XAA27315; Tue, 31 Oct 1995 23:13:16 -0800 Date: Tue, 31 Oct 1995 23:13:15 -0800 (PST) From: -Vince- To: Julian Elischer cc: jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <199511010713.XAA21794@ref.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Tue, 31 Oct 1995, Julian Elischer wrote: > > > > On Tue, 31 Oct 1995, John Capo wrote: > > > > I'll take a look at that so I don't really need to reinstall from > > floppies? Isn't the -current tree supposed to be newer than the -stable > > tree and will the -current tree become atleast 2.1? > think of it this way: > > /---->2.1 /->2.2 > / / > 1.0---->1.1---->1.1.5->X /---->2.0---->2.0.5---+----------+-->? > ---- ^ > BSD4.4--------------/ | > | > -current is presently HERE > I'm not sure if the next 'stabel' > release will be based on 2.1 or 2.2 > but I draw it as being 2.2 here So it is really ahead of stable or 2.1 in the code? Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Tue Oct 31 23:28:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA28443 for current-outgoing; Tue, 31 Oct 1995 23:28:24 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA28425 ; Tue, 31 Oct 1995 23:28:04 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA20983; Wed, 1 Nov 1995 18:23:37 +1100 Date: Wed, 1 Nov 1995 18:23:37 +1100 From: Bruce Evans Message-Id: <199511010723.SAA20983@godzilla.zeta.org.au> To: gibbs@freefall.freebsd.org, wollman@lcs.mit.edu Subject: Re: Time problems Cc: current@FreeBSD.org, wollman@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk >Can we do occasional 8254 based sanity checking of the system time to >either automatically revert to the 8254 on systems that the new code >yields poor results, or simply to fix up the time occasionally? I Reverting to the 8254 early is easy. Simply don't set pentium_mhz if the error for truncating to an int would be too large. Reverting to it later and keeping the clocks in sync is harder. There is no way to tell which of the the 8254 clock and the Pentium clock has drifted without comparing them both with a external time source, and if you have such a time source then it should be possible to use it to keep the Pentium clock in sync. The 8254 maximum count and pentium_mhz should be varied to reduce adjustments. >>a bit hard to diagnose. For those machines on which the results are >>reasonable, I expect timekeeping to be rather better than it was. >>According to xntpd, my machine is within about 3 seconds per day, >>which is about the same as it was before. (It's the precision, rather >>than the accuracy, where this technique gives a benefit.) >> >>-GAWollman >Precision and overhead right? Why is it that xntpd doesn't either >complain about my large offset (I started it just after using ntpdate), >or keep my time in sync? Perhaps because of the microtime() jitter that I reported in previous mail - if the accuracy is low then the jitter becomes large when adjtime() is used to improved the accuracy. However, I guess xntpd should be able to handle large jitter. I confused precision and accuracy a bit in my previous mail. It isn't true that the Pentium clock gives more precision in the current implementation. If both clocks have _no_ drift but large inaccuracy, then the precision is proportional by the the inverse of the factor used to convert from a cycle count to a time. For the 8254 clock, the factor is 11932 and for the Pentium clock it is 90. Thus the Pentium clock is about 132 times less precise than the 8254 clock unless someone made a point of making the Pentium clock frequency an integral number of MHz. Bruce From owner-freebsd-current Wed Nov 1 00:03:25 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA00314 for current-outgoing; Wed, 1 Nov 1995 00:03:25 -0800 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA00202 for ; Wed, 1 Nov 1995 00:02:06 -0800 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id KAA18894; Wed, 1 Nov 1995 10:00:29 +0200 From: John Hay Message-Id: <199511010800.KAA18894@zibbi.mikom.csir.co.za> Subject: Re: Time problems To: wollman@lcs.mit.edu (Garrett A. Wollman) Date: Wed, 1 Nov 1995 10:00:29 +0200 (SAT) Cc: current@FreeBSD.org In-Reply-To: <9510311747.AA29686@halloran-eldar.lcs.mit.edu> from "Garrett A. Wollman" at Oct 31, 95 12:47:55 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1822 Sender: owner-current@FreeBSD.org Precedence: bulk OK, I changed the values in calibrate_cyclecounter() like suggested and now my time stay much closer to reality. My CPU even probe as a 90MHz processor! > CPU: 90-MHz Pentium 735\\90 (Pentium-class CPU) > Origin = "GenuineIntel" Id = 0x525 Stepping=5 > Features=0x3bf Can we get some kernel config option to do this or will I have to change clock.c after every ctm? Or will this get to be the default? John -- John Hay -- John.Hay@csir.co.za > In talking to David Greenman about this problem, we found that one of > his machines which exhibits this problem suffers from (1). Other > people have suggested (2) for their motherboards. (David's > motherboard took about 12 seconds to perform a ten-second delay.) > > Here's one thing which you might try: > > In this function (in i386/isa/clock.c): > > ------------------------------------ > calibrate_cyclecounter(void) > { > /* > * Don't need volatile; should always use unsigned if 2's > * complement arithmetic is desired. > */ > unsigned long long count; > > __asm __volatile(".byte 0x0f, 0x30" : : "A"(0LL), "c" (0x10)); > DELAY(1000000); > __asm __volatile(".byte 0xf,0x31" : "=A" (count)); > /* > * XX lose if the clock rate is not nearly a multiple of 1000000. > */ > pentium_mhz = (count + 500000) / 1000000; > } > ------------------------------------ > > Change the occurrences of `1000000' to `10000' and `500000' to > `5000'. This will reduce the calibration time, which makes it more > likely that the error in your clock will be small enough to get > rounded off. If that doesn't work, then just #ifdef out the body of > the function, which will cause the 8254-alike to act as the reference > for timekeeping. > From owner-freebsd-current Wed Nov 1 00:32:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA02396 for current-outgoing; Wed, 1 Nov 1995 00:32:21 -0800 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA02384 for ; Wed, 1 Nov 1995 00:32:13 -0800 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD-4.4) id TAA10618; Wed, 1 Nov 1995 19:31:18 +1100 From: michael butler Message-Id: <199511010831.TAA10618@asstdc.scgt.oz.au> Subject: Re: Time problems To: bde@zeta.org.au (Bruce Evans) Date: Wed, 1 Nov 1995 19:31:17 +1100 (EST) Cc: current@freebsd.org In-Reply-To: <199511010723.SAA20983@godzilla.zeta.org.au> from "Bruce Evans" at Nov 1, 95 06:23:37 pm X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2217 Sender: owner-current@freebsd.org Precedence: bulk > >>a bit hard to diagnose. For those machines on which the results are > >>reasonable, I expect timekeeping to be rather better than it was. > >>According to xntpd, my machine is within about 3 seconds per day, > >>which is about the same as it was before. (It's the precision, rather > >>than the accuracy, where this technique gives a benefit.) 3/86400 = ~34ppm .. most PCs would be hard-pushed to better that. I'd be happy if that was the general scale of error :-) With some manual trimming, I have two (non-pentia) here that are 5ppm and -6ppm but the average "off-the-shelf" box isn't much better than +/-300ppm. > Perhaps because of the microtime() jitter that I reported in previous > mail - if the accuracy is low then the jitter becomes large when adjtime() > is used to improved the accuracy. However, I guess xntpd should be > able to handle large jitter. The way that the NTP documentation reads, it seems that the PLL is unhappy beyond the designed capture range of +/-128ppm and that one should adjust the kernel tick value (with "tickadj -t ...") to bring it to within those boundaries. In preference, it states that (if you're a "screwdriver programmer" :-)) you can (and should) adjust your system clock to correct the offset. Unfortunately, most PCs these days don't seem to have a trimcap to play with :-( Note especially that the "dispersion" derived by XNTPD is a measure of how much jitter it perceives between your clock and the remote reference and provides a statistical window within which measurements are considered credible enough upon which to act. If you have any significant traffic on the link between you and the reference which causes the poll latency to vary beyond this dispersion value, the local jitter becomes almost irrelevant. To quantify this, an unloaded 64k ISDN link can incur a 28mS latency. Add some news to it and, courtesy of the various order-uncertainties in propagation, that can deviate by as much as 2 seconds. Now add the uncertainties inherent on the other links that feed into the 64k and ... Bluntly, NTP over a modem-based connection is statistical guesswork which you should expect to wander all over the shop as link traffic varies. michael From owner-freebsd-current Wed Nov 1 01:04:00 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA04144 for current-outgoing; Wed, 1 Nov 1995 01:04:00 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA04135 for ; Wed, 1 Nov 1995 01:03:56 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id BAA15243; Wed, 1 Nov 1995 01:00:51 -0800 Date: Wed, 1 Nov 1995 01:00:50 -0800 (PST) From: -Vince- To: current@FreeBSD.ORG Subject: make world failed with -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk Does anyone know what's wrong since make world fails on -current: ===> share/doc/FAQ sgmlfmt -f ascii /usr/src/share/doc/FAQ/freebsd-faq.sgml Input file ascii not found install -c -o bin -g bin -m 444 freebsd-faq.ascii /usr/share/doc/FAQ install: freebsd-faq.ascii: No such file or directory *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. root@apollo [12:51am][/usr/src] >> Any help would be appreciated. Thanks! Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Wed Nov 1 01:08:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA04423 for current-outgoing; Wed, 1 Nov 1995 01:08:14 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA04397 for ; Wed, 1 Nov 1995 01:08:06 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA24620; Wed, 1 Nov 1995 20:03:05 +1100 Date: Wed, 1 Nov 1995 20:03:05 +1100 From: Bruce Evans Message-Id: <199511010903.UAA24620@godzilla.zeta.org.au> To: jhay@mikom.csir.co.za, wollman@lcs.mit.edu Subject: Re: Time problems Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk >OK, I changed the values in calibrate_cyclecounter() like suggested and now >my time stay much closer to reality. >My CPU even probe as a 90MHz processor! >> CPU: 90-MHz Pentium 735\\90 (Pentium-class CPU) >> Origin = "GenuineIntel" Id = 0x525 Stepping=5 >> Features=0x3bf >Can we get some kernel config option to do this or will I have to change >clock.c after every ctm? Or will this get to be the default? No. Reducing the calibration time should just decrease the accuracy of the calibration (and speed up the boot :-). Find out which clock is inaccurate or which part of the calibration routine is buggy. Define DELAYDEBUG to get some debugging code in clock.c. It currently generates delays of powers of 10 usec up to 10 seconds. You could increase the delats to 100, 1000, ... seconds and time them with a stopwatch to see how accurate DELAY() is. Bruce From owner-freebsd-current Wed Nov 1 01:08:37 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA04490 for current-outgoing; Wed, 1 Nov 1995 01:08:37 -0800 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA04475 ; Wed, 1 Nov 1995 01:08:31 -0800 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id BAA09757; Wed, 1 Nov 1995 01:08:05 -0800 From: "Rodney W. Grimes" Message-Id: <199511010908.BAA09757@GndRsh.aac.dev.com> Subject: Re: Time problems To: bde@zeta.org.au (Bruce Evans) Date: Wed, 1 Nov 1995 01:08:04 -0800 (PST) Cc: gibbs@freefall.freebsd.org, wollman@lcs.mit.edu, current@FreeBSD.org, wollman@FreeBSD.org In-Reply-To: <199511010723.SAA20983@godzilla.zeta.org.au> from "Bruce Evans" at Nov 1, 95 06:23:37 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2540 Sender: owner-current@FreeBSD.org Precedence: bulk ... > I confused precision and accuracy a bit in my previous mail. It isn't > true that the Pentium clock gives more precision in the current > implementation. If both clocks have _no_ drift but large inaccuracy, > then the precision is proportional by the the inverse of the factor > used to convert from a cycle count to a time. For the 8254 clock, > the factor is 11932 and for the Pentium clock it is 90. Thus the > Pentium clock is about 132 times less precise than the 8254 clock > unless someone made a point of making the Pentium clock frequency > an integral number of MHz. And there in lies a part of the problem, the clock frequency of the Pentium CPU is controlled by either a crystal or a clock synth chip wich is running at some frequency X. Instead of using X the code is using X / 1E6 loosing 6 digits of precision in the process :-(. I have hooked clock synth chips to high precission (12 to 15) digit frequency counters and believe me there are significant digits in that 1E6 area that is being truncated. It is also the cause of bogus dmesg crap like: CPU: 99-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) That is wrong, this is a 9985304553 Hz clocked Pentium 815\100 (At 25 degrees C, 1 Atmosphere, it drifts with temperature a bit, and I am sure if I swapped power supplies it would shift some :-)) I would suggest that the intgral MHz be changed to Integral HZ, it will allow very fine resolution corrections, and the chip type selection code to be updated so that it correctly rounds per the following table when selecting the Icomp index value (and my table adds the seriously missing other Pentium chips): Integral MHZ iComp 59-61 510 65-67 567 74-76 610 * 89-91 735 99-101 815 119-121 1000 * 132-134 1110 * * I know at my last look these are missing from the iComp detection code. IMHO the whole idea of trying to print the iComp and/or model should be trashed, as there is nothing preventing me from running an A80502-133 SK106 (official Intel Part number) at anything from 10 to 1110 iComps, it's still an A80502-133!!!! The 1110\133 designation is marketing crap, meaningless to just about every one: CPU: Intel Pentium Processor clocked at 99.85 Mhz (Pentium class CPU) makes a lot more since to me! Also note the current messeage is not properly marking Pentium as a trademark, and wrongly using Pentium as a noun :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Nov 1 01:27:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA05515 for current-outgoing; Wed, 1 Nov 1995 01:27:53 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA05505 for ; Wed, 1 Nov 1995 01:27:50 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id BAA00252; Wed, 1 Nov 1995 01:27:49 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id BAA10684; Wed, 1 Nov 1995 01:20:59 -0800 Message-Id: <199511010920.BAA10684@corbin.Root.COM> To: "Garrett A. Wollman" cc: "Justin T. Gibbs" , current@freebsd.org Subject: Re: Time problems In-reply-to: Your message of "Tue, 31 Oct 95 12:47:55 EST." <9510311747.AA29686@halloran-eldar.lcs.mit.edu> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 01 Nov 1995 01:20:59 -0800 Sender: owner-current@freebsd.org Precedence: bulk >calibration. There are two possible sources of error involved here: > > 1) The part of your chipset that emulates the timer/counter is >operating at the wrong rate (or the DELAY function isn't working right >for it). > > 2) Your CPU's cycle counter is not operating at the nominal >rate, or its rate in MHz is not close to an integer. > >In talking to David Greenman about this problem, we found that one of >his machines which exhibits this problem suffers from (1). Other >people have suggested (2) for their motherboards. (David's >motherboard took about 12 seconds to perform a ten-second delay.) It was the other way around - it too 8.5 seconds to do a DELAY(10000000). -DG From owner-freebsd-current Wed Nov 1 02:07:37 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA07719 for current-outgoing; Wed, 1 Nov 1995 02:07:37 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA07712 for ; Wed, 1 Nov 1995 02:07:32 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id LAA06042 ; Wed, 1 Nov 1995 11:07:29 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id LAA18134 ; Wed, 1 Nov 1995 11:07:29 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.1/keltia-uucp-2.6) id KAA15481; Wed, 1 Nov 1995 10:51:06 +0100 (MET) From: Ollivier Robert Message-Id: <199511010951.KAA15481@keltia.freenix.fr> Subject: Re: FreeBSD 2.1 update To: vince@apollo.COSC.GOV (-Vince-) Date: Wed, 1 Nov 1995 10:51:05 +0100 (MET) Cc: jc@irbs.com, current@FreeBSD.org In-Reply-To: from "-Vince-" at Oct 31, 95 09:24:02 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1275 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk It seems that -Vince- said: > I know what you mean but what does the > and < and other stuff > mean from the diff output? the "<" means these lines are from the first file and the ">" that they come from the second. Anyway, what you want is either "diff -u" or "diff -c" output. Both are easier to read. Unified diffs ("-u") are smaller. You will see easily what has changed and what was added/removed. "-c" will give you lines preceded by "+"/"-" for added removed and "!" for changed lines in separate area for both files. "-u" will give you only "+"/"-" but there is only one area displayed (so they are smaller). -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #5: Mon Oct 30 00:03:29 MET 1995 From owner-freebsd-current Wed Nov 1 02:59:23 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA09306 for current-outgoing; Wed, 1 Nov 1995 02:59:23 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA09300 for ; Wed, 1 Nov 1995 02:59:19 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id CAA16916; Wed, 1 Nov 1995 02:55:58 -0800 Date: Wed, 1 Nov 1995 02:55:57 -0800 (PST) From: -Vince- To: Ollivier Robert cc: jc@irbs.com, current@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <199511010951.KAA15481@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Ollivier Robert wrote: > It seems that -Vince- said: > > I know what you mean but what does the > and < and other stuff > > mean from the diff output? > > the "<" means these lines are from the first file and the ">" that they > come from the second. > > Anyway, what you want is either "diff -u" or "diff -c" output. Both are > easier to read. Unified diffs ("-u") are smaller. You will see easily what > has changed and what was added/removed. > > "-c" will give you lines preceded by "+"/"-" for added removed and "!" for > changed lines in separate area for both files. > > "-u" will give you only "+"/"-" but there is only one area displayed (so > they are smaller). Oh okay, Thanks for the detailed information! =) Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Wed Nov 1 03:00:30 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA09389 for current-outgoing; Wed, 1 Nov 1995 03:00:30 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA09379 ; Wed, 1 Nov 1995 03:00:25 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id MAA06361 ; Wed, 1 Nov 1995 12:00:12 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id MAA18233 ; Wed, 1 Nov 1995 12:00:11 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.1/keltia-uucp-2.6) id LAA15613; Wed, 1 Nov 1995 11:12:00 +0100 (MET) From: Ollivier Robert Message-Id: <199511011012.LAA15613@keltia.freenix.fr> Subject: Re: FreeBSD 2.1 update To: vince@apollo.COSC.GOV (-Vince-) Date: Wed, 1 Nov 1995 11:12:00 +0100 (MET) Cc: julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org In-Reply-To: from "-Vince-" at Oct 31, 95 11:13:15 pm X-Operating-System: FreeBSD 2.2-CURRENT ctm#1275 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk It seems that -Vince- said: > > So it is really ahead of stable or 2.1 in the code? -CURRENT is ahead of 2.1. 2.1 is "just" 2.0.5 with fixes. It has not the latest VM rewrite, the latest PPP, and so on. At some point after 2.1, -CURRENT will probably become 2.3-CURRENT and -STABLE will be 2.2-STABLE to end up with 2.2-RELEASE and so on. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #5: Mon Oct 30 00:03:29 MET 1995 From owner-freebsd-current Wed Nov 1 03:00:43 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA09430 for current-outgoing; Wed, 1 Nov 1995 03:00:43 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA09409 for ; Wed, 1 Nov 1995 03:00:35 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id MAA06366 ; Wed, 1 Nov 1995 12:00:13 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id MAA18236 ; Wed, 1 Nov 1995 12:00:12 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.1/keltia-uucp-2.6) id LAA15626; Wed, 1 Nov 1995 11:19:16 +0100 (MET) From: Ollivier Robert Message-Id: <199511011019.LAA15626@keltia.freenix.fr> Subject: Re: make world failed with -current To: vince@apollo.COSC.GOV (-Vince-) Date: Wed, 1 Nov 1995 11:19:15 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: from "-Vince-" at Nov 1, 95 01:00:50 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1275 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG Precedence: bulk It seems that -Vince- said: > Stop. > root@apollo [12:51am][/usr/src] >> > > Any help would be appreciated. Thanks! You have an outdated sgmlfmt and "make world" doesn't take are of it yet. Go to /usr/src/usr.bin/sgmlfmt, "make all install", then try again. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #5: Mon Oct 30 00:03:29 MET 1995 From owner-freebsd-current Wed Nov 1 03:30:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA10704 for current-outgoing; Wed, 1 Nov 1995 03:30:52 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA10697 ; Wed, 1 Nov 1995 03:30:47 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id DAA17301; Wed, 1 Nov 1995 03:27:22 -0800 Date: Wed, 1 Nov 1995 03:27:21 -0800 (PST) From: -Vince- To: Ollivier Robert cc: julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <199511011012.LAA15613@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Ollivier Robert wrote: > It seems that -Vince- said: > > > > So it is really ahead of stable or 2.1 in the code? > > -CURRENT is ahead of 2.1. 2.1 is "just" 2.0.5 with fixes. It has not the > latest VM rewrite, the latest PPP, and so on. > > At some point after 2.1, -CURRENT will probably become 2.3-CURRENT and > -STABLE will be 2.2-STABLE to end up with 2.2-RELEASE and so on. So what you are saying is that -release is really just -current at some point? and -stable is just really -current before a -release? Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Wed Nov 1 03:31:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA10744 for current-outgoing; Wed, 1 Nov 1995 03:31:34 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA10739 for ; Wed, 1 Nov 1995 03:31:29 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id DAA17314; Wed, 1 Nov 1995 03:27:58 -0800 Date: Wed, 1 Nov 1995 03:27:58 -0800 (PST) From: -Vince- To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: make world failed with -current In-Reply-To: <199511011019.LAA15626@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Wed, 1 Nov 1995, Ollivier Robert wrote: > It seems that -Vince- said: > > Stop. > > root@apollo [12:51am][/usr/src] >> > > > > Any help would be appreciated. Thanks! > > You have an outdated sgmlfmt and "make world" doesn't take are of it yet. > > Go to /usr/src/usr.bin/sgmlfmt, "make all install", then try again. Thanks, never knew it was sgmlfmt that was the problem... Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Wed Nov 1 07:06:45 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA17726 for current-outgoing; Wed, 1 Nov 1995 07:06:45 -0800 Received: from dtr.com (dtr.rain.com [204.119.8.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA17721 for ; Wed, 1 Nov 1995 07:06:40 -0800 From: bmk@dtr.com Received: (from bmk@localhost) by dtr.com (8.6.11/8.6.9) id HAA18658 for freebsd-current@freebsd.org; Wed, 1 Nov 1995 07:06:37 -0800 Message-Id: <199511011506.HAA18658@dtr.com> Subject: Can't build -current from 10/31/1995 To: freebsd-current@freebsd.org Date: Wed, 1 Nov 1995 07:06:36 -0800 (PST) Reply-To: bmk@dtr.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 455 Sender: owner-current@freebsd.org Precedence: bulk I received the -current sources via CTM (ftp from freefall.cdrom.com) on 10/31/1995 and can't get it built. The failure looks like: ==> bin/ps cc -O -I/sys -static -o ps fmt.o keyword.o nlist.o print.o ps.o -lm -lkvm ld: scrt0.o: No such file or directory *** Error code 1 Stop. I'm building it on top of a 2.0.5-RELEASE system. Are there any additional steps that I need to take? I'm using 'make -NOCLEANDIR -NOOBJDIR -DNOPROFILE -DNOSECURE'. From owner-freebsd-current Wed Nov 1 07:13:08 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA17850 for current-outgoing; Wed, 1 Nov 1995 07:13:08 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA17845 for ; Wed, 1 Nov 1995 07:13:03 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id HAA00474; Wed, 1 Nov 1995 07:13:01 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id HAA02230; Wed, 1 Nov 1995 07:12:58 -0800 Message-Id: <199511011512.HAA02230@corbin.Root.COM> To: bmk@dtr.com cc: freebsd-current@freebsd.org Subject: Re: Can't build -current from 10/31/1995 In-reply-to: Your message of "Wed, 01 Nov 95 07:06:36 PST." <199511011506.HAA18658@dtr.com> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 01 Nov 1995 07:12:57 -0800 Sender: owner-current@freebsd.org Precedence: bulk >I received the -current sources via CTM (ftp from freefall.cdrom.com) on >10/31/1995 and can't get it built. The failure looks like: > >==> bin/ps >cc -O -I/sys -static -o ps fmt.o keyword.o nlist.o print.o ps.o -lm -lkvm >ld: scrt0.o: No such file or directory >*** Error code 1 You need to rebuild crt0 first. cd /usr/src/lib/csu/i386 make ; make install -DG From owner-freebsd-current Wed Nov 1 07:33:19 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA18578 for current-outgoing; Wed, 1 Nov 1995 07:33:19 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA18573 for ; Wed, 1 Nov 1995 07:33:13 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA01193; Wed, 1 Nov 1995 10:33:04 -0500 Date: Wed, 1 Nov 1995 10:33:04 -0500 From: "Garrett A. Wollman" Message-Id: <9511011533.AA01193@halloran-eldar.lcs.mit.edu> To: "Rodney W. Grimes" Cc: current@FreeBSD.org Subject: Re: Time problems In-Reply-To: <199511010908.BAA09757@GndRsh.aac.dev.com> References: <199511010723.SAA20983@godzilla.zeta.org.au> <199511010908.BAA09757@GndRsh.aac.dev.com> Sender: owner-current@FreeBSD.org Precedence: bulk < said: > I have hooked clock synth chips to high precission (12 to 15) digit > frequency counters and believe me there are significant digits in > that 1E6 area that is being truncated. It is also the cause of > bogus dmesg crap like: > CPU: 99-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) When I have time to sit down and figure out a reasonable value to use, I plan to convert the calculation to use fixed-point arithmetic. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Nov 1 07:38:24 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA18772 for current-outgoing; Wed, 1 Nov 1995 07:38:24 -0800 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA18765 for ; Wed, 1 Nov 1995 07:38:10 -0800 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id RAA19641; Wed, 1 Nov 1995 17:33:13 +0200 From: John Hay Message-Id: <199511011533.RAA19641@zibbi.mikom.csir.co.za> Subject: Re: Time problems To: bde@zeta.org.au (Bruce Evans) Date: Wed, 1 Nov 1995 17:33:13 +0200 (SAT) Cc: wollman@lcs.mit.edu, current@FreeBSD.org In-Reply-To: <199511010903.UAA24620@godzilla.zeta.org.au> from "Bruce Evans" at Nov 1, 95 08:03:05 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1824 Sender: owner-current@FreeBSD.org Precedence: bulk > > >OK, I changed the values in calibrate_cyclecounter() like suggested and now > >my time stay much closer to reality. > > >My CPU even probe as a 90MHz processor! > >> CPU: 90-MHz Pentium 735\\90 (Pentium-class CPU) > >> Origin = "GenuineIntel" Id = 0x525 Stepping=5 > >> Features=0x3bf > > >Can we get some kernel config option to do this or will I have to change > >clock.c after every ctm? Or will this get to be the default? > > No. Reducing the calibration time should just decrease the accuracy of > the calibration (and speed up the boot :-). Find out which clock is > inaccurate or which part of the calibration routine is buggy. Define > DELAYDEBUG to get some debugging code in clock.c. It currently > generates delays of powers of 10 usec up to 10 seconds. You could > increase the delats to 100, 1000, ... seconds and time them with a > stopwatch to see how accurate DELAY() is. > > Bruce > OK, I did that and the 10 second delay takes about 8.5 seconds and the 100 second delay takes about 88 seconds. Here is the first part of dmesg: CPU: DELAY(1)... 1 calls to getit() at -14 usec each DELAY(10)... 1 calls to getit() at -5 usec each DELAY(100)... 22 calls to getit() at 3 usec each DELAY(1000)... 261 calls to getit() at 3 usec each DELAY(10000)... 2648 calls to getit() at 3 usec each DELAY(100000)... 26511 calls to getit() at 3 usec each DELAY(1000000)... 238632 calls to getit() at 4 usec each DELAY(10000000)... 2351886 calls to getit() at 4 usec each DELAY(100000000)... 23667381 calls to getit() at 4 usec each 892492-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) >From about 100000 the values that is being printed vary quite a lot between boots. Now how do I go further to find out where my problem is? John -- John Hay -- John.Hay@csir.co.za From owner-freebsd-current Wed Nov 1 09:24:40 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA22711 for current-outgoing; Wed, 1 Nov 1995 09:24:40 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA22706 ; Wed, 1 Nov 1995 09:24:38 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id JAA09853 ; Wed, 1 Nov 1995 09:21:37 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id SAA09102 ; Wed, 1 Nov 1995 18:01:22 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id SAA18832 ; Wed, 1 Nov 1995 18:01:21 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.1/keltia-uucp-2.6) id RAA17313; Wed, 1 Nov 1995 17:05:11 +0100 (MET) From: Ollivier Robert Message-Id: <199511011605.RAA17313@keltia.freenix.fr> Subject: Re: FreeBSD 2.1 update To: vince@apollo.COSC.GOV (-Vince-) Date: Wed, 1 Nov 1995 17:05:11 +0100 (MET) Cc: julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org In-Reply-To: from "-Vince-" at Nov 1, 95 03:27:21 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1275 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk It seems that -Vince- said: > > At some point after 2.1, -CURRENT will probably become 2.3-CURRENT and > > -STABLE will be 2.2-STABLE to end up with 2.2-RELEASE and so on. > > So what you are saying is that -release is really just -current > at some point? and -stable is just really -current before a -release? Not really. What we have *now* is: * 2.1-STABLE will become 2.1-RELEASE * 2.2-CURRENT aka "the Bleeding Edge(tm)". What we will [probably] have is * 2.2-CURRENT become 2.2-STABLE after 2.1-RELEASE is out. It is intended to be 2.2-RELEASE one day. When 2.2-STABLE begins its life, 2.3-CURRENT will begin and so on. Note as I'm not part of the core team so what is above are only my thoughts, they may want to change the numbers :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #5: Mon Oct 30 00:03:29 MET 1995 From owner-freebsd-current Wed Nov 1 09:32:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA22873 for current-outgoing; Wed, 1 Nov 1995 09:32:12 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA22867 for ; Wed, 1 Nov 1995 09:32:07 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA07621; Thu, 2 Nov 1995 04:30:41 +1100 Date: Thu, 2 Nov 1995 04:30:41 +1100 From: Bruce Evans Message-Id: <199511011730.EAA07621@godzilla.zeta.org.au> To: bde@zeta.org.au, jhay@mikom.csir.co.za Subject: Re: Time problems Cc: current@FreeBSD.org, wollman@lcs.mit.edu Sender: owner-current@FreeBSD.org Precedence: bulk >OK, I did that and the 10 second delay takes about 8.5 seconds and the 100 >second delay takes about 88 seconds. Here is the first part of dmesg: Urk. >Now how do I go further to find out where my problem is? Perhaps the 8254 clock is being accessed too fast. Try adding some delays before each inb() and outb() in clock.c:getit(). Count to 100 or so to get at least 1 usec delay. If pentium_mhz is set to 0, then microtime() uses essentially the same method as DELAY(). It accesses the clock registers as fast as possible. Errors as large as 15 in 100 might be noticeable if you run the following program. You will have to adjust the constants 25 and 50 (perhaps to 0 and 100) to filter out the uninteresting stuff. Differences of < 0 or much less than the average value mean that there is a problem. The program should calculate the average value to decide a good range to filter... --- #include #include #define SIZE 102400 struct timeval buf[SIZE]; int main(void) { int n; long s; struct timeval tv; struct timezone tz; s = gettimeofday(&tv, &tz); buf[0] = tv; printf("%ld %ld\n", buf[0].tv_sec, buf[0].tv_usec); for (n = 1; n < SIZE; ++n) { s = gettimeofday(&tv, &tz); buf[n] = tv; } for (n = 1; n < SIZE; ++n) { s = (buf[n].tv_sec - buf[n - 1].tv_sec) * 1000000 + buf[n].tv_usec - buf[n - 1].tv_usec; if (s < 25 || s > 50) printf("%d %ld\n", n, s); } return 0; } --- Bruce From owner-freebsd-current Wed Nov 1 10:05:06 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA23849 for current-outgoing; Wed, 1 Nov 1995 10:05:06 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id KAA23844 for ; Wed, 1 Nov 1995 10:05:04 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA01541; Wed, 1 Nov 1995 13:01:55 -0500 Date: Wed, 1 Nov 1995 13:01:55 -0500 From: "Garrett A. Wollman" Message-Id: <9511011801.AA01541@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: Time problems In-Reply-To: <199511011730.EAA07621@godzilla.zeta.org.au> References: <199511011730.EAA07621@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.org Precedence: bulk < said: > much less than the average value mean that there is a problem. The > program should calculate the average value to decide a good range to > filter... Here is a program that I have used to measure a whole bunch of things about the clock... ------------------------------------ #include #include #include #include #include #include #include #include #define N 2000000 int diffs[N]; int hist[N]; int main(void) { int i, j; int min, max; double sum, mean, var, sumsq; struct timeval tv, otv; memset(diffs, '\0', sizeof diffs); /* fault in whole array, we hope */ for(i = 0; i < N; i++) { gettimeofday(&tv, 0); do { otv = tv; gettimeofday(&tv, 0); } while(tv.tv_sec == otv.tv_sec && tv.tv_usec == otv.tv_usec); diffs[i] = tv.tv_usec - otv.tv_usec + 1000000 * (tv.tv_sec - otv.tv_sec); } min = INT_MAX; max = INT_MIN; sum = 0; sumsq = 0; for(i = 0; i < N; i++) { if(diffs[i] > max) max = diffs[i]; if(diffs[i] < min) min = diffs[i]; sum += diffs[i]; sumsq += diffs[i] * diffs[i]; } mean = sum / (double)N; var = (sumsq - 2 * mean * sum + sum * mean) / (double)N; printf("min %d, max %d, mean %f, std %f\n", min, max, mean, sqrt(var)); for(i = 0; i < N; i++) { hist[diffs[i]]++; } for(j = 0; j < 5; j++) { max = 0; min = 0; for(i = 0; i < N; i++) { if(hist[i] > max) { max = hist[i]; min = i; /* xxx */ } } printf("%dth: %d (%d observations)\n", j + 1, min, max); hist[min] = 0; } return 0; } ------------------------------------ -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Wed Nov 1 10:22:45 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA24238 for current-outgoing; Wed, 1 Nov 1995 10:22:45 -0800 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA24232 for ; Wed, 1 Nov 1995 10:22:41 -0800 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id KAA10044; Wed, 1 Nov 1995 10:22:09 -0800 From: "Rodney W. Grimes" Message-Id: <199511011822.KAA10044@GndRsh.aac.dev.com> Subject: Re: make world failed with -current To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Wed, 1 Nov 1995 10:22:09 -0800 (PST) Cc: vince@apollo.COSC.GOV, current@FreeBSD.ORG In-Reply-To: <199511011019.LAA15626@keltia.freenix.fr> from "Ollivier Robert" at Nov 1, 95 11:19:15 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 508 Sender: owner-current@FreeBSD.ORG Precedence: bulk > > It seems that -Vince- said: > > Stop. > > root@apollo [12:51am][/usr/src] >> > > > > Any help would be appreciated. Thanks! > > You have an outdated sgmlfmt and "make world" doesn't take are of it yet. > > Go to /usr/src/usr.bin/sgmlfmt, "make all install", then try again. Please add sgmlfmt to the ``tools:'' target of /usr/src/Makefile. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Wed Nov 1 11:16:09 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA25232 for current-outgoing; Wed, 1 Nov 1995 11:16:09 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA25227 ; Wed, 1 Nov 1995 11:16:05 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id LAA00864; Wed, 1 Nov 1995 11:03:05 -0800 To: -Vince- cc: Ollivier Robert , julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-reply-to: Your message of "Wed, 01 Nov 1995 03:27:21 PST." Date: Wed, 01 Nov 1995 11:03:04 -0800 Message-ID: <862.815252584@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > So what you are saying is that -release is really just -current > at some point? and -stable is just really -current before a -release? NO. Jordan From owner-freebsd-current Wed Nov 1 11:47:09 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA25776 for current-outgoing; Wed, 1 Nov 1995 11:47:09 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA25771 ; Wed, 1 Nov 1995 11:47:05 -0800 Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.12) id LAA23144; Wed, 1 Nov 1995 11:45:05 -0800 From: Julian Elischer Message-Id: <199511011945.LAA23144@ref.tfs.com> Subject: Re: FreeBSD 2.1 update To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Wed, 1 Nov 1995 11:45:05 -0800 (PST) Cc: vince@apollo.COSC.GOV, roberto@keltia.freenix.fr, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org In-Reply-To: <862.815252584@time.cdrom.com> from "Jordan K. Hubbard" at Nov 1, 95 11:03:04 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 514 Sender: owner-current@FreeBSD.org Precedence: bulk > > > So what you are saying is that -release is really just -current > > at some point? and -stable is just really -current before a -release? > > NO. NO? I think he has it right eventhough he says it a bit oddly.. -current always moves forwards. every so often a 'branch' is made that is eventually made into a release.. What I'm not sure of myself, is whether -stable derives from -current, or from a previous (unstable?) release. (because we are effectively doing both at the moment) > > Jordan > From owner-freebsd-current Wed Nov 1 12:24:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA26730 for current-outgoing; Wed, 1 Nov 1995 12:24:27 -0800 Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA26724 for ; Wed, 1 Nov 1995 12:24:23 -0800 Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD-4.4) id HAA19813 for current@freebsd.org; Thu, 2 Nov 1995 07:23:41 +1100 From: michael butler Message-Id: <199511012023.HAA19813@asstdc.scgt.oz.au> Subject: apparent tcp double-send ? To: current@freebsd.org Date: Thu, 2 Nov 1995 07:23:40 +1100 (EST) X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2913 Sender: owner-current@freebsd.org Precedence: bulk I noticed this whilst doing a little snooping .. ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: S 951910400:951910400(0) win 4096 (ttl 59, id 6771) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: S 951910400:951910400(0) win 4096 (ttl 58, id 6771) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: S 4154539922:4154539922(0) ack 951910401 win 16384 (ttl 64, id 12805) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: S 4154539922:4154539922(0) ack 951910401 win 16384 (ttl 63, id 12805) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: . ack 1 win 4096 (ttl 59, id 6772) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: . ack 1 win 4096 (ttl 58, id 6772) asstdc.scgt.oz.au.4957 > ppp1.asstdc.com.au.auth: S 4154580138:4154580138(0) win 16384 ppp1.asstdc.com.au.auth: S 4154580138:4154580138(0) win 16384 asstdc.scgt.oz.au.http: P 1:282(281) ack 1 win 4096 (ttl 59, id 6773) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: P 1:282(281) ack 1 win 4096 (ttl 58, id 6773) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: . ack 282 win 16103 (ttl 64, id 12812) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: . ack 282 win 16103 (ttl 63, id 12812) ppp1.asstdc.com.au.auth > asstdc.scgt.oz.au.4957: R 0:0(0) ack 4154580139 win 0 (ttl 59, id 6774) ppp1.asstdc.com.au.auth > asstdc.scgt.oz.au.4957: R 0:0(0) ack 1 win 0 (ttl 58, id 6774) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: P 1:101(100) ack 282 win 16384 (ttl 64, id 12825) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: . 101:613(512) ack 282 win 16384 (ttl 64, id 12826) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: P 1:101(100) ack 282 win 16384 (ttl 63, id 12825) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: . 101:613(512) ack 282 win 16384 (ttl 63, id 12826) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: FP 613:619(6) ack 282 win 16384 (ttl 64, id 12829) asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: FP 613:619(6) ack 282 win 16384 (ttl 63, id 12829) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: . ack 101 win 3996 (ttl 59, id 6775) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: . ack 101 win 3996 (ttl 58, id 6775) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: . ack 613 win 3584 (ttl 59, id 6776) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: . ack 613 win 3584 (ttl 58, id 6776) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: . ack 620 win 4090 (ttl 59, id 6777) ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: . ack 620 win 4090 (ttl 58, id 6777) ppp1 is connected via another -current machine which uses the same address for ethernet and ppp but no proxy arp. Strange MSS .. anyway, ppp1 is using Trumpet 2.0b .. is this BSD, Trumpet or TcpDump ? Suggestions ? michael From owner-freebsd-current Wed Nov 1 12:46:43 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA27294 for current-outgoing; Wed, 1 Nov 1995 12:46:43 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA27289 ; Wed, 1 Nov 1995 12:46:40 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id MAA01274; Wed, 1 Nov 1995 12:44:55 -0800 To: Julian Elischer cc: vince@apollo.COSC.GOV, roberto@keltia.freenix.fr, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-reply-to: Your message of "Wed, 01 Nov 1995 11:45:05 PST." <199511011945.LAA23144@ref.tfs.com> Date: Wed, 01 Nov 1995 12:44:55 -0800 Message-ID: <1272.815258695@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > > > > > So what you are saying is that -release is really just -current > > > at some point? and -stable is just really -current before a -release? > > > > NO. > NO? > I think he has it right eventhough he says it a bit oddly.. Well, odd or not, -stable is not -current at any sense. -current is an entirely separate branch, and "-release" doesn't even exist. I don't see how any answer other than "no" would have been correct! :-) Jordan From owner-freebsd-current Wed Nov 1 12:50:31 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA27423 for current-outgoing; Wed, 1 Nov 1995 12:50:31 -0800 Received: from alpha.netcraft.co.uk (alpha.netcraft.co.uk [194.72.238.8]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA27417 ; Wed, 1 Nov 1995 12:50:25 -0800 Received: (from paul@localhost) by alpha.netcraft.co.uk (8.6.12/8.6.9) id UAA00447; Wed, 1 Nov 1995 20:47:01 GMT From: Paul Richards Message-Id: <199511012047.UAA00447@alpha.netcraft.co.uk> Subject: Re: FreeBSD 2.1 update To: julian@ref.tfs.com (Julian Elischer) Date: Wed, 1 Nov 1995 20:46:56 +0000 (GMT) Cc: jkh@time.cdrom.com, vince@apollo.COSC.GOV, roberto@keltia.freenix.fr, jc@irbs.com, current@FreeBSD.ORG, FAQ@FreeBSD.ORG In-Reply-To: <199511011945.LAA23144@ref.tfs.com> from "Julian Elischer" at Nov 1, 95 11:45:05 am Reply-to: paul@netcraft.co.uk X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1018 Sender: owner-current@FreeBSD.ORG Precedence: bulk In reply to Julian Elischer who said > > NO? > I think he has it right eventhough he says it a bit oddly.. > > -current always moves forwards. > every so often a 'branch' is made that is eventually made into a release.. > What I'm not sure of myself, is whether -stable > derives from -current, or from a previous (unstable?) release. > (because we are effectively doing both at the moment) I think it would probably make sense for stable to continue as a 2.1 lineage until such time as current is felt stable enough to become a release candidate. If current is in development a long time there may be a 2.1.1 release or even a 2.1.2 Eventually though current will reach a point where it becomes a release candidate and a new 2.2 stable branch taken off it. I guess the 2.1 lineage would die at that point due to lack of resources. Just speculation on my part.... -- Paul Richards, Netcraft Ltd. Internet: paul@netcraft.co.uk, http://www.netcraft.co.uk Phone: 0370 462071 (Mobile), +44 1225 447500 (work) From owner-freebsd-current Wed Nov 1 12:56:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA27720 for current-outgoing; Wed, 1 Nov 1995 12:56:11 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA27715 ; Wed, 1 Nov 1995 12:56:08 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id MAA01356; Wed, 1 Nov 1995 12:53:46 -0800 To: paul@netcraft.co.uk cc: julian@ref.tfs.com (Julian Elischer), vince@apollo.COSC.GOV, roberto@keltia.freenix.fr, jc@irbs.com, current@FreeBSD.ORG, FAQ@FreeBSD.ORG Subject: Re: FreeBSD 2.1 update In-reply-to: Your message of "Wed, 01 Nov 1995 20:46:56 GMT." <199511012047.UAA00447@alpha.netcraft.co.uk> Date: Wed, 01 Nov 1995 12:53:45 -0800 Message-ID: <1353.815259225@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG Precedence: bulk > I think it would probably make sense for stable to continue as a 2.1 > lineage until such time as current is felt stable enough to become a release > candidate. If current is in development a long time there may be a 2.1.1 > release or even a 2.1.2 Substitute "may be" for "almost certainly will be" and I think you're closer to the mark! :) Jordan From owner-freebsd-current Wed Nov 1 14:32:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA00849 for current-outgoing; Wed, 1 Nov 1995 14:32:27 -0800 Received: from kryten.atinc.com (kryten.Atinc.COM [198.138.38.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA00842 ; Wed, 1 Nov 1995 14:32:16 -0800 Received: (jmb@localhost) by kryten.atinc.com (8.6.9/8.3) id RAA03446; Wed, 1 Nov 1995 17:19:40 -0500 Date: Wed, 1 Nov 1995 17:19:39 -0500 (EST) From: "Jonathan M. Bresler" Subject: Re: Time problems To: "Rodney W. Grimes" cc: Bruce Evans , gibbs@freefall.freebsd.org, wollman@lcs.mit.edu, current@FreeBSD.org, wollman@FreeBSD.org In-Reply-To: <199511010908.BAA09757@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Rodney W. Grimes wrote: > CPU: Intel Pentium Processor clocked at 99.85 Mhz (Pentium class CPU) > > makes a lot more since to me! Also note the current messeage is not > properly marking Pentium as a trademark, and wrongly using Pentium as > a noun :-(. a 586 by any other name.....kills two errors with one demystification. Jonathan M. Bresler jmb@kryten.atinc.com | Analysis & Technology, Inc. FreeBSD Postmaster jmb@FreeBSD.Org | 2341 Jeff Davis Hwy play go. | Arlington, VA 22202 ride bike. hack FreeBSD.--ah the good life | 703-418-2800 x346 From owner-freebsd-current Wed Nov 1 19:09:35 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA08699 for current-outgoing; Wed, 1 Nov 1995 19:09:35 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id TAA08693 for ; Wed, 1 Nov 1995 19:09:30 -0800 Received: from fw.ast.com by ast.com with SMTP id AA21092 (5.67b/IDA-1.5 for ); Wed, 1 Nov 1995 19:10:40 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tApXu-00008GC; Wed, 1 Nov 95 20:38 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0tApWM-000IvyC; Wed, 1 Nov 95 20:36 WET Message-Id: Date: Wed, 1 Nov 95 20:36 WET To: current@FreeBSD.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Wed Nov 1 1995, 20:36:50 CST Subject: Re: Time problems Sender: owner-current@FreeBSD.org Precedence: bulk [3]Bruce Evans writes: [3]Perhaps the 8254 clock is being accessed too fast. Try adding some delays [3]before each inb() and outb() in clock.c:getit(). Count to 100 or so to [3]get at least 1 usec delay. Uh, I don't think this will work as you expect on a Pentium or a P6. It is too easy for the parallel integer unit(s) to execute the inb/outbs in one unit and do the nice delay loop in the other, thus wrecking your timing delay. On the Pentium and up you must force these types of "timed" instruction sequences to be done sequentially. Execution Time is no longer linear.... :-) I am chasing a bug in the printer driver (-STROBE pulse timing is out of spec) as we write that is probably caused by someone assuming that *all* the instructions would execute in the order they were coded. Not anymore. In *general* you are guaranteed that IN and OUT instructions will generate -IOR and -IOW cycles in the order they were coded, but any code that has no dependencies/effects on the IN/OUT opcodes can be executed out of order in relation to the IN/OUT opcodes. So if the purpose of that code is to place a timing delta between IN/OUT instructions, it probably won't do the job *consistently*. It can vary on a given processor depending on which IU was available on entry to the routine at a given instant. Yucky. If the inbs and outbs were actually calls to inbs and outbs rather than being inline, the serialization problems tend to go away. At least on the Pentium. This may not be the case on the P6 and other processors with multiple execution units. See the Pentium songbook for less information on how to deal with this issue. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Wed Nov 1 19:48:17 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA10267 for current-outgoing; Wed, 1 Nov 1995 19:48:17 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA10257 ; Wed, 1 Nov 1995 19:48:12 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id TAA12633; Wed, 1 Nov 1995 19:41:26 -0800 Date: Wed, 1 Nov 1995 19:41:25 -0800 (PST) From: -Vince- To: Ollivier Robert cc: julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <199511011605.RAA17313@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Ollivier Robert wrote: > It seems that -Vince- said: > > > At some point after 2.1, -CURRENT will probably become 2.3-CURRENT and > > > -STABLE will be 2.2-STABLE to end up with 2.2-RELEASE and so on. > > > > So what you are saying is that -release is really just -current > > at some point? and -stable is just really -current before a -release? > > Not really. > > What we have *now* is: > > * 2.1-STABLE will become 2.1-RELEASE > * 2.2-CURRENT aka "the Bleeding Edge(tm)". Yes, but won't people in 2.1-RELEASE when it comes out be supping -CURRENT once again? > What we will [probably] have is > > * 2.2-CURRENT become 2.2-STABLE after 2.1-RELEASE is out. It is intended to > be 2.2-RELEASE one day. > > When 2.2-STABLE begins its life, 2.3-CURRENT will begin and so on. > > Note as I'm not part of the core team so what is above are only my > thoughts, they may want to change the numbers :-) Oh okay, it seems like everyone has a different way of explaining this =) Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Wed Nov 1 19:59:32 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA10806 for current-outgoing; Wed, 1 Nov 1995 19:59:32 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA10797 ; Wed, 1 Nov 1995 19:59:24 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id TAA14080; Wed, 1 Nov 1995 19:53:52 -0800 Date: Wed, 1 Nov 1995 19:53:51 -0800 (PST) From: -Vince- To: Julian Elischer cc: "Jordan K. Hubbard" , roberto@keltia.freenix.fr, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <199511011945.LAA23144@ref.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Julian Elischer wrote: > > > > > So what you are saying is that -release is really just -current > > > at some point? and -stable is just really -current before a -release? > > > > NO. > NO? > I think he has it right eventhough he says it a bit oddly.. Well, it was like 2am and I was up for 20 hours sitting here so I wasn't exactly awake ;) > -current always moves forwards. > every so often a 'branch' is made that is eventually made into a release.. > What I'm not sure of myself, is whether -stable > derives from -current, or from a previous (unstable?) release. > (because we are effectively doing both at the moment) That is what I wanted to know since I noticed after every release, people will sup -CURRENT and then like there will be a ALPHA, BETA, GAMMA version but now it seems like there is only SNAP, and STABLE whatever that is... Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Wed Nov 1 20:23:19 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA11937 for current-outgoing; Wed, 1 Nov 1995 20:23:19 -0800 Received: from bacchus.eng.umd.edu (bacchus.eng.umd.edu [129.2.94.5]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA11928 ; Wed, 1 Nov 1995 20:23:13 -0800 Received: from latte.eng.umd.edu (latte.eng.umd.edu [129.2.98.15]) by bacchus.eng.umd.edu (8.7/8.7) with ESMTP id XAA03433; Wed, 1 Nov 1995 23:16:54 -0500 (EST) Received: (chuckr@localhost) by latte.eng.umd.edu (8.7/8.6.4) id XAA26823; Wed, 1 Nov 1995 23:16:53 -0500 (EST) Date: Wed, 1 Nov 1995 23:16:53 -0500 (EST) From: Chuck Robey X-Sender: chuckr@latte.eng.umd.edu To: -Vince- cc: Ollivier Robert , julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, -Vince- wrote: > On Wed, 1 Nov 1995, Ollivier Robert wrote: > > > It seems that -Vince- said: > > > > At some point after 2.1, -CURRENT will probably become 2.3-CURRENT and > > > > -STABLE will be 2.2-STABLE to end up with 2.2-RELEASE and so on. > > > > > > So what you are saying is that -release is really just -current > > > at some point? and -stable is just really -current before a -release? > > > > Not really. > > > > What we have *now* is: > > > > * 2.1-STABLE will become 2.1-RELEASE > > * 2.2-CURRENT aka "the Bleeding Edge(tm)". > > Yes, but won't people in 2.1-RELEASE when it comes out be supping > -CURRENT once again? > > > What we will [probably] have is > > > > * 2.2-CURRENT become 2.2-STABLE after 2.1-RELEASE is out. It is intended to > > be 2.2-RELEASE one day. > > > > When 2.2-STABLE begins its life, 2.3-CURRENT will begin and so on. > > > > Note as I'm not part of the core team so what is above are only my > > thoughts, they may want to change the numbers :-) > > Oh okay, it seems like everyone has a different way of explaining > this =) Maybe that's right, but it's not what I understood to be true. Understand that this stuff is not written in stone, there are no contracts forcing things to happen in any particular manner, but I had the understanding that we were going to be doing a dual-track thing. The even numbered releases were to be ones that would concentrate on stability, and so the possibility of these being late would be kinda high. Balancing this out would be the odd numbered releases, which would satisfy those (like me) that wanted more frequent releases. The combination, it was to be hoped, might possibly satisfy those of both camps. Using this thinking, there will not be a 2.2 stable, just a 2.2 RELEASE, and the next stable target, for those using FreeBSD for more than a hobby, would be 2.4. > > Cheers, > -Vince- vince@COSC.GOV - GUS Mailing Lists Admin > UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) > Chabot Observatory & Science Center - Board of Advisors > Running FreeBSD - Real UN*X for Free! > Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin > > ========================================================================== Chuck Robey chuckr@eng.umd.edu, I run FreeBSD-current on n3lxx + Journey2 Three Accounts for the Super-users in the sky, Seven for the Operators in their halls of fame, Nine for Ordinary Users doomed to crie, One for the Illegal Cracker with his evil game In the Domains of Internet where the data lie. One Account to rule them all, One Account to watch them, One Account to make them all and in the network bind them. From owner-freebsd-current Wed Nov 1 21:17:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA14620 for current-outgoing; Wed, 1 Nov 1995 21:17:41 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA14615 ; Wed, 1 Nov 1995 21:17:39 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id VAA24956; Wed, 1 Nov 1995 21:11:52 -0800 Date: Wed, 1 Nov 1995 21:11:51 -0800 (PST) From: -Vince- To: "Jordan K. Hubbard" cc: Julian Elischer , roberto@keltia.freenix.fr, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <1272.815258695@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Jordan K. Hubbard wrote: > > > > > > > So what you are saying is that -release is really just -current > > > > at some point? and -stable is just really -current before a -release? > > > > > > NO. > > NO? > > I think he has it right eventhough he says it a bit oddly.. > > Well, odd or not, -stable is not -current at any sense. -current is > an entirely separate branch, and "-release" doesn't even exist. > I don't see how any answer other than "no" would have been > correct! :-) Sorry I wasn't asking the question more clearly but what I meant is isn't the -stable like branch off -current and then when -stable becomes the next -release version, wouldn't the src tree for supping just be the -current tree for development of future releases or will future releases simply be bugfixes to the last release? Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Wed Nov 1 21:18:07 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA14667 for current-outgoing; Wed, 1 Nov 1995 21:18:07 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA14658 ; Wed, 1 Nov 1995 21:18:01 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id VAA28280; Wed, 1 Nov 1995 21:16:31 -0800 To: -Vince- cc: Ollivier Robert , julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-reply-to: Your message of "Wed, 01 Nov 1995 19:41:25 PST." Date: Wed, 01 Nov 1995 21:16:30 -0800 Message-ID: <28274.815289390@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > Yes, but won't people in 2.1-RELEASE when it comes out be supping > -CURRENT once again? I certainly hope not! :-) Jordan From owner-freebsd-current Wed Nov 1 22:11:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA16514 for current-outgoing; Wed, 1 Nov 1995 22:11:11 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA16504 ; Wed, 1 Nov 1995 22:11:08 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id WAA20044; Wed, 1 Nov 1995 22:08:08 -0800 To: Chuck Robey cc: -Vince- , Ollivier Robert , julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-reply-to: Your message of "Wed, 01 Nov 1995 23:16:53 EST." Date: Wed, 01 Nov 1995 22:08:08 -0800 Message-ID: <20042.815292488@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > Maybe that's right, but it's not what I understood to be true. Understand > that this stuff is not written in stone, there are no contracts forcing > things to happen in any particular manner, but I had the understanding > that we were going to be doing a dual-track thing. The even numbered The problem is that the dual-track thing is turning into a LOT of work, and I don't think that David is entirely amused at the amount of life he's lost in keeping things in sync.. What will no doubt evolve is something more "holistic" where we maintain the 2.1 release branch as long as it seems practical to do so (e.g. as long as it makes sense to continue releasing bug-fix point releases along it) and beaver away in 2.2 as the catch-all experiemental branch. At some stage, I'd hope that 2.2 would slow down enough to become stable, at which point (perhaps just short of the point of most ideal stability) maybe we'll just branch again and let 2.2 become what 2.1 is now, with 2.3 becoming -current. I don't know though, we could end up doing something entirely different than this. This is one of those things that's really difficult to do advance planning for in a volunteer effort. Sometimes we move really fast, other times we slow to a crawl. Sometimes we fix something really critical and we'd really like to see it in a release, other times we break the tree pretty badly for awhile with a new experimental feature that eventually turns out to be worth the effort but is a pain in the butt during the transition period. I do know that we have very finite engineering resources, and we need to apply them in the most cost-effective manner or we will simply cease to exist. Striking a balance between this and what the users want is the challenge we'll be facing over the next 12 months or so, and this will effect how the releases are numbered and planned. Jordan From owner-freebsd-current Wed Nov 1 23:46:23 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA20020 for current-outgoing; Wed, 1 Nov 1995 23:46:23 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA20015 ; Wed, 1 Nov 1995 23:46:18 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id XAA10904; Wed, 1 Nov 1995 23:40:13 -0800 Date: Wed, 1 Nov 1995 23:40:12 -0800 (PST) From: -Vince- To: Chuck Robey cc: Ollivier Robert , julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Chuck Robey wrote: > On Wed, 1 Nov 1995, -Vince- wrote: > > > On Wed, 1 Nov 1995, Ollivier Robert wrote: > > > > > It seems that -Vince- said: > > > > > At some point after 2.1, -CURRENT will probably become 2.3-CURRENT and > > > > > -STABLE will be 2.2-STABLE to end up with 2.2-RELEASE and so on. > > > > > > > > So what you are saying is that -release is really just -current > > > > at some point? and -stable is just really -current before a -release? > > > > > > Not really. > > > > > > What we have *now* is: > > > > > > * 2.1-STABLE will become 2.1-RELEASE > > > * 2.2-CURRENT aka "the Bleeding Edge(tm)". > > > > Yes, but won't people in 2.1-RELEASE when it comes out be supping > > -CURRENT once again? > > > > > What we will [probably] have is > > > > > > * 2.2-CURRENT become 2.2-STABLE after 2.1-RELEASE is out. It is intended to > > > be 2.2-RELEASE one day. > > > > > > When 2.2-STABLE begins its life, 2.3-CURRENT will begin and so on. > > > > > > Note as I'm not part of the core team so what is above are only my > > > thoughts, they may want to change the numbers :-) > > > > Oh okay, it seems like everyone has a different way of explaining > > this =) > > Maybe that's right, but it's not what I understood to be true. Understand > that this stuff is not written in stone, there are no contracts forcing > things to happen in any particular manner, but I had the understanding > that we were going to be doing a dual-track thing. The even numbered > releases were to be ones that would concentrate on stability, and so the > possibility of these being late would be kinda high. Balancing this out > would be the odd numbered releases, which would satisfy those (like me) > that wanted more frequent releases. The combination, it was to be hoped, > might possibly satisfy those of both camps. Using this thinking, there > will not be a 2.2 stable, just a 2.2 RELEASE, and the next stable target, > for those using FreeBSD for more than a hobby, would be 2.4. Hmmm, but if -stable is turned to RELEASE, what happens to the next stable? Is it just based on the on-going -CURRENT release after the RELEASE? I'm just confused =) Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Wed Nov 1 23:57:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA20535 for current-outgoing; Wed, 1 Nov 1995 23:57:20 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA20529 ; Wed, 1 Nov 1995 23:57:14 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id XAA11547; Wed, 1 Nov 1995 23:51:10 -0800 Date: Wed, 1 Nov 1995 23:51:10 -0800 (PST) From: -Vince- To: "Jordan K. Hubbard" cc: Ollivier Robert , julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <28274.815289390@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Jordan K. Hubbard wrote: > > Yes, but won't people in 2.1-RELEASE when it comes out be supping > > -CURRENT once again? > > I certainly hope not! :-) Hmmm, but isn't that the case since when people install the release version and sup, they always end up with -CURRENT =) Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Thu Nov 2 00:10:28 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA20981 for current-outgoing; Thu, 2 Nov 1995 00:10:28 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA20973 ; Thu, 2 Nov 1995 00:10:24 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id AAA24057; Thu, 2 Nov 1995 00:08:47 -0800 To: -Vince- cc: Ollivier Robert , julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-reply-to: Your message of "Wed, 01 Nov 1995 23:51:10 PST." Date: Thu, 02 Nov 1995 00:08:47 -0800 Message-ID: <24055.815299727@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > Hmmm, but isn't that the case since when people install the > release version and sup, they always end up with -CURRENT =) You forget that there's more than one sup collection. They could also sup stable! Jordan From owner-freebsd-current Thu Nov 2 00:45:00 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA21927 for current-outgoing; Thu, 2 Nov 1995 00:45:00 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA21922 ; Thu, 2 Nov 1995 00:44:57 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id AAA13170; Thu, 2 Nov 1995 00:38:46 -0800 Date: Thu, 2 Nov 1995 00:38:44 -0800 (PST) From: -Vince- To: "Jordan K. Hubbard" cc: Ollivier Robert , julian@ref.tfs.com, jc@irbs.com, current@FreeBSD.org, FAQ@FreeBSD.org Subject: Re: FreeBSD 2.1 update In-Reply-To: <24055.815299727@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Thu, 2 Nov 1995, Jordan K. Hubbard wrote: > > Hmmm, but isn't that the case since when people install the > > release version and sup, they always end up with -CURRENT =) > > You forget that there's more than one sup collection. They could also > sup stable! Well, when 2.05R was out, that was only -CURRENT and then -stable came out sometime later.... I think I'm just confused now.. =) Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Thu Nov 2 00:47:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA22009 for current-outgoing; Thu, 2 Nov 1995 00:47:13 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA22003 for ; Thu, 2 Nov 1995 00:47:07 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id AAA13226; Thu, 2 Nov 1995 00:40:53 -0800 Date: Thu, 2 Nov 1995 00:40:51 -0800 (PST) From: -Vince- To: current@FreeBSD.ORG Subject: schg flag on make world in -CURRENT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk Hi everyone, Does anyone know why the make world in the 11/1/95 -CURRENT keeps making many binaries with the schg flag and then when I do a make world, it will not overwrite the files since it can't delete the file? Thanks! Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Thu Nov 2 00:54:13 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id AAA22182 for current-outgoing; Thu, 2 Nov 1995 00:54:13 -0800 Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id AAA22177 for ; Thu, 2 Nov 1995 00:54:10 -0800 Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.6.12/8.6.12) id AAA10537; Thu, 2 Nov 1995 00:52:44 -0800 From: "Rodney W. Grimes" Message-Id: <199511020852.AAA10537@GndRsh.aac.dev.com> Subject: Re: Time problems To: uhclem%nemesis@fw.ast.com (Frank Durda IV) Date: Thu, 2 Nov 1995 00:52:43 -0800 (PST) Cc: current@FreeBSD.org In-Reply-To: from "Frank Durda IV" at Nov 1, 95 08:36:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 978 Sender: owner-current@FreeBSD.org Precedence: bulk > > [3]Bruce Evans writes: > [3]Perhaps the 8254 clock is being accessed too fast. Try adding some delays > [3]before each inb() and outb() in clock.c:getit(). Count to 100 or so to > [3]get at least 1 usec delay. > > Uh, I don't think this will work as you expect on a Pentium or a P6. It is > too easy for the parallel integer unit(s) to execute the inb/outbs in one > unit and do the nice delay loop in the other, thus wrecking your timing delay. > On the Pentium and up you must force these types of "timed" instruction > sequences to be done sequentially. > > Execution Time is no longer linear.... :-) ... I suggest you go read the book again, IN and OUT instructions are ``serailization'' instuctions. All code between them will have _completed_ execution before the external cycle runs. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Thu Nov 2 01:11:15 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA22786 for current-outgoing; Thu, 2 Nov 1995 01:11:15 -0800 Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id BAA22781 for ; Thu, 2 Nov 1995 01:11:10 -0800 Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (5.x/csrelayMX-SVR4_1.1tmp/RB) id AA27655; Thu, 2 Nov 1995 10:10:49 +0100 Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB) id KAA21257; Thu, 2 Nov 1995 10:10:45 +0100 Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4) id KAA17471; Thu, 2 Nov 1995 10:10:45 +0100 To: michael butler Cc: current@freebsd.org Subject: Re: apparent tcp double-send ? In-Reply-To: Your message of "Thu, 02 Nov 1995 07:23:40 +1100." <199511012023.HAA19813@asstdc.scgt.oz.au> Date: Thu, 02 Nov 1995 10:10:44 +0100 Message-Id: <17470.815303444@curie.cs.utwente.nl> From: Andras Olah Sender: owner-current@freebsd.org Precedence: bulk On Thu, 02 Nov 1995 07:23:40 +1100, michael butler wrote: > I noticed this whilst doing a little snooping .. > > ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: S 951910400:951910400(0) win 4096 (ttl 59, id 6771) > ppp1.asstdc.com.au.1091 > asstdc.scgt.oz.au.http: S 951910400:951910400(0) win 4096 (ttl 58, id 6771) > asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: S 4154539922:4154539922(0) ack 951910401 win 16384 (ttl 64, id 12805) > asstdc.scgt.oz.au.http > ppp1.asstdc.com.au.1091: S 4154539922:4154539922(0) ack 951910401 win 16384 (ttl 63, id 12805) [ ... ] > ppp1 is connected via another -current machine which uses the same address > for ethernet and ppp but no proxy arp. Strange MSS .. anyway, ppp1 is using > Trumpet 2.0b .. is this BSD, Trumpet or TcpDump ? Suggestions ? The duplicates are caused by some routing anomaly. Notice that the TTL of the duplicate is always one less than that of the original. As for the MSS, they're OK. Please notice that the behavior of FreeBSD changed by 2.0.5R, because the original BSD treatment of MSS was not correct. The MSS you send should depend only on the capabilities of your i/f, but not on the route. It's the responsibility of the other end, which recieves your MSS, to calculate its optimum outgoing segment size based on your MSS option and on the route's MTU. Andras From owner-freebsd-current Thu Nov 2 07:44:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA03712 for current-outgoing; Thu, 2 Nov 1995 07:44:18 -0800 Received: from fieber-john.campusview.indiana.edu (Fieber-John.campusview.indiana.edu [149.159.1.34]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA03703 for ; Thu, 2 Nov 1995 07:44:14 -0800 Received: (from jfieber@localhost) by fieber-john.campusview.indiana.edu (8.6.12/8.6.12) id KAA26205; Thu, 2 Nov 1995 10:44:02 -0500 Date: Thu, 2 Nov 1995 10:44:01 -0500 (EST) From: John Fieber X-Sender: jfieber@fieber-john.campusview.indiana.edu To: "Rodney W. Grimes" cc: Ollivier Robert , vince@apollo.COSC.GOV, current@FreeBSD.org Subject: Re: make world failed with -current In-Reply-To: <199511011822.KAA10044@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.org Precedence: bulk On Wed, 1 Nov 1995, Rodney W. Grimes wrote: > > Go to /usr/src/usr.bin/sgmlfmt, "make all install", then try again. > > Please add sgmlfmt to the ``tools:'' target of /usr/src/Makefile. I've asked a couple times about doing this. The first time received some grumbles, the second time recieved no replies. Since a source upgrade from 2.0.5 to either stable or current *WILL* break because of this, barring any complaints I will put this in to both current *and* stable. Once the sgml tools stablize, they can probably be safely removed from the target. -john == jfieber@indiana.edu =========================================== == http://fieber-john.campusview.indiana.edu/~jfieber ============ From owner-freebsd-current Thu Nov 2 07:55:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA04069 for current-outgoing; Thu, 2 Nov 1995 07:55:41 -0800 Received: from plains.nodak.edu (89@plains.NoDak.edu [134.129.111.64]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id HAA04064 for ; Thu, 2 Nov 1995 07:55:36 -0800 Received: (from tinguely@localhost) by plains.nodak.edu (8.6.11/8.6.10) id JAA17082; Thu, 2 Nov 1995 09:55:31 -0600 Date: Thu, 2 Nov 1995 09:55:31 -0600 From: Mark Tinguely Message-Id: <199511021555.JAA17082@plains.nodak.edu> To: freebsd-current@freebsd.org Subject: Matrox meteor (sys/pci/meteor.c) patch Cc: james@miller.cs.uwm.edu Content-Length: 1980 Sender: owner-current@freebsd.org Precedence: bulk I visually found an error in the /sys/pci/meteor.c Matrox Meteor video capture driver in the setting the frequency for SECAM, and AUTO modes. Secam and PAL use 50 Hz, while NTSC uses 60 Hz. Automode should not also set 60Hz, though I think that setting will get ignored. (note to Jim Lowe, when I sent this patch to you last week, I set the 0x40 (60Hz field select) bit on the 0x0f register for SECAM, it should be the 0x20 (Secam Cross Color Reduction). below is now correct. ) these changes are also at: ftp://joy.cs.ndsu.nodak.edu/pub/meteor... --mark. *** meteor.c.orig Tue Oct 24 08:40:21 1995 --- meteor.c Tue Oct 24 08:46:03 1995 *************** *** 36,41 **** --- 36,43 ---- 8/29/95 Fixes suggested by Bruce Evans. meteor_mmap should return -1 on error rather than 0. unit # > NMETEOR should be unit # >= NMETEOR. + 10/24/95 Turn 50 Hz processing for SECAM and 60 Hz processing + off for AUTOMODE. */ #include "meteor.h" *************** *** 891,897 **** SAA7196_WRITE(mtr, 0x0d, (SAA7196_REG(mtr, 0x0d) & ~0x01) | 0x1); SAA7196_WRITE(mtr, 0x0f, ! (SAA7196_REG(mtr, 0x0f) & ~0xe0) | 0xe0); SAA7196_WRITE(mtr, 0x22, 0x00); SAA7196_WRITE(mtr, 0x24, (SAA7196_REG(mtr, 0x24) | 0x0c)); --- 893,899 ---- SAA7196_WRITE(mtr, 0x0d, (SAA7196_REG(mtr, 0x0d) & ~0x01) | 0x1); SAA7196_WRITE(mtr, 0x0f, ! (SAA7196_REG(mtr, 0x0f) & ~0xe0) | 0x20); SAA7196_WRITE(mtr, 0x22, 0x00); SAA7196_WRITE(mtr, 0x24, (SAA7196_REG(mtr, 0x24) | 0x0c)); *************** *** 905,911 **** SAA7196_WRITE(mtr, 0x0d, (SAA7196_REG(mtr, 0x0d) & ~0x01)); SAA7196_WRITE(mtr, 0x0f, ! (SAA7196_REG(mtr, 0x0f) & ~0xc0) | 0xc0); break; default: return EINVAL; --- 907,913 ---- SAA7196_WRITE(mtr, 0x0d, (SAA7196_REG(mtr, 0x0d) & ~0x01)); SAA7196_WRITE(mtr, 0x0f, ! (SAA7196_REG(mtr, 0x0f) & ~0xc0) | 0x80); break; default: return EINVAL; From owner-freebsd-current Thu Nov 2 08:45:29 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA06473 for current-outgoing; Thu, 2 Nov 1995 08:45:29 -0800 Received: from dtr.com (dtr.rain.com [204.119.8.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA06468 for ; Thu, 2 Nov 1995 08:45:24 -0800 From: bmk@dtr.com Received: (from bmk@localhost) by dtr.com (8.6.11/8.6.9) id IAA00686; Thu, 2 Nov 1995 08:43:43 -0800 Message-Id: <199511021643.IAA00686@dtr.com> Subject: Re: make world failed with -current To: jfieber@indiana.edu (John Fieber) Date: Thu, 2 Nov 1995 08:43:43 -0800 (PST) Cc: rgrimes@gndrsh.aac.dev.com, roberto@keltia.freenix.fr, vince@apollo.COSC.GOV, current@FreeBSD.org In-Reply-To: from "John Fieber" at Nov 2, 95 10:44:01 am Reply-To: bmk@dtr.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2557 Sender: owner-current@FreeBSD.org Precedence: bulk > On Wed, 1 Nov 1995, Rodney W. Grimes wrote: > > > Go to /usr/src/usr.bin/sgmlfmt, "make all install", then try again. > > > > Please add sgmlfmt to the ``tools:'' target of /usr/src/Makefile. > I've asked a couple times about doing this. The first time received some > grumbles, the second time recieved no replies. Since a source upgrade > from 2.0.5 to either stable or current *WILL* break because of this, > barring any complaints I will put this in to both current *and* stable. > Once the sgml tools stablize, they can probably be safely removed from > the target. I've encountered several other problems building -current on a 2.0.5 system. I've found workarounds for all of them except one. gnu/usr.bin/groff/pic won't build, it complains of an unterminated character constant. (This is using sources obtained via CTM on Oct. 31). |cc -O -I. -I/usr/src/gnu/usr.bin/groff/pic/../include -DHAVE_UNISTD_H=1 |-DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_SYS_DIR_H=1 |-DHAVE_CC_LIMITS_H=1 -DHAVE_CC_UNISTD_H=1 -DSTDLIB_H_DECLARES_GETOPT=1 |-DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 |-DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DRETSIGTYPE=void |-DHAVE_MMAP=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_SYS_SIGLIST=1 -c |pic.c |pic.y:1630: unterminated character constant |*** Error code 1 As a workaround, I commented the pic subdir from the groff makefile and did a make world. I was then able to compile the sources and get everything installed. Now, even running with 2.2-current kernel, libraries, and binaries, I can't get gnu/usr.bin/groff/pic to compile. Bummer. One other problem is that if for whatever reason 'make all' fails to complete after compiling bin/sh, a 'make clean' must be done in bin/sh in order to continue the 'make all'. Is this clear? |bmk@everest (507) $ cd /usr/src/bin/sh |bmk@everest (508) $ make all |cc -O -DSHELL -I. -I/usr/src/bin/sh -static |/usr/src/bin/sh/builtins.c -o /usr/src/bin/sh/builtins |/usr/lib/scrt0.o: Undefined symbol `_main' referenced from text segment |/var/tmp/cc0006771.o: Undefined symbol `_bltincmd' referenced from text segment |/var/tmp/cc0006771.o: Undefined symbol `_bgcmd' referenced from text segment |/var/tmp/cc0006771.o: Undefined symbol `_breakcmd' referenced from text segment |/var/tmp/cc0006771.o: Undefined symbol `_cdcmd' referenced from text segment |/var/tmp/cc0006771.o: Undefined symbol `_dotcmd' referenced from text segment |/var/tmp/cc0006771.o: Undefined symbol `_echocmd' referenced from text segment From owner-freebsd-current Thu Nov 2 08:57:25 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA06971 for current-outgoing; Thu, 2 Nov 1995 08:57:25 -0800 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA06966 for ; Thu, 2 Nov 1995 08:57:18 -0800 Received: from olympus by devnull (8.6.8/8.6.6) id KAA20320; Thu, 2 Nov 1995 10:56:27 -0600 Received: by olympus (4.1/TSS2.1) id AA11177; Thu, 2 Nov 95 10:56:32 CST From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9511021656.AA11177@olympus> Subject: pppd won't hold connection To: current@freebsd.org Date: Thu, 2 Nov 1995 10:56:31 -0600 (CST) X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 447 Sender: owner-current@freebsd.org Precedence: bulk Has anything changed in the ppp kernel code? I noticed new stuff supped. It won't hold a connection now. The new executable is working with the old kernel. I was on the commit list. I guess I have fallen off. Thanks, Boyd -- _______________________________________________________________________ Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner _______________________________________________________________________ From owner-freebsd-current Thu Nov 2 09:01:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA07137 for current-outgoing; Thu, 2 Nov 1995 09:01:16 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id JAA07129 for ; Thu, 2 Nov 1995 09:01:10 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA03187; Thu, 2 Nov 1995 12:00:55 -0500 Date: Thu, 2 Nov 1995 12:00:55 -0500 From: "Garrett A. Wollman" Message-Id: <9511021700.AA03187@halloran-eldar.lcs.mit.edu> To: -Vince- Cc: current@FreeBSD.ORG Subject: schg flag on make world in -CURRENT In-Reply-To: References: Sender: owner-current@FreeBSD.ORG Precedence: bulk < said: > Does anyone know why the make world in the 11/1/95 -CURRENT keeps > making many binaries with the schg flag and then when I do a make world, > it will not overwrite the files since it can't delete the file? Thanks! Because your kernel is in secure mode. You can't do a `make world' in secure mode. See init(8) and the definition of `securelevel' in kern/kern_sysctl.c. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu Nov 2 09:15:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA07514 for current-outgoing; Thu, 2 Nov 1995 09:15:20 -0800 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA07507 for ; Thu, 2 Nov 1995 09:15:13 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA17328; Thu, 2 Nov 1995 10:17:30 -0700 Date: Thu, 2 Nov 1995 10:17:30 -0700 From: Nate Williams Message-Id: <199511021717.KAA17328@rocky.sri.MT.net> To: faulkner@mpd.tandem.com (Boyd Faulkner) Cc: current@freebsd.org Subject: Re: pppd won't hold connection In-Reply-To: <9511021656.AA11177@olympus> References: <9511021656.AA11177@olympus> Sender: owner-current@freebsd.org Precedence: bulk > Has anything changed in the ppp kernel code? Yep. > I noticed new stuff supped. > It won't hold a connection now. The new executable is working with the > old kernel. Re-build the kernel and see if it makes any difference. Peter made lots of changes made to both the userland stuff and the kernel. Nate From owner-freebsd-current Thu Nov 2 09:21:14 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA07779 for current-outgoing; Thu, 2 Nov 1995 09:21:14 -0800 Received: from devnull (devnull.mpd.tandem.com [131.124.4.29]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA07771 for ; Thu, 2 Nov 1995 09:21:07 -0800 Received: from olympus by devnull (8.6.8/8.6.6) id LAA21647; Thu, 2 Nov 1995 11:20:19 -0600 Received: by olympus (4.1/TSS2.1) id AA11354; Thu, 2 Nov 95 11:20:29 CST From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9511021720.AA11354@olympus> Subject: Re: pppd won't hold connection To: nate@rocky.sri.MT.net (Nate Williams) Date: Thu, 2 Nov 1995 11:20:28 -0600 (CST) Cc: faulkner@devnull, current@freebsd.org In-Reply-To: <199511021717.KAA17328@rocky.sri.MT.net> from "Nate Williams" at Nov 2, 95 10:17:30 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 824 Sender: owner-current@freebsd.org Precedence: bulk > > > Has anything changed in the ppp kernel code? > > Yep. > > > I noticed new stuff supped. > > It won't hold a connection now. The new executable is working with the > > old kernel. > > Re-build the kernel and see if it makes any difference. Peter made lots > of changes made to both the userland stuff and the kernel. > > > > Nate > I tried the new kernel first. It did not work for me. I am rebuilding again in hopes that the problem will go away. I assume it is working for everyone else. Fortunately, the old kernel still works so I can resup if this doesn't fix it. Thanks, Boyd -- _______________________________________________________________________ Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner _______________________________________________________________________ From owner-freebsd-current Thu Nov 2 09:23:20 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA07843 for current-outgoing; Thu, 2 Nov 1995 09:23:20 -0800 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA07838 for ; Thu, 2 Nov 1995 09:23:14 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA17355; Thu, 2 Nov 1995 10:25:28 -0700 Date: Thu, 2 Nov 1995 10:25:28 -0700 From: Nate Williams Message-Id: <199511021725.KAA17355@rocky.sri.MT.net> To: faulkner@mpd.tandem.com (Boyd Faulkner) Cc: current@freebsd.org Subject: Re: pppd won't hold connection In-Reply-To: <9511021720.AA11354@olympus> References: <199511021717.KAA17328@rocky.sri.MT.net> <9511021720.AA11354@olympus> Sender: owner-current@freebsd.org Precedence: bulk [ PPP changes in the kernel and user-land code ] > I tried the new kernel first. It did not work for me. I am rebuilding > again in hopes that the problem will go away. I assume it is working for > everyone else. I haven't had a chance to re-build a new kernel. > Fortunately, the old kernel still works so I can resup if this doesn't > fix it. I'd resup if I were you, since the commits were over a large enough period of time that you may have only gotten parts of them and not all of them. Nate From owner-freebsd-current Thu Nov 2 09:36:47 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA08142 for current-outgoing; Thu, 2 Nov 1995 09:36:47 -0800 Received: from haywire.DIALix.COM (news@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA08133 for ; Thu, 2 Nov 1995 09:36:41 -0800 Received: (from news@localhost) by haywire.DIALix.COM (sendmail) id BAA02900 for freebsd-current@freebsd.org; Fri, 3 Nov 1995 01:36:21 +0800 (WST) Received: from GATEWAY by haywire.DIALix.COM with netnews for freebsd-current@freebsd.org (problems to: usenet@haywire.dialix.com) To: freebsd-current@freebsd.org Date: 3 Nov 1995 01:36:16 +0800 From: peter@haywire.dialix.com (Peter Wemm) Message-ID: <47avig$2qg$1@haywire.DIALix.COM> Organization: DIALix Services, Perth, Australia. References: <9511021656.AA11177@olympus>, <199511021717.KAA17328@rocky.sri.MT.net> Subject: Re: pppd won't hold connection Sender: owner-current@freebsd.org Precedence: bulk nate@rocky.sri.MT.net (Nate Williams) writes: >> Has anything changed in the ppp kernel code? >Yep. >> I noticed new stuff supped. >> It won't hold a connection now. The new executable is working with the >> old kernel. >Re-build the kernel and see if it makes any difference. Peter made lots >of changes made to both the userland stuff and the kernel. It should work the other way around though.. The old userland stuff theoretically should work with the new kernel code (at least, I believe Bruce Evans was doing that at one stage, although he may have had to recompile the pppd with the new header files first). >Nate -Peter From owner-freebsd-current Thu Nov 2 09:45:44 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA08556 for current-outgoing; Thu, 2 Nov 1995 09:45:44 -0800 Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA08323 for ; Thu, 2 Nov 1995 09:41:08 -0800 Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id TAA00119; Thu, 2 Nov 1995 19:29:40 +0200 From: John Hay Message-Id: <199511021729.TAA00119@zibbi.mikom.csir.co.za> Subject: Re: Time problems To: bde@zeta.org.au (Bruce Evans) Date: Thu, 2 Nov 1995 19:29:39 +0200 (SAT) Cc: current@FreeBSD.org, wollman@lcs.mit.edu In-Reply-To: <199511011730.EAA07621@godzilla.zeta.org.au> from "Bruce Evans" at Nov 2, 95 04:30:41 am X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1416 Sender: owner-current@FreeBSD.org Precedence: bulk > > >OK, I did that and the 10 second delay takes about 8.5 seconds and the 100 > >second delay takes about 88 seconds. Here is the first part of dmesg: > > Urk. > > >Now how do I go further to find out where my problem is? > > Perhaps the 8254 clock is being accessed too fast. Try adding some delays > before each inb() and outb() in clock.c:getit(). Count to 100 or so to > get at least 1 usec delay. I added "for(x=0;x<100;x++);" between the inb and outb instructions and now the 100 second delay takes 98-99 seconds. So this is now much closer. It is also being probed as a 90MHz processor now. So it looks like this helps. > > If pentium_mhz is set to 0, then microtime() uses essentially the same > method as DELAY(). It accesses the clock registers as fast as possible. > Errors as large as 15 in 100 might be noticeable if you run the following > program. You will have to adjust the constants 25 and 50 (perhaps to 0 > and 100) to filter out the uninteresting stuff. Differences of < 0 or > much less than the average value mean that there is a problem. The > program should calculate the average value to decide a good range to > filter... I ran your program with the pentium timer disabled and regularly got negative numbers. The numbers vary, but things that I got was -6, -38, -44, -17, etc... Does this bring me closer to a permanent solution? John -- John Hay -- John.Hay@csir.co.za From owner-freebsd-current Thu Nov 2 11:32:34 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA12665 for current-outgoing; Thu, 2 Nov 1995 11:32:34 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA12660 for ; Thu, 2 Nov 1995 11:32:31 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA00243; Fri, 3 Nov 1995 06:30:02 +1100 Date: Fri, 3 Nov 1995 06:30:02 +1100 From: Bruce Evans Message-Id: <199511021930.GAA00243@godzilla.zeta.org.au> To: bmk@dtr.com, jfieber@indiana.edu Subject: Re: make world failed with -current Cc: current@FreeBSD.org, rgrimes@gndrsh.aac.dev.com, roberto@keltia.freenix.fr, vince@apollo.COSC.GOV Sender: owner-current@FreeBSD.org Precedence: bulk >I've encountered several other problems building -current on a 2.0.5 >system. I've found workarounds for all of them except one. >gnu/usr.bin/groff/pic won't build, it complains of an unterminated >character constant. (This is using sources obtained via CTM on Oct. >31). >|cc -O -I. -I/usr/src/gnu/usr.bin/groff/pic/../include -DHAVE_UNISTD_H=1 >|-DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_SYS_DIR_H=1 >|-DHAVE_CC_LIMITS_H=1 -DHAVE_CC_UNISTD_H=1 -DSTDLIB_H_DECLARES_GETOPT=1 >|-DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 >|-DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DRETSIGTYPE=void >|-DHAVE_MMAP=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_SYS_SIGLIST=1 -c >|pic.c >|pic.y:1630: unterminated character constant >|*** Error code 1 pic.c shouldn't exist. groff/Makefile.cfg contains a .y.cc rule that is supposed to produce pic.cc. It has always worked here. Bruce From owner-freebsd-current Thu Nov 2 12:09:11 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA13758 for current-outgoing; Thu, 2 Nov 1995 12:09:11 -0800 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA13753 for ; Thu, 2 Nov 1995 12:09:09 -0800 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.12/8.6.9) with SMTP id MAA12302; Thu, 2 Nov 1995 12:05:48 -0800 To: John Fieber cc: "Rodney W. Grimes" , Ollivier Robert , vince@apollo.COSC.GOV, current@FreeBSD.org Subject: Re: make world failed with -current In-reply-to: Your message of "Thu, 02 Nov 1995 10:44:01 EST." Date: Thu, 02 Nov 1995 12:05:48 -0800 Message-ID: <12300.815342748@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org Precedence: bulk > I've asked a couple times about doing this. The first time received some > grumbles, the second time recieved no replies. Since a source upgrade C'mon John, you know the "rule": No replies == Just Do It. :-) Jordan From owner-freebsd-current Thu Nov 2 12:41:52 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA15042 for current-outgoing; Thu, 2 Nov 1995 12:41:52 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA15030 for ; Thu, 2 Nov 1995 12:41:48 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA02262; Fri, 3 Nov 1995 07:41:19 +1100 Date: Fri, 3 Nov 1995 07:41:19 +1100 From: Bruce Evans Message-Id: <199511022041.HAA02262@godzilla.zeta.org.au> To: current@FreeBSD.ORG, uhclem%nemesis@fw.ast.com Subject: Re: Time problems Sender: owner-current@FreeBSD.ORG Precedence: bulk >[3]Perhaps the 8254 clock is being accessed too fast. Try adding some delays >[3]before each inb() and outb() in clock.c:getit(). Count to 100 or so to >[3]get at least 1 usec delay. >Uh, I don't think this will work as you expect on a Pentium or a P6. It is >too easy for the parallel integer unit(s) to execute the inb/outbs in one >unit and do the nice delay loop in the other, thus wrecking your timing delay. >On the Pentium and up you must force these types of "timed" instruction >sequences to be done sequentially. It worked :-). Perhaps the compiler allocated the same register for the loop counter as for the inb. But even if the same register is, used, there's nothing to stop the following optimization: movl $1000,%eax 1: decl %eax jne 1b inb $0x43,%al to: unit 1 unit 2 ------ ------ movl $1000000,%eax inb $0x43,%hiddenreg 1: decl %eax /* stall */ jne 1b /* stall */ movl %hiddenreg,%al except that a lot of code might break. >I am chasing a bug in the printer driver (-STROBE pulse timing is out of spec) >as we write that is probably caused by someone assuming that *all* the >instructions would execute in the order they were coded. Not anymore. I/O instructions must be executed sequentially. Someone assumed that back to back i/o instructions take longer than than 0.5 usec. They do take much longer than that for 8MHz ISA buses, and code to check whether a further delay is necessary would make ISA systems even slower. >In *general* you are guaranteed that IN and OUT instructions will generate >-IOR and -IOW cycles in the order they were coded, but any code that has no >dependencies/effects on the IN/OUT opcodes can be executed out of order in >relation to the IN/OUT opcodes. So if the purpose of that code is to I think ordering is guaranteed for i/o to uncached memory too. >If the inbs and outbs were actually calls to inbs and outbs rather >than being inline, the serialization problems tend to go away. At least >on the Pentium. This may not be the case on the P6 and other processors >with multiple execution units. Perhaps both jmp and call synchronize everything? Then the loop would work. I'm also depending on the gcc feature of not optimizing away delay loops. Bruce From owner-freebsd-current Thu Nov 2 12:47:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA15245 for current-outgoing; Thu, 2 Nov 1995 12:47:18 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA15237 for ; Thu, 2 Nov 1995 12:47:16 -0800 Received: from apollo.COSC.GOV (root@apollo.COSC.GOV [198.94.103.34]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id MAA20133 for ; Thu, 2 Nov 1995 12:46:56 -0800 Received: (from vince@localhost) by apollo.COSC.GOV (8.6.12/8.6.9) id MAA22365; Thu, 2 Nov 1995 12:36:49 -0800 Date: Thu, 2 Nov 1995 12:36:48 -0800 (PST) From: -Vince- To: "Garrett A. Wollman" cc: current@FreeBSD.ORG Subject: Re: schg flag on make world in -CURRENT In-Reply-To: <9511021700.AA03187@halloran-eldar.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG Precedence: bulk On Thu, 2 Nov 1995, Garrett A. Wollman wrote: > < said: > > > Does anyone know why the make world in the 11/1/95 -CURRENT keeps > > making many binaries with the schg flag and then when I do a make world, > > it will not overwrite the files since it can't delete the file? Thanks! > > Because your kernel is in secure mode. You can't do a `make world' in > secure mode. See init(8) and the definition of `securelevel' in > kern/kern_sysctl.c. Hmmm, Terry told me that this was defined in /etc/rc but I looked and it wasn't defined but if it was in kern/kern_sysctl.c, wouldn't a new sup just overwrite the file again? Is there a simple way to get out of secure mode before doing a make world? Cheers, -Vince- vince@COSC.GOV - GUS Mailing Lists Admin UC Berkeley AstroPhysics - Electrical Engineering (Honorary B.S.) Chabot Observatory & Science Center - Board of Advisors Running FreeBSD - Real UN*X for Free! Linda Wong/Vivian Chow/Hacken Lee/Danny Chan Fan Club Mailiing Lists Admin From owner-freebsd-current Thu Nov 2 14:35:21 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA19856 for current-outgoing; Thu, 2 Nov 1995 14:35:21 -0800 Received: from ibp.ibp.fr (ibp.ibp.fr [132.227.60.30]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id OAA19849 for ; Thu, 2 Nov 1995 14:35:16 -0800 Received: from blaise.ibp.fr (blaise.ibp.fr [132.227.60.1]) by ibp.ibp.fr (8.6.12/jtpda-5.0) with ESMTP id XAA06534 ; Thu, 2 Nov 1995 23:35:07 +0100 Received: from (uucp@localhost) by blaise.ibp.fr (8.6.12/jtpda-5.0) with UUCP id XAA00581 ; Thu, 2 Nov 1995 23:35:06 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.7.1/keltia-uucp-2.6) id UAA21504; Thu, 2 Nov 1995 20:00:54 +0100 (MET) From: Ollivier Robert Message-Id: <199511021900.UAA21504@keltia.freenix.fr> Subject: Re: make world failed with -current To: jfieber@indiana.edu (John Fieber) Date: Thu, 2 Nov 1995 20:00:53 +0100 (MET) Cc: rgrimes@GndRsh.aac.dev.com, vince@apollo.COSC.GOV, current@FreeBSD.org In-Reply-To: from "John Fieber" at Nov 2, 95 10:44:01 am X-Operating-System: FreeBSD 2.2-CURRENT ctm#1275 X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org Precedence: bulk It seems that John Fieber said: > barring any complaints I will put this in to both current *and* stable. > Once the sgml tools stablize, they can probably be safely removed from > the target. Please do it. The inter-atlantic lines are too busy else I'd have done it myself... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.frmug.fr.net FreeBSD keltia.freenix.fr 2.2-CURRENT #5: Mon Oct 30 00:03:29 MET 1995 From owner-freebsd-current Thu Nov 2 16:03:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id QAA22493 for current-outgoing; Thu, 2 Nov 1995 16:03:48 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA22488 for ; Thu, 2 Nov 1995 16:03:43 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id BAA29048 for ; Fri, 3 Nov 1995 01:03:34 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id BAA15615 for freebsd-current@FreeBSD.org; Fri, 3 Nov 1995 01:03:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id BAA00212 for freebsd-current@FreeBSD.org; Fri, 3 Nov 1995 01:00:45 +0100 From: J Wunsch Message-Id: <199511030000.BAA00212@uriah.heep.sax.de> Subject: ps(1): proc size mismatch To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Fri, 3 Nov 1995 01:00:44 +0100 (MET) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 422 Sender: owner-current@FreeBSD.org Precedence: bulk After rebuilding -current (both, the kernel and the whole world), i'm constantly getting "proc size mismatch" from ps(1) and w(1). Can somebody gimme a hint what exactly has been changed, and what i need to build again (instead of the "make world" overkill)? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Thu Nov 2 17:06:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA00330 for current-outgoing; Thu, 2 Nov 1995 17:06:16 -0800 Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA00308 for ; Thu, 2 Nov 1995 17:06:12 -0800 From: bmk@dtr.com Received: from dtr.com (dtr.rain.com [204.119.8.19]) by who.cdrom.com (8.6.12/8.6.11) with ESMTP id QAA22181 for ; Thu, 2 Nov 1995 16:31:50 -0800 Received: (from bmk@localhost) by dtr.com (8.6.11/8.6.9) id QAA05775; Thu, 2 Nov 1995 16:25:53 -0800 Message-Id: <199511030025.QAA05775@dtr.com> Subject: Re: make world failed with -current To: bde@zeta.org.au (Bruce Evans) Date: Thu, 2 Nov 1995 16:25:53 -0800 (PST) Cc: current@freebsd.org In-Reply-To: <199511021930.GAA00243@godzilla.zeta.org.au> from "Bruce Evans" at Nov 3, 95 06:30:02 am Reply-To: bmk@dtr.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1601 Sender: owner-current@freebsd.org Precedence: bulk > >I've encountered several other problems building -current on a 2.0.5 > >system. I've found workarounds for all of them except one. > >gnu/usr.bin/groff/pic won't build, it complains of an unterminated > >character constant. (This is using sources obtained via CTM on Oct. > >31). > >|cc -O -I. -I/usr/src/gnu/usr.bin/groff/pic/../include -DHAVE_UNISTD_H=1 > >|-DHAVE_DIRENT_H=1 -DHAVE_LIMITS_H=1 -DHAVE_STDLIB_H=1 -DHAVE_SYS_DIR_H=1 > >|-DHAVE_CC_LIMITS_H=1 -DHAVE_CC_UNISTD_H=1 -DSTDLIB_H_DECLARES_GETOPT=1 > >|-DUNISTD_H_DECLARES_GETOPT=1 -DSTDLIB_H_DECLARES_PUTENV=1 > >|-DSTDIO_H_DECLARES_POPEN=1 -DSTDIO_H_DECLARE_PCLOSE=1 -DRETSIGTYPE=void > >|-DHAVE_MMAP=1 -DHAVE_RENAME=1 -DHAVE_MKSTEMP=1 -DHAVE_SYS_SIGLIST=1 -c > >|pic.c > >|pic.y:1630: unterminated character constant > >|*** Error code 1 > pic.c shouldn't exist. groff/Makefile.cfg contains a .y.cc rule that > is supposed to produce pic.cc. It has always worked here. Here's the wierdest part: I grabbed the groff/pic sources from ftp.freebsd.org:/pub/FreeBSD/FreeBSD-current/you-know-the-rest. Just for kicks, I diffed them against my tree. No differences. Did a 'make all' on the fresh sources, and they compiled fine. Something must have got dorked up during an intermediary step which confused make. Dunno. I guess the moral of the story is "When in doubt, do a ``make clean'' first." :) Now that I've an almost-i100%-working -current system, I'm going to make clean the whole tree and see if the build can go 100% smoothly. I have a suspicion that it'll go a lot smoother than the build on top of 2.0.5. :) From owner-freebsd-current Thu Nov 2 17:58:59 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id RAA01619 for current-outgoing; Thu, 2 Nov 1995 17:58:59 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id RAA01613 ; Thu, 2 Nov 1995 17:58:47 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA03367; Thu, 2 Nov 1995 18:57:30 -0700 From: Terry Lambert Message-Id: <199511030157.SAA03367@phaeton.artisoft.com> Subject: RFD: VFS, non-Intel architectures To: arch@freebsd.org Date: Thu, 2 Nov 1995 18:57:29 -0700 (MST) Cc: terry@phaeton.artisoft.com (Terry Lambert), hackers@freebsd.org, current@freebsd.org X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 8679 Sender: owner-current@freebsd.org Precedence: bulk REQUEST FOR DISCUSSION As some of you know, I am doing a port of FreeBSD to the Motorolla Ultra 603/604. ---------------------------------------------------------------------- Rationale: Part of a port to a different platform has always been support of the native file system for that platform. The native OS for the machine I am using for the port is AIX. In order to support the local file system, two things must be done: 1) A JFS kernel file system based on VFS must be written 2) Boot code that can load the kernel from a JFS partition must be written. It would aid me greatly in writing the JFS file system if the VFS interface matched its documentation. This is a primary concern for all VFS based file system authors. It would aid me greatly if it were possible to share code between the boot and the kernel file systems. This is a secondary concern, since I can safely use the PReP psecification for pre-Open Firmware boot code and use the IBM boot code. It is not practical to use the IBM code for a distribution, however, since IBM owns it and it requires an AIX license. A distribution version of the port will likely not use JFS as its native file system, also lessoning the secondary concern. To resolve my primary concern, I would like to modify the VFS interface code in the kernel (all code that makes VFS calls) to conform to the design criteria for the 4.4BSD-Lite stackable file system interface. Note that this concern is an issue for anyone attempting to use the 4.4BSD-Lite stackable file system interface for platform ports, and for people attempting to use the code in non-4.4BSD-Lite derived systems. Like Linux and Windows95. This interface is documented in John Heidemann's Master's thesis, which can be obtained by interested persons from ftp.cs.ucla.edu. The FICUS file system documentation available from the same site is also applicable. It is clear that Chris Torek's importation of the Heidemann code for the 4.4BSD-Lite release was a quick hack job. Both Garrett Wollman, and later myself, have made patches to Chris Torek's code to cause it to be more in line with John Heidemann's intent. Proposal: ---------------------------------------------------------------------- Here are the layering/framework issues I would like to address initially: 1) The vfs_opv_numops global is a count of the total number of per interface vop descriptors in the vfs_op_descs[] array in the machine generated file vnode_if.c. The effect of having the count occur in the vfs_init.c code instead of as a static initialization is to make the framework depend on having at least one static entry. --- I would like to replace the count mechanism with a static initialization mechanism based on the machine generation mechanism. Specifically, I'd like vnode_if.sh to add the following line: int vfs_opv_numops = sizeof(vfs_op_descs)/sizeof(struct vnodeop_desc *) - 1; to the end of vnode_if.c, and an extern reference to vnode_if.h, Function will be identical before and after the patches. The intent of this change is to allow the operating system to act correctly when going for 0->1 static file system definitions. This is both of obvious utility to cross platform porters in not having to get a file system operational as a minimal porting requirement (allowing the port to be staged), and brings the file system closer into line with the Heidemann document. This change currently exists as part of my "fs layering patches" in ~terry on freefall.cdrom.com. 2) The interface between the VFS framework and the file system instances incorrectly makes assumptions that the design document does not allow it to make. a) The underlying file system is assumed to free the path name buffer created by the file name lookup mechanism in vfs_lookup.c, This assumption constitutes common, undocumented state which must be reimplemented in each underlying file system. There are currently several coding errors in the underlying file systems that will cause failures in rare circumstances. These are a direct result of incorrect reimplementation of the assumed state manipulations regarding the path name buffer. --- I would like to remove the assumption of a BSD dependent lookup mechanism. I would accomplish this by moving the cn_pnbuf free into an inverse routine called "nameifree" in vfs_lookup.c. Function will be identical before and after the patches. This would simultaneously simplify the task of writing a new file system (by removing the state assumptions), clean up the state errors in the failure mode cases, and lessen the dependency on a BSD based path component name lookup mechanism, making the code more portable to non-BSD environments using dissimilar lookup mechanisms (like Linux). Note: this would require concommitant changes to the locations where namei() is called and asked to preserve the path so that such implied state could be easily backed out. The major offender in this case is vfs_syscalls.c, Note: this would require changes to the nfs_subs.s and dependent modules, since nfs implements its own lookup mechanism (called nfs_namei), and so will need a parallel backoff mechanism (nfs_nameifree). All of these changes exist as part of my "fs layering patches" in ~terry on freefall.cdrom.com. b) The underlying file system makes calls back to the VFS implementation layer to implement advisory file locking. This is in violation of the file system, layering documentation. It also poses problems for the support of NFS locking, and constitutes an undue complication for a file system author (or OS porter acting as a native file system author). --- I would like to move the file system advisory locking to make use of a two stage lock commit process. The logical explanation of this process is as follows: i) A lock assertion is done locally at the VFS and system call interface layer. ii) A lock assertion is made to the underlying file system(s). iii)(1) If the lock is not "vetoed" by the underlying file system, the assertion is allowed. iii)(2) If the lock is vetoed by the underlying file system, the local lock assertion is reverted locally and the assertion is disallowed. For lock deassertion, the order of local/underlying is reversed. Function will be identical before and after the patches. This has the net effect of simplfying the advisory locking code in the per file system implementation, since most file systems will be using the local locking pardigm. It also moves the POSIX semantics into the OS, where they belong. The resulting advisory lock structures are to be hung from the vnode instead of the per file system inode, further generalizing their applicability. Finally, it simplifies the case of a stacked or union file system mount, since underlying cases result in one or more calls, the failure of which causes a veto to be returned to the local call layer. These change are "code in developement". c) The underlying file system makes assumptions about the in core inode structure. File locks are made on a per file system basis. This makes them subject to the same issues as advisory locking with regard to portability, code reuse, and file system authoring as advisory locks. --- I would like to move the file system file locking to make use of a similar multistage commit process as that described for the advisory locking. The reasoning is identical. The resulting file lock structures are to be hung from the vnode instead of the per file system inode, further generalizing their applicability. Function will be identical before and after the patches. These change are "code in developement". d) The underlying file system is expected to imply retention of the path name buffer when doing a lookup for a rename/mkdir/create operation. This is an assumption of state. --- I would like to move the assumption of state out of the per file system implementation case to simplify the implementation of additional file systems during OS porting, or otherwise. This will have the same effect with regard to bringing the file system framwork into compliance with the Heidemann documentation. Function will be identical before and after the patches. These change are "code in developement". I would like to invite discussion on these proposed VFS changes. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Nov 2 18:26:44 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA03393 for current-outgoing; Thu, 2 Nov 1995 18:26:44 -0800 Received: from bsdi.BSDI.COM (bsdi.BSDI.COM [205.230.224.1]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA03348 ; Thu, 2 Nov 1995 18:26:19 -0800 Received: (from torek@localhost) by bsdi.BSDI.COM (8.6.12/8.6.12) id TAA18845; Thu, 2 Nov 1995 19:26:16 -0700 Date: Thu, 2 Nov 1995 19:26:16 -0700 From: Chris Torek Message-Id: <199511030226.TAA18845@bsdi.BSDI.COM> To: arch@freebsd.org, terry@lambert.org Subject: Re: RFD: VFS, non-Intel architectures Cc: current@freebsd.org, hackers@freebsd.org Sender: owner-current@freebsd.org Precedence: bulk I am not going to comment on most of this, but I have to say one thing: >It is clear that Chris Torek's importation of the Heidemann code for >the 4.4BSD-Lite release was a quick hack job. I had nothing at all to do with the stackable vnodes in 4.4-Lite. (In fact, I argued for a completely different implementation of parts of it.) Chris From owner-freebsd-current Thu Nov 2 18:54:16 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA05387 for current-outgoing; Thu, 2 Nov 1995 18:54:16 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA05354 ; Thu, 2 Nov 1995 18:54:03 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA03572; Thu, 2 Nov 1995 19:52:10 -0700 From: Terry Lambert Message-Id: <199511030252.TAA03572@phaeton.artisoft.com> Subject: Re: RFD: VFS, non-Intel architectures To: torek@BSDI.COM (Chris Torek) Date: Thu, 2 Nov 1995 19:52:10 -0700 (MST) Cc: arch@FreeBSD.org, terry@lambert.org, current@FreeBSD.org, hackers@FreeBSD.org In-Reply-To: <199511030226.TAA18845@bsdi.BSDI.COM> from "Chris Torek" at Nov 2, 95 07:26:16 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 930 Sender: owner-current@FreeBSD.org Precedence: bulk > I am not going to comment on most of this, but I have to say one > thing: > > >It is clear that Chris Torek's importation of the Heidemann code for > >the 4.4BSD-Lite release was a quick hack job. > > I had nothing at all to do with the stackable vnodes in 4.4-Lite. > (In fact, I argued for a completely different implementation of > parts of it.) Sorry; Kirk McKusick told me that as well. I was put off on the wrong track by some tags. Kirk says that the port was done by John and himself. In any case, it still shows the marks of being a quick hack, which is what I wanted to address. Sorry for any inconvenience. Actually, I'd really like to hear your comments on the rest of the RFD, especially now that I know that you are at odds with the current implementation as well. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Nov 3 02:49:03 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id CAA04661 for current-outgoing; Fri, 3 Nov 1995 02:49:03 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id CAA04654 for ; Fri, 3 Nov 1995 02:48:52 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA00204; Fri, 3 Nov 1995 21:42:52 +1100 Date: Fri, 3 Nov 1995 21:42:52 +1100 From: Bruce Evans Message-Id: <199511031042.VAA00204@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@lcs.mit.edu Subject: Re: Time problems Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk >Here is a program that I have used to measure a whole bunch of things >about the clock... I get the following output for `rtprio 0 ./thisprog' on a lightly loaded DX2/66 VLB (ISA clock :-() system running -current: min 13, max 171, mean 14.286634, std 1.836667 1th: 14 (1053245 observations) 2th: 15 (587593 observations) 3th: 13 (299847 observations) 4th: 16 (51817 observations) 5th: 33 (934 observations) This is the expected behaviour. After reducing N from 2000000 to 100000, I get the following output for `./thisprog' on a heavily loaded DX2/66 VLB (ISA clock :-() system running Linux 1.2.13: Segmentation fault >#define N 2000000 >int diffs[N]; >int hist[N]; hist[] has indices min..max, not 0..N-1. max was abour 230000 under Linux, so an index was out of bounds because I reduced N. min might be < 0 if gettimeofday() is broken. Bruce From owner-freebsd-current Fri Nov 3 03:49:22 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA07263 for current-outgoing; Fri, 3 Nov 1995 03:49:22 -0800 Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id DAA07255 ; Fri, 3 Nov 1995 03:49:20 -0800 Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0tBKcX-0003wUC; Fri, 3 Nov 95 03:49 PST Received: from localhost (localhost [127.0.0.1]) by critter.tfs.com (8.6.11/8.6.9) with SMTP id MAA02383; Fri, 3 Nov 1995 12:49:15 +0100 X-Authentication-Warning: critter.tfs.com: Host localhost didn't use HELO protocol To: "Rodney W. Grimes" cc: bde@zeta.org.au (Bruce Evans), gibbs@freefall.freebsd.org, wollman@lcs.mit.edu, current@FreeBSD.org, wollman@FreeBSD.org Subject: Re: Time problems In-reply-to: Your message of "Wed, 01 Nov 1995 01:08:04 PST." <199511010908.BAA09757@GndRsh.aac.dev.com> Date: Fri, 03 Nov 1995 12:49:14 +0100 Message-ID: <2381.815399354@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org Precedence: bulk > CPU: Intel Pentium Processor clocked at 99.85 Mhz (Pentium class CPU) Good idea. Will put it on my list. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so. From owner-freebsd-current Fri Nov 3 08:42:22 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA17251 for current-outgoing; Fri, 3 Nov 1995 08:42:22 -0800 Received: from devnull.mpd.tandem.com (devnull.mpd.tandem.com [131.124.4.29]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id IAA17242 for ; Fri, 3 Nov 1995 08:42:16 -0800 Received: from olympus by devnull.mpd.tandem.com (8.6.8/8.6.6) id KAA25483; Fri, 3 Nov 1995 10:41:59 -0600 Received: by olympus (4.1/TSS2.1) id AA13947; Fri, 3 Nov 95 10:42:08 CST From: faulkner@mpd.tandem.com (Boyd Faulkner) Message-Id: <9511031642.AA13947@olympus> Subject: Re: pppd won't hold connection To: peter@haywire.dialix.com (Peter Wemm) Date: Fri, 3 Nov 1995 10:42:08 -0600 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <47avig$2qg$1@haywire.DIALix.COM> from "Peter Wemm" at Nov 3, 95 01:36:16 am X-Mailer: ELM [version 2.4 PL17] Content-Type: text Content-Length: 1211 Sender: owner-current@freebsd.org Precedence: bulk > > nate@rocky.sri.MT.net (Nate Williams) writes: > > >Re-build the kernel and see if it makes any difference. Peter made lots > >of changes made to both the userland stuff and the kernel. > > It should work the other way around though.. The old userland stuff > theoretically should work with the new kernel code (at least, I > believe Bruce Evans was doing that at one stage, although he may have > had to recompile the pppd with the new header files first). > > >Nate > > -Peter > OK. It works for me now. How do I get defaultroute to work? static int setdefaultroute() { if (!ipcp_allowoptions[0].default_route) { fprintf(stderr, "%s: defaultroute option is disabled\n", progname); return 0; } ipcp_wantoptions[0].default_route = 1; return 1; } in options.c How do I turn ipcp_allowoptions[0].default_route on without rewriting the code? (I did and it works.) The default route option used to be enabled by default. Thanks, Boyd -- _______________________________________________________________________ Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner _______________________________________________________________________ From owner-freebsd-current Fri Nov 3 08:49:41 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id IAA17622 for current-outgoing; Fri, 3 Nov 1995 08:49:41 -0800 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id IAA17609 for ; Fri, 3 Nov 1995 08:49:37 -0800 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.8.2/19Aug95-0530PM) id AA05415; Fri, 3 Nov 1995 11:49:13 -0500 Date: Fri, 3 Nov 1995 11:49:13 -0500 From: "Garrett A. Wollman" Message-Id: <9511031649.AA05415@halloran-eldar.lcs.mit.edu> To: Bruce Evans Cc: current@FreeBSD.org Subject: Re: Time problems In-Reply-To: <199511031523.CAA11301@godzilla.zeta.org.au> References: <199511031523.CAA11301@godzilla.zeta.org.au> Sender: owner-current@FreeBSD.org Precedence: bulk < said: > You may have to wait for kernel changes (or write them :-) to use the > Pentium clock unless it is very close to an integral number of MHz. > Another problem with using it is that it breaks tickadj(8). > cpu_thisticklen() ignores the default value of `tick', so tickadj > can't be used to compensate for large errors in `pentium_mhz'. I do not see that this is the case. From kern/kern_clock.c: if (timedelta == 0) { time_update = CPU_THISTICKLEN(tick); } else { time_update = CPU_THISTICKLEN(tick) + tickdelta; timedelta -= tickdelta; } Certainly looks like the correct thing to me. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Fri Nov 3 09:37:46 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA19593 for current-outgoing; Fri, 3 Nov 1995 09:37:46 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA19583 for ; Fri, 3 Nov 1995 09:37:34 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id EAA15564; Sat, 4 Nov 1995 04:35:12 +1100 Date: Sat, 4 Nov 1995 04:35:12 +1100 From: Bruce Evans Message-Id: <199511031735.EAA15564@godzilla.zeta.org.au> To: bde@zeta.org.au, wollman@lcs.mit.edu Subject: Re: Time problems Cc: current@FreeBSD.org Sender: owner-current@FreeBSD.org Precedence: bulk >> You may have to wait for kernel changes (or write them :-) to use the >> Pentium clock unless it is very close to an integral number of MHz. >> Another problem with using it is that it breaks tickadj(8). >> cpu_thisticklen() ignores the default value of `tick', so tickadj >> can't be used to compensate for large errors in `pentium_mhz'. >I do not see that this is the case. From kern/kern_clock.c: > if (timedelta == 0) { > time_update = CPU_THISTICKLEN(tick); > } else { > time_update = CPU_THISTICKLEN(tick) + tickdelta; > timedelta -= tickdelta; > } Asumme for simplicity that timedelta is fixed at 0. Then `tickadj -t 9999' changes time_update in the above from 10000 to 9999 on non-Pentium systems but has no effect on Pentium systems. tickadj would have to hack on (a higher precision version of) pentium_mhz to achieve the same effect on Pentium systems. This is similar to the problem with jitter in the non-Pentium microtime() that I mentioned previously. Both tickadj and adjtimeofday() adjust secondary variables but have no effect on the primary clock frequency. The scaling factor of (1e6 / primary_clock_freqency) needs to be scaled by a factor of (tick + tickdelta) / (100000 / hz). Bruce From owner-freebsd-current Fri Nov 3 10:14:01 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA21095 for current-outgoing; Fri, 3 Nov 1995 10:14:01 -0800 Received: from haven.uniserve.com (haven.uniserve.com [198.53.215.121]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA21081 for ; Fri, 3 Nov 1995 10:13:55 -0800 Received: by haven.uniserve.com id <30743-4>; Fri, 3 Nov 1995 10:15:41 -0000 Date: Fri, 3 Nov 1995 10:15:36 -0800 (PST) From: Tom Samplonius To: current@freebsd.org Subject: Crash on -stable system Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk I just had a -stable system sup'ped and built Oct 26 panic with the following message: kernel page directory invalid pdir=0x1f8b023, va=0xefbfe000 panic: invalid kernel page directory Is this a known problem? Hardware is a ASUS pentium mb, Adaptec 2940, Compex Enet PCI ethernet, 32 megs of RAM. Tom From owner-freebsd-current Fri Nov 3 11:09:25 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA24019 for current-outgoing; Fri, 3 Nov 1995 11:09:25 -0800 Received: from haywire.DIALix.COM (peter@haywire.DIALix.COM [192.203.228.65]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA24009 for ; Fri, 3 Nov 1995 11:09:15 -0800 Received: (from peter@localhost) by haywire.DIALix.COM (sendmail) id DAA23428; Sat, 4 Nov 1995 03:08:53 +0800 (WST) Date: Sat, 4 Nov 1995 03:08:50 +0800 (WST) From: Peter Wemm Reply-To: peter@jhome.dialix.com To: Boyd Faulkner cc: freebsd-current@freebsd.org Subject: Re: pppd won't hold connection In-Reply-To: <9511031642.AA13947@olympus> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk On Fri, 3 Nov 1995, Boyd Faulkner wrote: > > nate@rocky.sri.MT.net (Nate Williams) writes: > > > > >Re-build the kernel and see if it makes any difference. Peter made lots > > >of changes made to both the userland stuff and the kernel. > > > > It should work the other way around though.. The old userland stuff > > theoretically should work with the new kernel code (at least, I > > believe Bruce Evans was doing that at one stage, although he may have > > had to recompile the pppd with the new header files first). > > > > >Nate > > > > -Peter > > > > OK. It works for me now. How do I get defaultroute to work? > > static int > setdefaultroute() > { > if (!ipcp_allowoptions[0].default_route) { > fprintf(stderr, "%s: defaultroute option is disabled\n", progname); > return 0; > } > ipcp_wantoptions[0].default_route = 1; > return 1; > } > in options.c > > How do I turn ipcp_allowoptions[0].default_route on without rewriting the > code? (I did and it works.) The default route option used to be enabled > by default. That indeed is a very GOOD question... I have just committed a fix from ppp-2.3alpha0 (the one with dial-on-demand support). -Peter > Thanks, > Boyd > -- > _______________________________________________________________________ > > Boyd Faulkner - faulkner@isd.tandem.com - http://cactus.org/~faulkner > _______________________________________________________________________ > From owner-freebsd-current Fri Nov 3 20:22:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA02887 for current-outgoing; Fri, 3 Nov 1995 20:22:27 -0800 Received: from precipice.shockwave.com (precipice.shockwave.com [171.69.108.33]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA02881 for ; Fri, 3 Nov 1995 20:22:23 -0800 Received: (from root@localhost) by precipice.shockwave.com (8.6.12/8.6.12) id UAA06256 for current@freebsd.org; Fri, 3 Nov 1995 20:21:39 -0800 Date: Fri, 3 Nov 1995 20:21:39 -0800 From: Paul Traina Message-Id: <199511040421.UAA06256@precipice.shockwave.com> To: current@freebsd.org Subject: MFS? Sender: owner-current@freebsd.org Precedence: bulk What's the current state of MFS in -stable and -current? I haven't tried using it in over a year (since the 4.4-lite integration). Is it still hosed badly, or just hosed a little bit, or functional? From owner-freebsd-current Fri Nov 3 21:54:47 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA07635 for current-outgoing; Fri, 3 Nov 1995 21:54:47 -0800 Received: from macs.mxim.com (macs.mxim.com [204.17.143.130]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA07630 for ; Fri, 3 Nov 1995 21:54:44 -0800 Received: (from michaele@localhost) by macs.mxim.com (8.6.11/8.6.9) id VAA05366; Fri, 3 Nov 1995 21:49:17 -0800 Date: Fri, 3 Nov 1995 21:49:16 -0800 (PST) From: Michael Enkelis To: current@freebsd.org Subject: SCSI Tape devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org Precedence: bulk I just found what might be a bug in the scsi driver in -stable i sup'ed last night. I can only do ONE operation to my tape drive. After the operation completes, it ignores all other commands until a reboot. Normaly inserting another tape will cause the drive to find BOT marker, this does not even happen. My hardware (from dmesg): FreeBSD 2.1-STABLE #0: Fri Nov 3 21:21:09 PST 1995 root@:/usr/src/sys/compile/ENKY CPU: i486DX (486-class CPU) real memory = 33554432 (32768K bytes) avail memory = 30937088 (30212K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x2a0-0x2a7 flags 0x301 on isa sio0: type 16550A (multiport) sio1 at 0x2a8-0x2af flags 0x301 on isa sio1: type 16550A (multiport) sio2 at 0x2b0-0x2b7 flags 0x301 on isa sio2: type 16450 (multiport) sio3 at 0x2b8-0x2bf irq 4 flags 0x301 on isa sio3: type 16450 (multiport master) mse0 at 0x23c irq 3 on isa pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.2MB 5.25in fd1: 1.44MB 3.5in ahc1: 274x Twin Channel, A SCSI Id=7, B SCSI Id=7, aic7770 <= Rev C, 4 SCBs ahc1 at 0x5000-0x50ff irq 11 on eisa slot 5 (ahc1:0:0): "QUANTUM P40S 940-40-94xx A.2" type 0 fixed SCSI 1 sd0(ahc1:0:0): Direct-Access 40MB (82029 512 byte sectors) (ahc1:1:0): "QUANTUM PD1050iS 3100" type 0 fixed SCSI 2 sd1(ahc1:1:0): Direct-Access 1003MB (2055096 512 byte sectors) (ahc1:5:0): "TANDBERG TDC 3600 -04." type 1 removable SCSI 1 st0(ahc1:5:0): Sequential-Access st0: Tandberg tdc3600 is a known rogue density code 0x10, 512-byte blocks, write-enabled (ahc1:6:0): "TOSHIBA CD-ROM DRIVE:XM 3332" type 5 removable SCSI 1 cd0(ahc1:6:0): CD-ROM cd0(ahc1:6:0): NOT READY asc:4,0 cd0(ahc1:6:0): Logical unit not ready, cause not reportable can't get the size 1 3C5x9 board(s) on EISA found at 0x8000 ep0 at 0x8000-0x800f irq 10 on eisa slot 8 ep0: aui/bnc[*BNC*] address 00:20:af:2c:5e:4b irq 10 npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 7 drq 1 on isa sb0: opl0 at 0x388 on isa opl0: -------------------------- The tape drive and cdrom are on the internal SCSI bus. My disk drives are on the external SCSI bus. The cdrom works fine, and until last month i beleve that the tape also worked ok. When i install a tape drive (tandberg 3820) on the external bus, it is probed as st0 and the tape drive (tandberg 3660) on the internal SCSI bus probes as st1. Now st0 DOES work, but st1 still only allows one operation. _ _ _ __ michaele@mxim.com ' ) ) ) / /) / ` / /) Michael Enkelis / / / o _. /_ __. _ // /-- __ /_ _ // o _ (503) 641 - 3737 x2245 / ' (_(_(__/ /_(_(_(<_(/_ (___, /) )_/ <_(<_(/_(_/_)_ From owner-freebsd-current Fri Nov 3 22:04:48 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA07751 for current-outgoing; Fri, 3 Nov 1995 22:04:48 -0800 Received: from ast.com (irvine.ast.com [165.164.128.2]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id WAA07746 for ; Fri, 3 Nov 1995 22:04:46 -0800 Received: from fw.ast.com by ast.com with SMTP id AA12334 (5.67b/IDA-1.5 for ); Fri, 3 Nov 1995 22:05:59 -0800 Received: from nemesis by fw.ast.com with uucp (Smail3.1.29.1 #4) id m0tBbXe-00008AC; Fri, 3 Nov 95 23:53 CST Received: by nemesis.lonestar.org (Smail3.1.27.1 #19) id m0tBbW4-000J4YC; Fri, 3 Nov 95 23:51 WET Message-Id: Date: Fri, 3 Nov 95 23:51 WET To: current@FreeBSD.org From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Fri Nov 3 1995, 23:51:43 CST Subject: Re: Opcode sequencing Sender: owner-current@FreeBSD.org Precedence: bulk [3]Bruce Evans writes: [3]Perhaps the 8254 clock is being accessed too fast. Try adding some delays [3]before each inb() and outb() in clock.c:getit(). Count to 100 or so to [3]get at least 1 usec delay. [4]Uh, I don't think this will work as you expect on a Pentium or a P6. It is [4]too easy for the parallel integer unit(s) to execute the inb/outbs in one [4]unit and do the nice delay loop in the other, thus wrecking your timing [4]delay. On the Pentium and up you must force these types of "timed" [4]instruction sequences to be done sequentially. [4] [4]Execution Time is no longer linear.... :-) [5]Rod Grimes rgrimes@gndrsh.aac.dev.com writes: [5]I suggest you go read the book again, IN and OUT instructions are [5]``serailization'' instuctions. All code between them will have _completed_ [5]execution before the external cycle runs. Uh, I did. 18-8.5 of Volume 3 of the 1994 Pentium songbook says: "The I/O instructions are *not* completely serializing; the processor does *not* wait for these instructions to complete before it prefetches the next instruction. However, they do have some serializing properties that cause them to function in a manner that is compatible with processor generations prior to the Pentium processor." [Ed: even the 486 and to a lesser extend the 386 had a habit of having the I/O cycle from an OUT instruction occur AFTER the next instruction was well-underway. More on this below.] and Chapter 15.4 "Ordering of I/O" says: "To optimize performance, the Pentium CPU allows memory reads to be reordered ahead of buffered writes in most situations. Internally, the CPU reads (cache hits) can be reordered around buffered writes. Memory reordering does not occur externally at the pins, read (cache miss) and writes appear in-order. The Intel486 CPU allows memory reads to be reordered ahead of buffered writes in certain precisely-defined circumstances. (See the Intel486TM Microprocessor Hardware Reference Manual for further details about the operation of the write buffer.) Using memory-mapped I/O, therefore, creates the possibility that an I/O read might be performed before the memory write of a previous instruction. To eliminate this possibility on the Intel486CPU, use an I/O instruction for the read. ****To eliminate this possibility on the Pentium processor, insert one of the serializing instructions, such as CPUID, between operations.**** [Ed: the reverse is also true on a 486 according to the HP 486 Logic Analyzer. An OUT followed by a memory read obtained data from the wrong location because the OUT I/O cycle had not occurred by the time the memory read was performed. (The OUT cycle would have changed memory banks in an expanded memory system, so the wrong bank was accessed even though the OUT appeared in the code before the MOV.) The solution was to insert a JMP $+2 between OUT and MOV opcodes. I don't know if similar or fancier action is required on the Pentium and this particular case isn't clearly covered in the Pentium manual.] When I/O instructions are used instead of memory-mapped I/O, the situation is different in two respects: 1. Some I/O writes are never buffered. The only I/O writes that the the Intel486 CPU buffers are those from the OUTS instruction. The Pentium processor does not buffer any I/O writes. Therefore, strict ordering of I/O operations is enforced by the processor. [Ed: Symantics. A plain OUT on a 486 may not be "buffered", but the I/O WRITE cycle also does not occur during the actual execution clocks of the OUT instruction. It occurs during or after the next instruction is performed. So you might call that "deferred". I think they are using "buffered" to say the I/O cycle does not occur only forced out onto the bus for some reason, and I agree that is not how it works. The I/O cycle occurs at a reasonably predictable point. It just isn't in the confines of the OUT instruction execution period.] 2. The [Pentium] processor synchronizes I/O instruction execution with *external* bus activity. Refer to Table 15-1. Table 15-1 [Pentium] I/O Serialization Processor Holds Awaiting for Completion of... Execution of... Current Current Next Pending Current Instruction Instruction? Instruction Stores? Store? IN Yes - Yes - INS Yes - Yes - REP INS Yes - Yes - OUT - Yes Yes Yes OUTS - Yes Yes Yes REP OUTS - Yes Yes Yes " Sorry, I don't know what the difference is between "Current Instruction" and "Current Instruction?". Perhaps it means an instruction in the other execution unit (if any) is held while this I/O instruction is performed. So much for this bit of trivia. Frank Durda IV |You want something here or uhclem%nemesis@fw.ast.com (Fastest Route)|every time? ...letni!rwsys!nemesis!uhclem | ...decvax!fw.ast.com!nemesis!uhclem | From owner-freebsd-current Fri Nov 3 23:51:18 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA10927 for current-outgoing; Fri, 3 Nov 1995 23:51:18 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA10892 for ; Fri, 3 Nov 1995 23:51:13 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA16839; Sat, 4 Nov 1995 08:51:07 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA29780; Sat, 4 Nov 1995 08:51:07 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id IAA06368; Sat, 4 Nov 1995 08:27:26 +0100 From: J Wunsch Message-Id: <199511040727.IAA06368@uriah.heep.sax.de> Subject: Re: MFS? To: pst@Shockwave.COM (Paul Traina) Date: Sat, 4 Nov 1995 08:27:26 +0100 (MET) Cc: current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199511040421.UAA06256@precipice.shockwave.com> from "Paul Traina" at Nov 3, 95 08:21:39 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 471 Sender: owner-current@freebsd.org Precedence: bulk As Paul Traina wrote: > What's the current state of MFS in -stable and -current? I haven't > tried using it in over a year (since the 4.4-lite integration). Is > it still hosed badly, or just hosed a little bit, or functional? I think it works fine, but you have to compile it statically into the kernel. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Nov 4 01:30:27 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA22459 for current-outgoing; Sat, 4 Nov 1995 01:30:27 -0800 Received: from aslan.cdrom.com (aslan.cdrom.com [192.216.223.142]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA22452 for ; Sat, 4 Nov 1995 01:30:24 -0800 Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1]) by aslan.cdrom.com (8.6.12/8.6.9) with SMTP id DAA27008; Sat, 4 Nov 1995 03:37:45 -0800 Message-Id: <199511041137.DAA27008@aslan.cdrom.com> X-Authentication-Warning: aslan.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol To: Michael Enkelis cc: current@freebsd.org Subject: Re: SCSI Tape devices In-reply-to: Your message of "Fri, 03 Nov 1995 21:49:16 PST." Date: Sat, 04 Nov 1995 03:37:45 -0800 From: "Justin T. Gibbs" Sender: owner-current@freebsd.org Precedence: bulk >I just found what might be a bug in the scsi driver in -stable i sup'ed last >night. > >I can only do ONE operation to my tape drive. After the operation completes, >it ignores all other commands until a reboot. Normaly inserting another tape >will cause the drive to find BOT marker, this does not even happen. Does the drive do anything to make you think commands are being sent to it after it goes out to lunch and you try to use it again? Have you tried tracing commands to that target with SCSIDEBUG turned on? What are the return codes of operations you try to the device? Does your tape drive match any of the "rogue" entries in st.c and if so, does removing the entry help? > _ _ _ __ michaele@mxim.com >' ) ) ) / /) / ` / /) Michael Enkelis > / / / o _. /_ __. _ // /-- __ /_ _ // o _ (503) 641 - 3737 x2245 >/ ' (_(_(__/ /_(_(_(<_(/_ (___, /) )_/ <_(<_(/_(_/_)_ > -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sat Nov 4 01:53:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id BAA26273 for current-outgoing; Sat, 4 Nov 1995 01:53:02 -0800 Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA26240 for ; Sat, 4 Nov 1995 01:52:55 -0800 Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA18533; Sat, 4 Nov 1995 10:50:43 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA00191; Sat, 4 Nov 1995 10:50:43 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.6.12/8.6.9) id IAA06483; Sat, 4 Nov 1995 08:58:43 +0100 From: J Wunsch Message-Id: <199511040758.IAA06483@uriah.heep.sax.de> Subject: Re: SCSI Tape devices To: michaele@mxim.com (Michael Enkelis) Date: Sat, 4 Nov 1995 08:58:43 +0100 (MET) Cc: current@freebsd.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: from "Michael Enkelis" at Nov 3, 95 09:49:16 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 1333 Sender: owner-current@freebsd.org Precedence: bulk As Michael Enkelis wrote: > I can only do ONE operation to my tape drive. After the operation > completes, it ignores all other commands until a reboot. Normaly > inserting another tape will cause the drive to find BOT marker, this > does not even happen. > (ahc1:5:0): "TANDBERG TDC 3600 -04." type 1 removable SCSI 1 > st0(ahc1:5:0): Sequential-Access st0: Tandberg tdc3600 is a known rogue > density code 0x10, 512-byte blocks, write-enabled I don't have problems with a similar drive: (bt0:4:0): "TANDBERG TDC 3600 =08:" type 1 removable SCSI 2 st0(bt0:4:0): Sequential-Access density code 0x0, drive empty (The different appearence is due to having ``options NEW_SCSICONF'' defined.) > When i install a tape drive (tandberg 3820) on the external bus, it is > probed as st0 and the tape drive (tandberg 3660) on the internal SCSI bus > probes as st1. Your external drive has a lower SCSI ID, and is therefore probed first. You can wire your TDC 3600 to st0 if you want; refer to the LINT config file. What exactly are you doing with your drive? What is the response (including syslog output) for a following `mt status', `mt rewoffl', `mt eom' etc.? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current Sat Nov 4 11:56:02 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id LAA23344 for current-outgoing; Sat, 4 Nov 1995 11:56:02 -0800 Received: from metal.ops.neosoft.com (root@metal-pluto.ops.NeoSoft.COM [198.65.163.227]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA23338 for ; Sat, 4 Nov 1995 11:55:59 -0800 Received: (from smace@localhost) by metal.ops.neosoft.com (8.7.1/8.7.1) id NAA02081 for current@freebsd.org; Sat, 4 Nov 1995 13:55:58 -0600 (CST) From: Scott Mace Message-Id: <199511041955.NAA02081@metal.ops.neosoft.com> Subject: vnode_pager_outpages error To: current@freebsd.org Date: Sat, 4 Nov 1995 13:55:57 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk While under high paging I sometimes get the following errors: vnode_pager_putpages: attempt to write meta-data!!! -- 0xfffe8000(ff) vnode_pager_putpages: attempt to write meta-data!!! -- 0xfffe9000(ff) this kernel was built from -current CTM1298. Also, I randomly get signal-10's and singal-11's when compiling. This is with an ASUS P55TP4XE/100 , 256 Pipline Burst cache, AHA2940 scsi 16MB EDO ram Scott From owner-freebsd-current Sat Nov 4 18:58:15 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA01424 for current-outgoing; Sat, 4 Nov 1995 18:58:15 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id SAA01419 for ; Sat, 4 Nov 1995 18:58:13 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id SAA01299; Sat, 4 Nov 1995 18:58:06 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id SAA00775; Sat, 4 Nov 1995 18:55:57 -0800 Message-Id: <199511050255.SAA00775@corbin.Root.COM> To: Scott Mace cc: current@freebsd.org Subject: Re: vnode_pager_outpages error In-reply-to: Your message of "Sat, 04 Nov 95 13:55:57 CST." <199511041955.NAA02081@metal.ops.neosoft.com> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 04 Nov 1995 18:55:56 -0800 Sender: owner-current@freebsd.org Precedence: bulk >While under high paging I sometimes get the following errors: > >vnode_pager_putpages: attempt to write meta-data!!! -- 0xfffe8000(ff) >vnode_pager_putpages: attempt to write meta-data!!! -- 0xfffe9000(ff) > >this kernel was built from -current CTM1298. This is a known problem, and as far as we can tell, is benign. >Also, I randomly get signal-10's and singal-11's when compiling. That's a real problem. It's interesting to note that Jordan was having trouble a few days ago when he tried to upgrade his 90Mhz machine (same motherboard as you) to 100Mhz. When he replaced the CPU with a 133Mhz one, his problems went away. In his case, it was obviously a hardware problem, but since the external cache and memory were operating with the same timing (66Mhz), I can only conclude that the problem was the CPU itself. Strange... >This is with an ASUS P55TP4XE/100 , > 256 Pipline Burst cache, AHA2940 scsi 16MB EDO ram Hmmm...what kind of disk are you using on it? I'm definately interested in the results of any equipment swapping you can do. It's possible that there is some sort of bug in the VM system (we've been down THIS road plenty of times :-)), but I haven't seen any problems like that here...and I do countless make worlds. I have two P55TP4XE based machines here, both are 90Mhz w/PB cache. I know that Rod does extensive testing with these motherboards, too, and he does 100Mhz+ there. His tests are all with -stable, however. -DG From owner-freebsd-current Sat Nov 4 19:30:53 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id TAA01886 for current-outgoing; Sat, 4 Nov 1995 19:30:53 -0800 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id TAA01880 for ; Sat, 4 Nov 1995 19:30:31 -0800 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id OAA27221; Sun, 5 Nov 1995 14:02:15 +1030 From: Michael Smith Message-Id: <199511050332.OAA27221@genesis.atrad.adelaide.edu.au> Subject: Re: SCSI Tape devices To: joerg_wunsch@uriah.heep.sax.de Date: Sun, 5 Nov 1995 14:02:14 +1030 (CST) Cc: michaele@mxim.com, current@FreeBSD.ORG In-Reply-To: <199511040758.IAA06483@uriah.heep.sax.de> from "J Wunsch" at Nov 4, 95 08:58:43 am Content-Type: text Content-Length: 1154 Sender: owner-current@FreeBSD.ORG Precedence: bulk J Wunsch stands accused of saying: > > (ahc1:5:0): "TANDBERG TDC 3600 -04." type 1 removable SCSI 1 > > st0(ahc1:5:0): Sequential-Access st0: Tandberg tdc3600 is a known rogue > > density code 0x10, 512-byte blocks, write-enabled ... > (bt0:4:0): "TANDBERG TDC 3600 =08:" type 1 removable SCSI 2 > st0(bt0:4:0): Sequential-Access density code 0x0, drive empty > > (The different appearence is due to having ``options NEW_SCSICONF'' > defined.) The other difference is that the guilty TDC3660 has _ancient_ firmware. Get a new PROM for the drive; rev =08 is the current (As shown by Joerg's unit). Tandberg have tech support on the 'net, or your local tape unit supplier should be able to helop. Failing that, I can email you an image and you can cut it yourself. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Sat Nov 4 21:05:33 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA18541 for current-outgoing; Sat, 4 Nov 1995 21:05:33 -0800 Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA18533 for ; Sat, 4 Nov 1995 21:05:21 -0800 Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.9/8.6.9) id PAA27356 for current@freebsd.org; Sun, 5 Nov 1995 15:39:00 +1030 From: Michael Smith Message-Id: <199511050509.PAA27356@genesis.atrad.adelaide.edu.au> Subject: Re: SCSI Tape devices To: current@freebsd.org Date: Sun, 5 Nov 1995 15:38:59 +1030 (CST) In-Reply-To: <199511050332.OAA27221@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Nov 5, 95 02:02:14 pm Content-Type: text Content-Length: 855 Sender: owner-current@freebsd.org Precedence: bulk Michael Smith stands accused of saying: > The other difference is that the guilty TDC3660 has _ancient_ firmware. > Get a new PROM for the drive; rev =08 is the current (As shown by Joerg's > unit). Tandberg have tech support on the 'net, or your local tape unit > supplier should be able to helop. Failing that, I can email you an image > and you can cut it yourself. If my creaking brain can be trusted, Tandberg are tdata.no, and my contact there was wimo@tdata.no. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ From owner-freebsd-current Sat Nov 4 23:51:12 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id XAA22126 for current-outgoing; Sat, 4 Nov 1995 23:51:12 -0800 Received: from metal.ops.neosoft.com (root@metal-pluto.ops.NeoSoft.COM [198.65.163.227]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id XAA22113 for ; Sat, 4 Nov 1995 23:51:09 -0800 Received: (from smace@localhost) by metal.ops.neosoft.com (8.7.1/8.7.1) id BAA01600; Sun, 5 Nov 1995 01:50:58 -0600 (CST) From: Scott Mace Message-Id: <199511050750.BAA01600@metal.ops.neosoft.com> Subject: Re: vnode_pager_outpages error To: davidg@Root.COM Date: Sun, 5 Nov 1995 01:50:58 -0600 (CST) Cc: current@freebsd.org In-Reply-To: <199511050255.SAA00775@corbin.Root.COM> from "David Greenman" at Nov 4, 95 06:55:56 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@freebsd.org Precedence: bulk > >Also, I randomly get signal-10's and singal-11's when compiling. > > That's a real problem. It's interesting to note that Jordan was having > trouble a few days ago when he tried to upgrade his 90Mhz machine (same > motherboard as you) to 100Mhz. When he replaced the CPU with a 133Mhz one, > his problems went away. In his case, it was obviously a hardware problem, but > since the external cache and memory were operating with the same timing > (66Mhz), I can only conclude that the problem was the CPU itself. Strange... I will see if I can try a 66mhz and 90mhz cpu (don't know if I can get a 133mhz one) > > >This is with an ASUS P55TP4XE/100 , > > 256 Pipline Burst cache, AHA2940 scsi 16MB EDO ram > > Hmmm...what kind of disk are you using on it? I'm definately interested in > the results of any equipment swapping you can do. It's possible that there > is some sort of bug in the VM system (we've been down THIS road plenty of > times :-)), but I haven't seen any problems like that here...and I do > countless make worlds. I have two P55TP4XE based machines here, both are 90Mhz > w/PB cache. I know that Rod does extensive testing with these motherboards, > too, and he does 100Mhz+ there. His tests are all with -stable, however. I have a Seagate st32550N attached to it. Also, I'm running 0111 rev of the ASUS bios. I also tried changing the main memory with standard 60ns simms, no change. I've tried it with -current and -stable and still get signal 11's but less frequently with -stable. Scott