From owner-freebsd-current Sun Sep 15 00:41:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA08113 for current-outgoing; Sun, 15 Sep 1996 00:41:40 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA08105 for ; Sun, 15 Sep 1996 00:41:36 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.7.5/8.7.3) id JAA16917; Sun, 15 Sep 1996 09:41:14 +0200 (SAT) From: John Hay Message-Id: <199609150741.JAA16917@zibbi.mikom.csir.co.za> Subject: Re: sppp with cisco hdlc bug fix In-Reply-To: <199609150202.GAA00358@Lapkin.RoSprint.ru> from Sandy Kovshov at "Sep 15, 96 06:02:16 am" To: sandy@Lapkin.RoSprint.ru (Sandy Kovshov) Date: Sun, 15 Sep 1996 09:41:14 +0200 (SAT) Cc: freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL24 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Here is little patch for bug in sppp pseudo driver with cisco hdlc protocol. > I've found it when test Riscom/N2 card with Cisco. At unknown reason, > Cisco send 20 byte packet (without ppp header) instead of 18 ;) > With old version it cause line hangup on keepalive timeout. > Thanks, I will have a look at it. Just for my own curiousness, what model Cisco are you using and what is the version of its OS? John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Sun Sep 15 04:31:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA16432 for current-outgoing; Sun, 15 Sep 1996 04:31:31 -0700 (PDT) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA16424 for ; Sun, 15 Sep 1996 04:31:12 -0700 (PDT) Received: (from uucp@localhost) by magnet.geophysik.tu-freiberg.de (8.7.5/8.7.3) with UUCP id NAA12702 for freebsd-current@freebsd.org; Sun, 15 Sep 1996 13:31:02 +0200 (MET DST) Received: (from holm@localhost) by unicorn.pppnet.tu-freiberg.de (8.7.5/8.6.9) id NAA05784 for freebsd-current@freebsd.org; Sun, 15 Sep 1996 13:24:10 +0200 (MET DST) From: Holm Tiffe Message-Id: <199609151124.NAA05784@unicorn.pppnet.tu-freiberg.de> Subject: diskless experience To: freebsd-current@freebsd.org Date: Sun, 15 Sep 1996 13:24:10 +0200 (MET DST) Reply-To: holm@geophysik.tu-freiberg.de X-PGP-Fingerprint: 86 EC A5 63 B5 28 78 13 8B FC E9 09 04 6E 86 FC X-Phone: +49-3731-74233 X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk first: WARNIG I don't speak english ! Hi, I'm trying to build an little diskless ISDN - router around an old 386/40 Mainboard with FreeBSD-current and the bisdn-0.97 package available from ftp.muc.ditec.de in /isdn. I have put into the Mainboard a WD8013, a TELES S0/16.3 card, a ancient 8 bit VGA, and 8 Mbytes of Memory. On the boothost machine (also FreeBSD-current) i have set up an extra rootfs and share the /usr fs with the host. The router is booting fine, but I think I have problems with the NFS based swap. I get some "still reboots" and many signal 11's from processes like sendmail, syslogd, inetd and others under heavy load. (tar cvfz /dev/null ./usr) I have tryed 3 Motherboards in the router ( two 486 and one 386 ) and two different Boothosts now, the problems are the same.... Maybe these are VM - problems ? a different problem: The tftpd on the Boothost logs the following after booting the diskless host: Sep 13 20:24:30 unicorn tftpd[6540]: tftpd: read: Connection refused I think, the tftpd is willing to read some status information from the tftp client, and there is no information available ... time out. The tree diskless SUN3/60 (used as Xterms) at work won't boot anymore from the FreeBSD Server with tftp for a while now, I havn't recoginzied this for some time, because there is also a SUN Sparc 2 as Bootserver... Has anyone the same problems ? Can anybody help here ? Holm PS: can we please include the bisdn-package into the CVS tree ? -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Strasse der Einheit 26 * * 09599 Freiberg Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 74200 unicorn!holm and the Answer is no ! * ******************************************************************************* From owner-freebsd-current Sun Sep 15 06:07:06 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA18655 for current-outgoing; Sun, 15 Sep 1996 06:07:06 -0700 (PDT) Received: from uuserve.on.ca (uuserve.on.ca [192.139.145.85]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA18650; Sun, 15 Sep 1996 06:07:03 -0700 (PDT) Received: (from rjr@localhost) by sparks.empath.on.ca (8.7.5/8.6.12) id JAA05405; Sun, 15 Sep 1996 09:06:53 -0400 (EDT) From: "Robert J. Rutter" Message-Id: <199609151306.JAA05405@sparks.empath.on.ca> Subject: Re: VM problem (OK!!) To: dyson@FreeBSD.ORG Date: Sun, 15 Sep 1996 09:06:53 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG Reply-To: "Robert Rutter" X-Return-Address: rjr@sparks.empath.on.ca X-Os: FreeBSD Unix 2.2-current X-Mailer: ELM [version 2.4ME+ PL25 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In a previous incarnation on local.freebsd-current, dyson@FreeBSD.ORG said: |> |> What option to set ? |> |For 256K cache 'options PQ_MEDIUMCACHE' |For 512K cache 'options PQ_LARGECACHE' |The default is to color for only a 64K cache, which provides only minor |improvements, but is much better than the random allocations that we |(and almost every other free OS) had previously done. I did a 'make world' on a 960913 -current and an i486 with 256K cache. I rebiult the kernel and rebooted, everything is ok. I then put 'options PQ_MEDIUMCACHE' in the kernel config and rebuilt the kernel. Everything is still ok. The kernel size and boot messages are the same. How do I tell if the 256K cache is being configured and used? Cheers, -- Robert Rutter rjr@sparks.empath.on.ca The thing I really like about Windows 95 is its artificial intelligence. For example, check the properties of any file with the extension "old". Windows 95 will tell you that it is an old file. What other major operating system available today has intelligence that is so artificial? From owner-freebsd-current Sun Sep 15 17:56:23 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA29407 for current-outgoing; Sun, 15 Sep 1996 17:56:23 -0700 (PDT) Received: from VX23.CC.MONASH.EDU.AU (vx23.cc.monash.edu.au [130.194.1.23]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA29402 for ; Sun, 15 Sep 1996 17:56:20 -0700 (PDT) Received: from moa.cc.monash.edu.au (george@moa.cc.monash.edu.au) by vaxc.cc.monash.edu.au (PMDF V5.0-6 #16291) id <01I9JLI6H9M899FPU9@vaxc.cc.monash.edu.au>; Mon, 16 Sep 1996 10:55:57 +1000 Received: (george@localhost) by moa.cc.monash.edu.au (8.6.10/8.6.4) id KAA02387; Mon, 16 Sep 1996 10:55:54 +1000 Date: Mon, 16 Sep 1996 10:55:54 +1000 From: George Scott Subject: Re: Build is complete To: FreeBSD-current@FreeBSD.org Cc: jkh@time.cdrom.com Message-id: <199609160055.KAA02387@moa.cc.monash.edu.au> Content-transfer-encoding: 7BIT Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > It sure does if you have no swap partition configured (or it's been > rendered unusable) and you just need to get enough swap made > available, using anything from your windows swap file to a file > hastily constructued in /var somewhere for the purpose, to compile a > rescue kernel. To me that looks like an reason to have vn in the kernel on the fixit floppy rather than in GENERIC. George. From owner-freebsd-current Sun Sep 15 18:33:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA01953 for current-outgoing; Sun, 15 Sep 1996 18:33:14 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA01936; Sun, 15 Sep 1996 18:33:10 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id UAA03277; Sun, 15 Sep 1996 20:31:41 -0500 (EST) From: "John S. Dyson" Message-Id: <199609160131.UAA03277@dyson.iquest.net> Subject: Re: VM problem (OK!!) To: rjr@sparks.empath.on.ca Date: Sun, 15 Sep 1996 20:31:41 -0500 (EST) Cc: dyson@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-Reply-To: <199609151306.JAA05405@sparks.empath.on.ca> from "Robert J. Rutter" at Sep 15, 96 09:06:53 am Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > In a previous incarnation on local.freebsd-current, dyson@FreeBSD.ORG said: > |> > |> What option to set ? > |> > |For 256K cache 'options PQ_MEDIUMCACHE' > |For 512K cache 'options PQ_LARGECACHE' > |The default is to color for only a 64K cache, which provides only minor > |improvements, but is much better than the random allocations that we > |(and almost every other free OS) had previously done. > > I did a 'make world' on a 960913 -current and an i486 with 256K cache. > I rebiult the kernel and rebooted, everything is ok. I then put > 'options PQ_MEDIUMCACHE' in the kernel config and rebuilt the kernel. > Everything is still ok. The kernel size and boot messages are the same. > How do I tell if the 256K cache is being configured and used? > The code is a bit rough right now. There is no feedback. Under ddb you can type: call DDB_print_pageq_info and if you have 64 page queues for the free page list, then it is configured. John From owner-freebsd-current Sun Sep 15 23:51:45 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA16249 for current-outgoing; Sun, 15 Sep 1996 23:51:45 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (marble.eps.nagoya-u.ac.jp [133.6.57.68]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA16233 for ; Sun, 15 Sep 1996 23:51:19 -0700 (PDT) Received: from marble.eps.nagoya-u.ac.jp (localhost [127.0.0.1]) by marble.eps.nagoya-u.ac.jp (8.7.4+2.6Wbeta6/3.3W9) with ESMTP id PAA00299 for ; Mon, 16 Sep 1996 15:51:08 +0900 (JST) Message-Id: <199609160651.PAA00299@marble.eps.nagoya-u.ac.jp> To: current@freebsd.org Subject: Cyrix/Ti/IBM 486 & Cyrix 5x86 FPU problem X-Mailer: Mew version 1.05+ on Emacs 19.28.1, Mule 2.3 X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 16 Sep 1996 15:51:07 +0900 From: KATO Takenori Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Cyrix/Ti/IBM 486 and Cyrix 5x86 users, I would provide the solution of another non-Intel CPU problem for FreeBSD-current. Exception 16 (FPU error) could not be handled on some machines with Cyrix/Ti/IBM 486 CPU, even though 80387 (or its compatible) is installed correctly. In such case, kernel says: no 387 emulator in kernel in kernel! and FPU error (e.g., divided by 0, sqrt of negative number) cannot be detected. This problem also appears on Cyrix 5x86 machines when undocumented feature of `faster FPU exception handler' is enabled. The following patch provides a trick to pretend FPU detected and makes kernel use exception 16 to catch FPU error. This feature is #ifdef'ed since it is harmful on 386/i486SX machine without FPU. Please add "options FPU_ERROR_BROKEN" line in your kernel configuration file. After npxattach routine detects FPU, exception 16 interface may work correctly, i.e., you can detect divided by 0 error, etc. Enjoy! ---------- BEGIN ---------- *** npx.c.orig Mon Sep 16 14:45:50 1996 --- npx.c Mon Sep 16 14:46:46 1996 *************** *** 274,279 **** --- 274,288 ---- */ control &= ~(1 << 2); /* enable divide by 0 trap */ fldcw(&control); + #ifdef FPU_ERROR_BROKEN + /* + * FPU error signal doesn't work on some CPU + * accelerator board. + */ + npx_ex16 = 1; + dvp->id_irq = 0; + return (-1); + #endif npx_traps_while_probing = npx_intrs_while_probing = 0; fp_divide_by_0(); if (npx_traps_while_probing != 0) { ---------- END ---------- ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan From owner-freebsd-current Mon Sep 16 00:31:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA18301 for current-outgoing; Mon, 16 Sep 1996 00:31:39 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA18291; Mon, 16 Sep 1996 00:31:04 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA07564; Mon, 16 Sep 1996 17:27:31 +1000 Date: Mon, 16 Sep 1996 17:27:31 +1000 From: Bruce Evans Message-Id: <199609160727.RAA07564@godzilla.zeta.org.au> To: rjr@sparks.empath.on.ca, toor@dyson.iquest.net Subject: Re: VM problem (OK!!) Cc: dyson@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I did a 'make world' on a 960913 -current and an i486 with 256K cache. >> I rebiult the kernel and rebooted, everything is ok. I then put >> 'options PQ_MEDIUMCACHE' in the kernel config and rebuilt the kernel. >> Everything is still ok. The kernel size and boot messages are the same. >> How do I tell if the 256K cache is being configured and used? Maybe using cmp -l to see if something other than the version number has changed. >The code is a bit rough right now. There is no feedback. Under ddb >you can type: > > call DDB_print_pageq_info > >and if you have 64 page queues for the free page list, then it is configured. This function is named vm_page_print_pageq_info in -current. You can simply type `show pageq' to call it, or `show' to get a list of `show' commands. Bruce From owner-freebsd-current Mon Sep 16 05:34:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA01392 for current-outgoing; Mon, 16 Sep 1996 05:34:47 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-140.ut.nl.ibm.net [139.92.42.140]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA01378; Mon, 16 Sep 1996 05:34:40 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id CAA03901; Mon, 16 Sep 1996 02:17:21 +0200 (MET DST) Message-Id: <199609160017.CAA03901@vector.jhs.no_domain> To: dyson@freebsd.org cc: current@freebsd.org Subject: Re: VM/kernel problems? From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Thu, 12 Sep 1996 19:19:30 CDT." <199609130019.TAA06054@dyson.iquest.net> Date: Mon, 16 Sep 1996 02:17:20 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: "John S. Dyson" > > > > I managed to zap my 2 machines here with current of a couple of days back, > > I got lots of sig 11s & 6s, & some free/malloc complaints, > > then I broke new things while fixing other things. > > I'm rebuilding now with old current binaries, then doing a make with 2.1.5 - src/ > > then will crawl back to current of a week or so ago, or maybe back to > > brand new current, once John D announces an OK. > > > > Synopsis: I'll confirm: don't use current of a few days ago folks, it bites - ! > > > Maybe I have made a mistake. For a while, I had warned the -current > mailing list before making my "commit." I will resume that procedure. That'd be nice. I'm certainly not complaining, one expects some volatility in current, but potential storm warnings where possible, are nice :-) BTW I rebuilt with a cvs export -D1-Sep src & that got both boxes stable, so I'm now taking 1 of my 2 boxes right up to current. > I hope to have a dual p6, so > watch out SMP guys :-)... It will also be a second machine to do more > complete testing on. In theory I have 2 boxes, 1 stable (lower case) & 1 current, but actualy both were current to the same bad time window, so I was off line for a while. Keep up the good work John :-) kernel people are hard to find ! Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Mon Sep 16 06:44:18 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA04352 for current-outgoing; Mon, 16 Sep 1996 06:44:18 -0700 (PDT) Received: from Lapkin.RoSprint.ru (root@Lapkin.RoSprint.ru [193.232.88.150]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA04339 for ; Mon, 16 Sep 1996 06:44:12 -0700 (PDT) Received: (from sandy@localhost) by Lapkin.RoSprint.ru (8.7.5/8.6.9) id RAA03985; Mon, 16 Sep 1996 17:41:04 +0400 (MSD) From: Sandy Kovshov Message-Id: <199609161341.RAA03985@Lapkin.RoSprint.ru> Subject: Re: sppp with cisco hdlc bug fix To: jhay@mikom.csir.co.za (John Hay) Date: Mon, 16 Sep 1996 17:41:03 +0400 (MSD) Cc: freebsd-current@FreeBSD.org In-Reply-To: <199609150741.JAA16917@zibbi.mikom.csir.co.za> from "John Hay" at Sep 15, 96 09:41:14 am X-Mailer: ELM [version 2.4 PL24alpha5] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > > > Here is little patch for bug in sppp pseudo driver with cisco hdlc protocol. > > I've found it when test Riscom/N2 card with Cisco. At unknown reason, > > Cisco send 20 byte packet (without ppp header) instead of 18 ;) > > With old version it cause line hangup on keepalive timeout. > > > > Thanks, I will have a look at it. Just for my own curiousness, what model > Cisco are you using and what is the version of its OS? > Cisco Internetwork Operating System Software IOS (tm) 4500 Software (C4500-J-M), Version 11.1(5), RELEASE SOFTWARE (fc1) ROM: System Bootstrap, Version 5.2(7b) [mkamson 7b], RELEASE SOFTWARE (fc1) ROM: 4500 Software (C4500-J-M), Version 11.1(2), RELEASE SOFTWARE (fc1) Your driver is ok. But problem with Cisco - Riscom/N2, because riscom receives 24 bytes data (tested with Linux driver). > John > -- > John Hay -- John.Hay@mikom.csir.co.za > From owner-freebsd-current Mon Sep 16 10:34:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA20229 for current-outgoing; Mon, 16 Sep 1996 10:34:28 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA20222 for ; Mon, 16 Sep 1996 10:34:24 -0700 (PDT) Received: from allegro.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0v2hWr-000Ql6C; Mon, 16 Sep 96 19:32 MET DST From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id TAA19507 for FreeBSD-current@FreeBSD.ORG; Mon, 16 Sep 1996 19:27:55 +0200 Message-Id: <199609161727.TAA19507@allegro.lemis.de> Subject: More on vn driver To: FreeBSD-current@FreeBSD.ORG (FreeBSD current users) Date: Mon, 16 Sep 1996 19:27:55 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk OK, I've configured, built and run a kernel with the vn driver, but my 'make release' still craps out in the same place. I seem to have all sorts of /dev/vn0*, so doesn't seem to be the reason. What else could I need to do? Here's the end of the make output: # make the small bootfd Making the small 4MB boot floppy. sh -e /usr/src/release/doFS.sh /R/stage /mnt 1200 /R/stage/mfsfd 42000 minimum open: Device not configured *** Error code 1 (continuing) rm -rf /R/stage/fixitfd mkdir /R/stage/fixitfd cd /R/stage/fixitfd && mkdir dev stand bin sbin etc mnt mnt1 mnt2 mnt3 mnt4 tmp if true ; then gzip -9 < /R/stage/crunch/fixit > /R/stage/fixitfd/stand/fixit_crunch ; else ln -f /R/stage/crunch/fixit /R/stage/fixitfd/stand/fixit_crunch ; fi chmod 555 /R/stage/fixitfd/stand/fixit_crunch for i in `crunchgen -l /usr/src/release/fixit_crunch.conf` ; do ln -f /R/stage/fixitfd/stand/fixit_crunch /R/stage/fixitfd/stand/$i ; done ( cd /R/stage/fixitfd/dev && cp /R/stage/trees/bin/dev/MAKEDEV . && sh MAKEDEV all ) cp /R/stage/trees/bin/etc/spwd.db /R/stage/fixitfd/etc cp /usr/src/release/fixit.profile /R/stage/fixitfd/.profile sh -e /usr/src/release/doFS.sh /R/stage /mnt 1200 /R/stage/fixitfd 10000 fd1200 open: Device not configured *** Error code 1 (continuing) `doRELEASE' not remade because of errors. + echo make release Finished make release Finished This is all the more fun because I can't just cd to the directory and try it out again. Every attempt takes 15 hours to die in the same place. Greg From owner-freebsd-current Mon Sep 16 10:35:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA20296 for current-outgoing; Mon, 16 Sep 1996 10:35:14 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA20287; Mon, 16 Sep 1996 10:35:11 -0700 (PDT) Received: from allegro.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0v2hWv-000Ql3C; Mon, 16 Sep 96 19:32 MET DST From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id TAA19420; Mon, 16 Sep 1996 19:16:21 +0200 Message-Id: <199609161716.TAA19420@allegro.lemis.de> Subject: Re: VM problem (OK!!) To: dyson@FreeBSD.ORG Date: Mon, 16 Sep 1996 19:16:21 +0200 (MET DST) Cc: FreeBSD-current@FreeBSD.ORG (FreeBSD current users) In-Reply-To: <199609160131.UAA03277@dyson.iquest.net> from "John S. Dyson" at Sep 15, 96 08:31:41 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk John S. Dyson writes: > > The code is a bit rough right now. There is no feedback. Under ddb > you can type: > > call DDB_print_pageq_info > > and if you have 64 page queues for the free page list, then it is configured. DDB_print_page_info maybe? I don't have a DDB_print_pageq_info in my kernel. I also don't see anything which obviously looks like the free page list. Instead, I have free_count (2035), free_reserve, free_min and free_target, all prefixed with cnt.v_. Am I calling the correct function? Greg From owner-freebsd-current Mon Sep 16 10:51:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA21489 for current-outgoing; Mon, 16 Sep 1996 10:51:59 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA21481 for ; Mon, 16 Sep 1996 10:51:57 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA16571; Mon, 16 Sep 1996 13:49:26 -0400 Date: Mon, 16 Sep 1996 13:49:26 -0400 From: Garrett Wollman Message-Id: <9609161749.AA16571@halloran-eldar.lcs.mit.edu> To: grog@lemis.de (Greg Lehey) Cc: FreeBSD-current@FreeBSD.org (FreeBSD current users) Subject: More on vn driver In-Reply-To: <199609161727.TAA19507@allegro.lemis.de> References: <199609161727.TAA19507@allegro.lemis.de> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < This is all the more fun because I can't just cd to the directory and > try it out again. Every attempt takes 15 hours to die in the same > place. # chroot ${RELEASEDIR} /bin/sh -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Mon Sep 16 13:04:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA03678 for current-outgoing; Mon, 16 Sep 1996 13:04:48 -0700 (PDT) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA03672 for ; Mon, 16 Sep 1996 13:04:44 -0700 (PDT) Received: (from bob@localhost) by luke.pmr.com (8.7.5/8.7.3) id PAA15172 for freebsd-current@freefall.cdrom.com; Mon, 16 Sep 1996 15:04:38 -0500 (CDT) From: Bob Willcox Message-Id: <199609162004.PAA15172@luke.pmr.com> Subject: Errors on make world linking pgms that use libresolv.a in -current?? To: freebsd-current@freefall.FreeBSD.org (freebsd-current) Date: Mon, 16 Sep 1996 15:04:38 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I have been receiving errors like: ===> usr.bin/dig cc -O -pipe -I/usr/src/usr.bin/dig/../../contrib/bind -I/usr/src/usr.bin/dig/../../contrib/bind/include -DUSE_OPTIONS_H -c /usr/src/usr.bin/dig/../../contrib/bind/tools/dig.c cc -O -pipe -I/usr/src/usr.bin/dig/../../contrib/bind -I/usr/src/usr.bin/dig/../../contrib/bind/include -DUSE_OPTIONS_H -c /usr/src/usr.bin/dig/../../contrib/bind/tools/nslookup/list.c cc -O -pipe -I/usr/src/usr.bin/dig/../../contrib/bind -I/usr/src/usr.bin/dig/../../contrib/bind/include -DUSE_OPTIONS_H -c /usr/src/usr.bin/dig/../../contrib/bind/tools/nslookup/subr.c cc -O -pipe -I/usr/src/usr.bin/dig/../../contrib/bind -I/usr/src/usr.bin/dig/../../contrib/bind/include -DUSE_OPTIONS_H -c /usr/src/usr.bin/dig/../../contrib/bind/tools/nslookup/debug.c cc -O -pipe -I/usr/src/usr.bin/dig/../../contrib/bind -I/usr/src/usr.bin/dig/../../contrib/bind/include -DUSE_OPTIONS_H -c /usr/src/usr.bin/dig/../../contrib/bind/tools/nslookup/send.c cc -O -pipe -I/usr/src/usr.bin/dig/../../contrib/bind -I/usr/src/usr.bin/dig/../../contrib/bind/include -DUSE_OPTIONS_H -o dig dig.o list.o subr.o debug.o send.o list.o: Undefined symbol `_inet_nsap_ntoa' referenced from text segment list.o: Undefined symbol `_inet_ntop' referenced from text segment debug.o: Undefined symbol `_inet_nsap_ntoa' referenced from text segment debug.o: Undefined symbol `_inet_ntop' referenced from text segment *** Error code 1 (continuing) For some time now when doing a make world on my -current system. The loading/linking of the failing programs all have problems with the above undefined symbols or others closely related to them. I suspect that I have forgotten/neglected to do something with the move of bind into the contrib heiarchy, but for the life of me, don't know what it is. Any help is greatly appreciated. Thanks, -- Bob Willcox politics, n: bob@luke.pmr.com A strife of interests masquerading as a contest of Austin, TX principles. The conduct of public affairs for private advantage. -- Ambrose Bierce From owner-freebsd-current Mon Sep 16 14:39:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10205 for current-outgoing; Mon, 16 Sep 1996 14:39:03 -0700 (PDT) Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA10197 for ; Mon, 16 Sep 1996 14:38:57 -0700 (PDT) Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7.4) id OAA29040; Mon, 16 Sep 1996 14:38:40 -0700 (PDT) Received: from localhost by newport.ece.uci.edu (8.7.4) id OAA05187; Mon, 16 Sep 1996 14:38:38 -0700 (PDT) Message-Id: <199609162138.OAA05187@newport.ece.uci.edu> To: Bruce Evans cc: freebsd-current@freebsd.org Subject: Re: Object directory changes to make In-reply-to: Your message of "Tue, 10 Sep 1996 07:00:19 +1000." <199609092100.HAA27432@godzilla.zeta.org.au> Date: Mon, 16 Sep 1996 14:38:33 -0700 From: Steven Wallace Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have made more changes to make and the makefiles as per our previous discussion. Bruce, will you look over ~swallace/work/make and ~swallace/work/mk once more before I commit? The object directory searching goes as follows. If the env var MAKEOBJDIRPREFIX is not set, then it's ${.CURDIR}/obj.`uname -m` $(.CURDIR}/obj ${MAKEOBJDIRPREFIX}`cwd` ${.CURDIR} If it IS set, then the order is ${MAKEOBJDIRPREFIX}`cwd` ${.CURDIR} I chose to make obj by default have a higher priority if MAKEOBJDIRPREFIX is not set because with an obj tree one may wish to use the object tree for something at /usr/obj/a/b/c, but not for /usr/obj/a/b. Since /usr/obj/a/b/ must be created for /usr/obj/a/b/c, /a/b/obj will not be used. The obj tree can be forced to used if MAKEOBJDIRPREFIX is set. .TARGETOBJDIR has been removed from make and CANONICALOBJDIR set in bsd.obj.mk. Also, a make target called objwarn checks to see if ${.OBJDIR} != ${.CURDIR} and ${.OBJDIR} != ${CANONICALOBJDIR} and outputs a warning. (No warning for the latter if MAKEOBJDIR or MAKEOBJDIRPREFIX is set). objwarn is called from bsd.prog.mk, bsd.kmod.mk, and bsd.lib.mk. Steven From owner-freebsd-current Mon Sep 16 16:49:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id QAA20830 for current-outgoing; Mon, 16 Sep 1996 16:49:01 -0700 (PDT) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA20824 for ; Mon, 16 Sep 1996 16:48:57 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.7.5/8.7.3) with SMTP id SAA08120; Mon, 16 Sep 1996 18:47:35 -0500 (CDT) X-Sender: rkw@eel.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 16 Sep 1996 18:47:37 -0500 To: Steven Wallace From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Object directory changes to make Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steven -- If I understand the changes that you are making, I HAVE VERY STRONG OBJECTIONS ! I am working hard at setting up an improved build scheme which does not follow the limited uses which you have considered. It appears that I will no longer be able to set the object directory to the desired location because it is neither directly related to the entire `cwd` nor does it end in "obj". In particular, I need to be able to parse the path {PREFIX}/src/{BRANCH}/file.c and put the resulting object in {PERHAPS_ANOTHER_PREFIX}/obj/{BRANCH}/file.o As I understand it, your scheme will not permit this. I still recomend consideration of some scheme that passes a "rule template" rather than using any set of fixed rules. Only the "default rule" needs to be built-in". >I have made more changes to make and the makefiles as per our >previous discussion. Bruce, will you look over ~swallace/work/make >and ~swallace/work/mk once more before I commit? > >The object directory searching goes as follows. If the env var >MAKEOBJDIRPREFIX is not set, then it's > >${.CURDIR}/obj.`uname -m` >$(.CURDIR}/obj >${MAKEOBJDIRPREFIX}`cwd` >${.CURDIR} > >If it IS set, then the order is >${MAKEOBJDIRPREFIX}`cwd` >${.CURDIR} From owner-freebsd-current Mon Sep 16 17:05:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA21745 for current-outgoing; Mon, 16 Sep 1996 17:05:09 -0700 (PDT) Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA21740 for ; Mon, 16 Sep 1996 17:05:05 -0700 (PDT) Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7.4) id RAA03730; Mon, 16 Sep 1996 17:04:55 -0700 (PDT) Received: from localhost by newport.ece.uci.edu (8.7.4) id RAA06410; Mon, 16 Sep 1996 17:04:53 -0700 (PDT) Message-Id: <199609170004.RAA06410@newport.ece.uci.edu> To: rkw@dataplex.net (Richard Wackerbarth) cc: current@freebsd.org Subject: Re: Object directory changes to make In-reply-to: Your message of "Mon, 16 Sep 1996 18:47:37 CDT." Date: Mon, 16 Sep 1996 17:04:51 -0700 From: Steven Wallace Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I am working hard at setting up an improved build scheme which does not > follow the limited uses which you have considered. The purpose of my changes is to bring back compatability of previous make yet retain new object tree changes. I also cleaned up some nasties. > > It appears that I will no longer be able to set the object directory to the > desired location because it is neither directly related to the entire `cwd` > nor does it end in "obj". If you want to set the object directory to a specific location, use MAKEOBJDIR=_path_ If you want it related to the entire `cwd` then do MAKEOBJDIRPREFIX=_prefix_path_ I don't understand what the problem is! > > I still recomend consideration of some scheme that passes a "rule template" > rather than using any set of fixed rules. Only the "default rule" needs to > be built-in". Fine! If you want to write a rule template thing, go ahead. Consider my changes to be the "default rule". Steven From owner-freebsd-current Mon Sep 16 22:22:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA09417 for current-outgoing; Mon, 16 Sep 1996 22:22:32 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA09409; Mon, 16 Sep 1996 22:22:28 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.6.12/8.6.12) with SMTP id WAA13761; Mon, 16 Sep 1996 22:22:27 -0700 Date: Mon, 16 Sep 1996 22:22:26 -0700 (PDT) From: Jaye Mathisen To: hackers@freebsd.org, current@freebsd.org Subject: What bad things happen if I run 2.1 bins with 2.2-current kernel? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is this likely to work OK? I realize programs like ps and stuff will need rebuilding, but what about more "userland" type stuff? From owner-freebsd-current Tue Sep 17 04:15:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA27685 for current-outgoing; Tue, 17 Sep 1996 04:15:16 -0700 (PDT) Received: from eel.dataplex.net (eel.dataplex.net [208.2.87.2]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA27680 for ; Tue, 17 Sep 1996 04:15:13 -0700 (PDT) Received: from [208.2.87.4] (cod [208.2.87.4]) by eel.dataplex.net (8.7.5/8.7.3) with SMTP id GAA18931; Tue, 17 Sep 1996 06:15:06 -0500 (CDT) X-Sender: rkw@eel.dataplex.net Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 17 Sep 1996 06:15:06 -0500 To: Steven Wallace From: rkw@dataplex.net (Richard Wackerbarth) Subject: Re: Object directory changes to make Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Fine! If you want to write a rule template thing, go ahead. >Consider my changes to be the "default rule". No. Although I support the idea of cleaning up the code, I do not support adding anything to the "default" action. It is bad enough that we need to support <...>., <...>/obj, and <...>/. There is no reason to add to that list. The problem with your attitude is that it builds even more unnecessary "legacy" baggage. There is no reason for me to have to support your changes as the default. You are not adding any functionality above that which my model handles. A more general solution is superior and no more difficult to implement. Unless you have a solution that handles my case as well as your own, I think that we should stay with the status quo. I consider that your changes introduce an unnecessary "wart" and wish to remove it before it becomes an entrenched item which has to be supported. From owner-freebsd-current Tue Sep 17 07:54:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA15247 for current-outgoing; Tue, 17 Sep 1996 07:54:24 -0700 (PDT) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA15160; Tue, 17 Sep 1996 07:53:22 -0700 (PDT) Received: from campa.panke.de (anonymous229.ppp.cs.tu-berlin.de [130.149.17.229]) by mail.cs.tu-berlin.de (8.6.12/8.6.12) with ESMTP id QAA05129; Tue, 17 Sep 1996 16:34:12 +0200 Received: (from wosch@localhost) by campa.panke.de (8.6.12/8.6.12) id PAA01161; Tue, 17 Sep 1996 15:38:37 +0200 Date: Tue, 17 Sep 1996 15:38:37 +0200 From: Wolfram Schneider Message-Id: <199609171338.PAA01161@campa.panke.de> To: phk@freebsd.org CC: current@freebsd.org Subject: ctm & sendmail flags Reply-to: Wolfram Schneider MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ctm should call sendmail with option "-oi" and maybe with option "-oem". man sendmail i Do not take dots on a line by themselves as a message termi- nator. ex Set error processing to mode x. Valid modes are `m' to mail back the error message, `w' to ``write'' back the error mes- sage (or mail it back if the sender is not logged in), `p' to print the errors on the terminal (default), `q' to throw away error messages (only exit status is returned), and `e' to do special processing for the BerkNet. If the text of the mes- sage is not mailed back by modes `m' or `w' and if the sender is local to this machine, a copy of the message is appended to the file dead.letter in the sender's home directory. From owner-freebsd-current Tue Sep 17 11:14:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA01692 for current-outgoing; Tue, 17 Sep 1996 11:14:59 -0700 (PDT) Received: from meter.eng.uci.edu (root@meter.eng.uci.edu [128.200.85.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA01680 for ; Tue, 17 Sep 1996 11:14:57 -0700 (PDT) Received: from newport.ece.uci.edu by meter.eng.uci.edu (8.7.4) id LAA18876; Tue, 17 Sep 1996 11:14:54 -0700 (PDT) Received: from localhost by newport.ece.uci.edu (8.7.4) id LAA11730; Tue, 17 Sep 1996 11:14:52 -0700 (PDT) Message-Id: <199609171814.LAA11730@newport.ece.uci.edu> To: rkw@dataplex.net (Richard Wackerbarth) cc: current@freebsd.org Subject: Re: Object directory changes to make In-reply-to: Your message of "Tue, 17 Sep 1996 06:15:06 CDT." Date: Tue, 17 Sep 1996 11:14:51 -0700 From: Steven Wallace Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > No. Although I support the idea of cleaning up the code, I do not support > adding anything to the "default" action. It is bad enough that we need to > support <...>., <...>/obj, and <...>/. There is no reason to add > to that list. I AM NOT ADDING ANYTHING TO THAT LIST. NOW GO AND LOOK AT THE CODE BEFORE YOU SAY ANYTHING MORE. From owner-freebsd-current Tue Sep 17 13:20:20 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11882 for current-outgoing; Tue, 17 Sep 1996 13:20:20 -0700 (PDT) Received: from inga.augusta.de (root@inga.augusta.de [193.175.23.65]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA11871 for ; Tue, 17 Sep 1996 13:20:15 -0700 (PDT) Received: from rabbit by inga.augusta.de with uucp (Smail3.1.29.1 #1) id m0v36Xv-004fXDC; Tue, 17 Sep 96 22:15 MET DST Received: by rabbit.augusta.de (Smail3.1.29.1 #1) id m0v36TG-000A6cC; Tue, 17 Sep 96 22:10 MET DST Message-Id: X-Mailer: exmh version 1.6.7 5/3/96 To: current@freebsd.org Subject: Canīt compile kernel X-url: http://www.augusta.de/~shanee/ Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Tue, 17 Sep 1996 22:10:14 +0200 From: Andreas Kohout Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, since src-cur.2139 (I update my src-tree with srcsrc-cur.2139 - src-cur.2180) I canīt build my kernel: cc -c -O -pipe -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Winline -Wunused -Wpointer-arith -nostdinc -I. -I../.. -I../../sys -I../../../include -DI586_CPU -DPROBE_VERBOSE -DDUMMY_NOPS -DLINUX -DCOMPAT_43 -DCD9660 -DMSDOSFS -DMFS -DNFS -DFFS -DINET -DKERNEL ../../kern/vfs_bio.c ../../kern/vfs_bio.c: In function `allocbuf': ../../kern/vfs_bio.c:1334: structure has no member named `pc' *** Error code 1 Stop. my /sbin/config is new ... Are my sources broken or do I have to wait a while?? -- Greeting, Andy running FreeBSD-current --------------------------------------------------------------------------- From owner-freebsd-current Tue Sep 17 17:29:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA24419 for current-outgoing; Tue, 17 Sep 1996 17:29:13 -0700 (PDT) Received: from wgrobez1.remote.louisville.edu (wgrobez1.remote.louisville.edu [136.165.243.183]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA24414 for ; Tue, 17 Sep 1996 17:29:10 -0700 (PDT) Received: from localhost (wangel@localhost) by wgrobez1.remote.louisville.edu (8.7.5/8.6.12) with SMTP id UAA00261 for ; Tue, 17 Sep 1996 20:28:47 -0400 (EDT) Date: Tue, 17 Sep 1996 20:28:46 -0400 (EDT) From: Gary Roberts To: freebsd-current@freebsd.org Subject: PPP problem with latest CURRENT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have the following problem with the latest FreeBSD-CURRENT. The kernel finds my com2, during probing etc. However, when I try to use PPP, it just gives the PPP logo: PPP USER INTERFACE BY: Blah blah blah and that's it.... it just sits there and 'locks' up so to speak, howerver the com port works because I can use TIP. Any help is appreciated! Gary Roberts System Admin. -- Altered Reality. http://136.165.243.183 -- Main User Pages From owner-freebsd-current Tue Sep 17 18:37:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA29316 for current-outgoing; Tue, 17 Sep 1996 18:37:50 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA29309 for ; Tue, 17 Sep 1996 18:37:47 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id SAA09571; Tue, 17 Sep 1996 18:37:45 -0700 (PDT) Date: Tue, 17 Sep 1996 18:37:45 -0700 (PDT) Message-Id: <199609180137.SAA09571@silvia.HIP.Berkeley.EDU> To: current@freebsd.org Subject: RAM parity error From: asami@freebsd.org (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there any reason why the above would happen when it is NOT the hardware that's broken? I've seen it on a couple of P6 boxes around here, with or without ccd, when I try to push a lot of stuff through the SCSI system (like parallel iozone's on multiple non-ccd filesystems). I'd send you the dmesg output if it's not all disks. I believe this machine has the Intel Natoma chipset with 32MB of parity RAM (9 chips, the middle one is bigger than others, is this the "logic parity" thing?).... Satoshi ------- >> gdb -k kernel.1 vmcore.1 GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.13 (i386-unknown-freebsd), Copyright 1994 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 201000 current pcb at 1e81f0 panic: RAM parity error, likely hardware failure. #0 0xf0113197 in boot () (kgdb) bt #0 0xf0113197 in boot () #1 0xf0113456 in panic () #2 0xf01c5b05 in isa_nmi () #3 0xf01bf2ee in trap () #4 0xf01b4b61 in calltrap () #5 0xf0194652 in scsi_scsi_cmd () #6 0xf0198269 in sdstart () #7 0xf019810e in sd_strategy () #8 0xf0195368 in scsi_strategy () #9 0xf0197c3c in sdstrategy () #10 0xf013927a in spec_strategy () #11 0xf01a4caa in ufs_strategy () #12 0xf012ed33 in cluster_read () #13 0xf019e5d1 in ffs_read () #14 0xf0135a86 in vn_read () #15 0xf011a16f in read () #16 0xf01bfca9 in syscall () #17 0xf01b4bb5 in Xsyscall () #18 0x1095 in ?? () From owner-freebsd-current Tue Sep 17 19:16:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA16379 for current-outgoing; Tue, 17 Sep 1996 19:16:14 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA16273; Tue, 17 Sep 1996 19:15:59 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id TAA01319; Tue, 17 Sep 1996 19:15:54 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609180215.TAA01319@GndRsh.aac.dev.com> Subject: Re: RAM parity error In-Reply-To: <199609180137.SAA09571@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "Sep 17, 96 06:37:45 pm" To: asami@FreeBSD.org (Satoshi Asami) Date: Tue, 17 Sep 1996 19:15:53 -0700 (PDT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > Is there any reason why the above would happen when it is NOT the > hardware that's broken? I've seen it on a couple of P6 boxes around > here, with or without ccd, when I try to push a lot of stuff through > the SCSI system (like parallel iozone's on multiple non-ccd > filesystems). > > I'd send you the dmesg output if it's not all disks. I believe this > machine has the Intel Natoma chipset with 32MB of parity RAM (9 chips, > the middle one is bigger than others, is this the "logic parity" > thing?).... If you have ``logic parity'' instead of true parity you have defeated 75 % of the purpose of even having parity on memory. I would highly encorage you to try a swapout with some ``real parity'' memory and more than likely watch your problem go away... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Sep 17 19:22:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA18287 for current-outgoing; Tue, 17 Sep 1996 19:22:29 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA18262 for ; Tue, 17 Sep 1996 19:22:25 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id TAA09684; Tue, 17 Sep 1996 19:22:06 -0700 (PDT) Date: Tue, 17 Sep 1996 19:22:06 -0700 (PDT) Message-Id: <199609180222.TAA09684@silvia.HIP.Berkeley.EDU> To: rgrimes@GndRsh.aac.dev.com CC: current@FreeBSD.org In-reply-to: <199609180215.TAA01319@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com) Subject: Re: RAM parity error From: asami@FreeBSD.org (Satoshi Asami) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk * If you have ``logic parity'' instead of true parity you have defeated * 75 % of the purpose of even having parity on memory. 75%? I thought that was 100% ;) (Ok, maybe it can check the memory bus failure, but how often would that happen?) * I would highly * encorage you to try a swapout with some ``real parity'' memory and * more than likely watch your problem go away... I'd never buy a "logic parity" board myself, but unfortunately, these machines are donated to our project (they aren't even supposed to be running FreeBSD!) so I can't change anything in them. :( So, do you think this is a memory problem? Is there some other test I can run, other than stressing the SCSI system? (It doesn't crash when I run the "fast bcopy" benchmark, and I think that thing stresses the memory system a lot....) Satoshi From owner-freebsd-current Tue Sep 17 20:15:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA07116 for current-outgoing; Tue, 17 Sep 1996 20:15:35 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA07083; Tue, 17 Sep 1996 20:15:25 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id UAA11084; Tue, 17 Sep 1996 20:16:07 -0700 (PDT) Message-Id: <199609180316.UAA11084@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: asami@FreeBSD.org (Satoshi Asami) cc: current@FreeBSD.org, haertel@ichips.intel.com, erich@uruk.org Subject: Re: RAM parity error In-reply-to: Your message of "Tue, 17 Sep 1996 18:37:45 PDT." <199609180137.SAA09571@silvia.HIP.Berkeley.EDU> From: David Greenman Reply-To: dg@root.com Date: Tue, 17 Sep 1996 20:16:07 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk ["parity" errors on P6 machines during heavy I/O] >Is there any reason why the above would happen when it is NOT the >hardware that's broken? I've seen it on a couple of P6 boxes around >here, with or without ccd, when I try to push a lot of stuff through >the SCSI system (like parallel iozone's on multiple non-ccd >filesystems). *Very* interesting... >#4 0xf01b4b61 in calltrap () >#5 0xf0194652 in scsi_scsi_cmd () >#6 0xf0198269 in sdstart () I'll bet that the real traceback has a "#4.5" that is ahc_scsi_cmd(). gdb often doesn't decode the traceback correctly since it doesn't deal with trapframes correctly. I'm seeing *exactly* the same behavior on wcarchive (B0 Orion, Stepping 1 of the P6). During heavy disk I/O, I occasionally see "RAM parity errors" during the outsl instruction. I've addionally seen *weird* traps - reserved traps that are outside the 0-18 range. These also happen during this _same_ outsl instruction. I believe that whatever is causing this is also the cause of the machine hangs that I'm seeing sometimes multiple times a day. The weird traps look like this: instruction pointer = 0x8:0xe01a4557 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 21 (fsck) interrupt mask = bio kernel: type 28 trap, code=0 Stopped at _ahc_scsi_cmd+0x3ff: repe outsl (%esi),%dx db> tr _ahc_scsi_cmd(e8be6500,eeb4d950,5399c,2,dfbffd94) at _ahc_scsi_cmd+0x3ff _scsi_scsi_cmd(e8b31980,dfbffd88,a,f034c000,400,4,2710,eeb4d950,400) at _scsi_scsi_cmd+0x164 _sdstart(14,0,e8b32e14,eeb4d950) at _sdstart+0xf3 _sd_strategy(eeb4d950,e8b31980,eeb4d950,eeb4d950,dfbfff1c) at _sd_strategy+0x7b _scsi_strategy(eeb4d950,e01ad080,dfbffe24,e010afea,eeb4d950) at _scsi_strategy+0x84 _sdstrategy(eeb4d950,eeb4d950) at _sdstrategy+0x10 _physio(e016811c,0,da0,1,e010b100) at _physio+0x1ca _rawread(da0,dfbfff1c,0,e8be6a00,e8b31580) at _rawread+0x2f _spec_read(dfbffed0,dfbffeec,e012a2ae,dfbffed0,dfbfd3c4) at _spec_read+0x80 _ufsspec_read(dfbffed0,dfbfd3c4,400,dfbfff94,e8be6a00) at _ufsspec_read+0x21 _vn_read(e8be8e00,dfbfff1c,e8b31580,dfbfd3c4,e01a9ce8) at _vn_read+0x86 _read(e8bedc00,dfbfff94,dfbfff8c,a733800,0) at _read+0xa7 _syscall(dfbf0027,f3e0027,6c7000,0,dfbfd400) at _syscall+0x147 _Xsyscall() at _Xsyscall+0x2b --- syscall 3, eip = 0x255a5, ebp = 0xdfbfd400 --- Note that "trap 28" simply indicates that the trap is not within the 0-18 of supported traps (28 is the internal trap number for T_RESERVED, which all unhandled traps translate to). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Sep 17 20:17:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA07487 for current-outgoing; Tue, 17 Sep 1996 20:17:02 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA07460; Tue, 17 Sep 1996 20:16:57 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id UAA11098; Tue, 17 Sep 1996 20:17:39 -0700 (PDT) Message-Id: <199609180317.UAA11098@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: asami@freebsd.org (Satoshi Asami) cc: rgrimes@gndrsh.aac.dev.com, current@freebsd.org Subject: Re: RAM parity error In-reply-to: Your message of "Tue, 17 Sep 1996 19:22:06 PDT." <199609180222.TAA09684@silvia.HIP.Berkeley.EDU> From: David Greenman Reply-To: dg@root.com Date: Tue, 17 Sep 1996 20:17:39 -0700 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * I would highly > * encorage you to try a swapout with some ``real parity'' memory and > * more than likely watch your problem go away... > >I'd never buy a "logic parity" board myself, but unfortunately, these >machines are donated to our project (they aren't even supposed to be >running FreeBSD!) so I can't change anything in them. :( > >So, do you think this is a memory problem? Is there some other test I >can run, other than stressing the SCSI system? (It doesn't crash when >I run the "fast bcopy" benchmark, and I think that thing stresses the >memory system a lot....) Not likely. All of the memory in wcarchive is "true" parity. The parity errors always occur during the *same* instruction. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Tue Sep 17 20:21:21 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA08765 for current-outgoing; Tue, 17 Sep 1996 20:21:21 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08720; Tue, 17 Sep 1996 20:21:11 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id UAA01366; Tue, 17 Sep 1996 20:21:07 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609180321.UAA01366@GndRsh.aac.dev.com> Subject: Re: RAM parity error In-Reply-To: <199609180222.TAA09684@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "Sep 17, 96 07:22:06 pm" To: asami@FreeBSD.org (Satoshi Asami) Date: Tue, 17 Sep 1996 20:21:06 -0700 (PDT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > * If you have ``logic parity'' instead of true parity you have defeated > * 75 % of the purpose of even having parity on memory. > > 75%? I thought that was 100% ;) (Ok, maybe it can check the memory > bus failure, but how often would that happen?) > > * I would highly > * encorage you to try a swapout with some ``real parity'' memory and > * more than likely watch your problem go away... > > I'd never buy a "logic parity" board myself, but unfortunately, these > machines are donated to our project (they aren't even supposed to be > running FreeBSD!) so I can't change anything in them. :( > > So, do you think this is a memory problem? Yes, ``memory parity error'' == hardware fault in the memory subsystem. > Is there some other test I > can run, other than stressing the SCSI system? Yes, ``make world''. > (It doesn't crash when > I run the "fast bcopy" benchmark, and I think that thing stresses the > memory system a lot....) That is only stressing the memory system from the ``host'' port, not from the PCI bus master port. Interactions between the two is what really streeses the memory system to the limits. > > Satoshi > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Sep 17 20:22:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09020 for current-outgoing; Tue, 17 Sep 1996 20:22:08 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08988; Tue, 17 Sep 1996 20:22:03 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id UAA01376; Tue, 17 Sep 1996 20:21:58 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199609180321.UAA01376@GndRsh.aac.dev.com> Subject: Re: RAM parity error In-Reply-To: <199609180222.TAA09684@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "Sep 17, 96 07:22:06 pm" To: asami@freebsd.org (Satoshi Asami) Date: Tue, 17 Sep 1996 20:21:58 -0700 (PDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * If you have ``logic parity'' instead of true parity you have defeated > * 75 % of the purpose of even having parity on memory. > > 75%? I thought that was 100% ;) (Ok, maybe it can check the memory > bus failure, but how often would that happen?) Ooopsss.. didn't hit this one last time... you would be surprised at how often the error actually occurs on the BUS and not from the data out of the chips. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD From owner-freebsd-current Tue Sep 17 20:43:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA17915 for current-outgoing; Tue, 17 Sep 1996 20:43:40 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA17768 for ; Tue, 17 Sep 1996 20:43:18 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id NAA17448; Wed, 18 Sep 1996 13:30:21 +1000 Date: Wed, 18 Sep 1996 13:30:21 +1000 From: Bruce Evans Message-Id: <199609180330.NAA17448@godzilla.zeta.org.au> To: bde@zeta.org.au, swallace@ece.uci.edu Subject: Re: Object directory changes to make Cc: freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have made more changes to make and the makefiles as per our >previous discussion. Bruce, will you look over ~swallace/work/make >and ~swallace/work/mk once more before I commit? The seem to be essentially OK. The objwarn changes seem to be a bit too decentalized. Did you try putting them on the `all' target? Please recover the description of MAKEOBJDIR from an old version. Oops, its semantics has changed. The .${MACHINE} suffix previously didn't apply to it (the same path was bogusly search twice). Please fix this. >The object directory searching goes as follows. If the env var >MAKEOBJDIRPREFIX is not set, then it's > >${.CURDIR}/obj.`uname -m` >$(.CURDIR}/obj >${MAKEOBJDIRPREFIX}`cwd` ^^^^^^^^^^^^^^^^^^^^^^^^^ /usr/obj`cwd` (/usr/obj = default MAXKOBJDIRPREFIX) >${.CURDIR} Also, if MAKEOBJDIRPREFIX is not set, but MAKEOBJDIR is set, then the path is: ${MAKEOBJDIR}.`uname -m` # shouldn't search here ${MAKEOBJDIR} /usr/obj`cwd` # shouldn't search here ${.CURDIR} >If it IS set, then the order is >${MAKEOBJDIRPREFIX}`cwd` >${.CURDIR} Also, MAKEOBJDIRPREFIX has priority over MAKEOBJDIR if both are set. Bruce From owner-freebsd-current Tue Sep 17 20:54:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA22570 for current-outgoing; Tue, 17 Sep 1996 20:54:33 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA22536 for ; Tue, 17 Sep 1996 20:54:27 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id UAA09793; Tue, 17 Sep 1996 20:54:16 -0700 (PDT) Date: Tue, 17 Sep 1996 20:54:16 -0700 (PDT) Message-Id: <199609180354.UAA09793@silvia.HIP.Berkeley.EDU> To: rgrimes@GndRsh.aac.dev.com CC: current@FreeBSD.org In-reply-to: <199609180321.UAA01366@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com) Subject: Re: RAM parity error From: asami@FreeBSD.org (Satoshi Asami) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk * > Is there some other test I * > can run, other than stressing the SCSI system? * * Yes, ``make world''. I've done this many times on this machine, both with and without ccd. Also, it's been compiling most of packages-current recently, and it can run like 4 simultaneous compilations without even flinching. The crash so far has only happened during iozone. It will crash with 100% probability if I run iozone on a ccd with a separate make process. It crashes less frequently if there is only one iozone on a single ccd. It did die with multiple iozone's on non-ccd disks too. * > (It doesn't crash when * > I run the "fast bcopy" benchmark, and I think that thing stresses the * > memory system a lot....) * * That is only stressing the memory system from the ``host'' port, not * from the PCI bus master port. Interactions between the two is what * really streeses the memory system to the limits. I see. Satoshi From owner-freebsd-current Tue Sep 17 21:03:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA24921 for current-outgoing; Tue, 17 Sep 1996 21:03:05 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA24892 for ; Tue, 17 Sep 1996 21:03:01 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id VAA09813; Tue, 17 Sep 1996 21:01:15 -0700 (PDT) Date: Tue, 17 Sep 1996 21:01:15 -0700 (PDT) Message-Id: <199609180401.VAA09813@silvia.HIP.Berkeley.EDU> To: dg@root.com CC: current@FreeBSD.org, haertel@ichips.intel.com, erich@uruk.org In-reply-to: <199609180316.UAA11084@root.com> (message from David Greenman on Tue, 17 Sep 1996 20:16:07 -0700) Subject: Re: RAM parity error From: asami@FreeBSD.org (Satoshi Asami) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk * I'll bet that the real traceback has a "#4.5" that is ahc_scsi_cmd(). gdb * often doesn't decode the traceback correctly since it doesn't deal with * trapframes correctly. I'm seeing *exactly* the same behavior on wcarchive (B0 * Orion, Stepping 1 of the P6). During heavy disk I/O, I occasionally see "RAM * parity errors" during the outsl instruction. That's very interesting to hear. This machine is running 2.2-current (about 1 day old), btw. Intel Natoma, step unknown. By the way, I just remembered that it once crashed during a newfs (over a 35-disk ccd) too. A single disk iozone won't crash it, so I guess having the load of multiple disk I/O's is the problem. Satoshi From owner-freebsd-current Tue Sep 17 21:14:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA29935 for current-outgoing; Tue, 17 Sep 1996 21:14:08 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA29906 for ; Tue, 17 Sep 1996 21:14:04 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.5/8.6.9) id VAA09862; Tue, 17 Sep 1996 21:14:01 -0700 (PDT) Date: Tue, 17 Sep 1996 21:14:01 -0700 (PDT) Message-Id: <199609180414.VAA09862@silvia.HIP.Berkeley.EDU> To: rgrimes@GndRsh.aac.dev.com, current@FreeBSD.org In-reply-to: <199609180354.UAA09793@silvia.HIP.Berkeley.EDU> (asami@FreeBSD.org) Subject: Re: RAM parity error From: asami@FreeBSD.org (Satoshi Asami) Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk * From: asami@FreeBSD.org (Satoshi Asami) * I've done this many times on this machine, both with and without ccd. * Also, it's been compiling most of packages-current recently, and it * can run like 4 simultaneous compilations without even flinching. Well, I guess I spoke a litte too soon. I just started two compilations (xemacs and wine) and it crashed. I'm not sure why it worked before, maybe it's the particular combination of processes (patch on one, tar on the other) or the disk (it's using a Quantum 4GB Atlas now, it was using an array of 4GB Seagates before). Satoshi From owner-freebsd-current Wed Sep 18 00:45:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA12844 for current-outgoing; Wed, 18 Sep 1996 00:45:15 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA12733 for ; Wed, 18 Sep 1996 00:45:05 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id RAA04741 for current@freebsd.org; Wed, 18 Sep 1996 17:15:03 +0930 From: Michael Smith Message-Id: <199609180745.RAA04741@genesis.atrad.adelaide.edu.au> Subject: possible vm kernel death To: current@freebsd.org Date: Wed, 18 Sep 1996 17:15:02 +0930 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hmm. I've been trying to build the world on this (other) machine for days now, and have been plagued with no end of problems. I am _not_ convinced that the machine is 100% hardware reliable. Although earlier this year (march-april) it was worlding every couple of weeks OK, it has (I believe) had a memory swap since then. (P120, Soyo Triton, NCR & 2G seagate). Initially the build was failing _consistently_ when compiling libncurses/lib_options -> lib_options.so; the machine would spontaneously reboot. I've been supping as close as I could, watching for changes filtering through from JD; the kernel it's currently running's /sys/vm Id strings are at the bottom of this message. The reason I post this is just that it looks VM-ish and it _may_ be helpful. Also, the machine is still sitting in DDB if there are extra things I can do to shed light on the subject. The trap is (summarised) as follows : trap 12 fva 0x66 ip 0x8:0xf012f2c6 sp 0x10:0xefbfff28 fp 0x10:0xefbfff3c cs base 0x0, limit 0xfffff, type 0x1b dpl 0, pres 1, def32 1, gran 1 eflags interrupt, resume, iopl = 0 proc 4 (update) interrupt mask (none) _vfs_msync + 0x4e testb 0x1,0x3d(%eax) _sync + 0x40 _kproc_start + 0x32 _main + 0xcc If it makes a difference, the kernel was built on a -STABLE system using /usr/sbin/config from HEAD. Ideas? (These all match the versions I get checking out on freefall) default_pager.c: * $Id: default_pager.c,v 1.9 1996/06/16 20:37:22 dyson Exp $ device_pager.c: * $Id: device_pager.c,v 1.23 1996/05/18 03:37:30 dyson Exp $ kern_lock.c: * $Id: kern_lock.c,v 1.10 1995/12/07 12:48:02 davidg Exp $ swap_pager.c: * $Id: swap_pager.c,v 1.71 1996/09/08 20:44:33 dyson Exp $ vm_fault.c: * $Id: vm_fault.c,v 1.57 1996/09/08 20:44:37 dyson Exp $ vm_glue.c: * $Id: vm_glue.c,v 1.53 1996/09/15 11:24:21 bde Exp $ vm_init.c: * $Id: vm_init.c,v 1.12 1995/12/11 04:58:07 dyson Exp $ vm_kern.c: * $Id: vm_kern.c,v 1.27 1996/07/02 02:08:02 dyson Exp $ vm_map.c: * $Id: vm_map.c,v 1.57 1996/09/14 11:54:55 bde Exp $ vm_meter.c: * $Id: vm_meter.c,v 1.16 1996/09/08 20:44:39 dyson Exp $ vm_mmap.c: * $Id: vm_mmap.c,v 1.49 1996/07/30 03:08:12 dyson Exp $ vm_object.c: * $Id: vm_object.c,v 1.81 1996/09/14 11:54:57 bde Exp $ vm_page.c: * $Id: vm_page.c,v 1.64 1996/09/14 11:54:59 bde Exp $ vm_pageout.c: * $Id: vm_pageout.c,v 1.85 1996/09/08 20:44:48 dyson Exp $ vm_pager.c: * $Id: vm_pager.c,v 1.24 1996/09/08 20:44:49 dyson Exp $ vm_swap.c: * $Id: vm_swap.c,v 1.39 1996/07/12 04:12:25 bde Exp $ vm_unix.c: * $Id: vm_unix.c,v 1.11 1996/06/25 00:36:46 dyson Exp $ vnode_pager.c: * $Id: vnode_pager.c,v 1.64 1996/09/10 05:28:23 dyson Exp $ -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 01:11:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA26286 for current-outgoing; Wed, 18 Sep 1996 01:11:29 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA26251 for ; Wed, 18 Sep 1996 01:11:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id BAA11564; Wed, 18 Sep 1996 01:11:42 -0700 (PDT) Message-Id: <199609180811.BAA11564@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: current@FreeBSD.org Subject: Re: possible vm kernel death In-reply-to: Your message of "Wed, 18 Sep 1996 17:15:02 +0930." <199609180745.RAA04741@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Wed, 18 Sep 1996 01:11:42 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Hmm. I've been trying to build the world on this (other) machine for days >now, and have been plagued with no end of problems. I am _not_ convinced >that the machine is 100% hardware reliable. Although earlier this year >(march-april) it was worlding every couple of weeks OK, it has (I believe) >had a memory swap since then. (P120, Soyo Triton, NCR & 2G seagate). > >Initially the build was failing _consistently_ when compiling >libncurses/lib_options -> lib_options.so; the machine would >spontaneously reboot. I've been supping as close as I could, watching for >changes filtering through from JD; the kernel it's currently running's >/sys/vm Id strings are at the bottom of this message. Are you sure that you're not using some old LKMs? This is definately filesystem related and appears to be caused by a 'sync' to a out of date loadable kernel module. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Wed Sep 18 01:17:26 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA28579 for current-outgoing; Wed, 18 Sep 1996 01:17:26 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA28550 for ; Wed, 18 Sep 1996 01:17:22 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id RAA05042; Wed, 18 Sep 1996 17:47:13 +0930 From: Michael Smith Message-Id: <199609180817.RAA05042@genesis.atrad.adelaide.edu.au> Subject: Re: possible vm kernel death To: dg@root.com Date: Wed, 18 Sep 1996 17:47:12 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, current@FreeBSD.org In-Reply-To: <199609180811.BAA11564@root.com> from "David Greenman" at Sep 18, 96 01:11:42 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk David Greenman stands accused of saying: > > Are you sure that you're not using some old LKMs? This is definately > filesystem related and appears to be caused by a 'sync' to a out of date > loadable kernel module. The system has no mounts other than local UFS filesystems AFAIK (all the NFS mounts were removed earlier as I was suspicious of them too, although NFS is static in the kernel). If it's still possible that another LKM could have been loaded then I'll punt it and try the build again; is there anything I can look at to see which LKM's are loaded? > David Greenman -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 01:37:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA06837 for current-outgoing; Wed, 18 Sep 1996 01:37:57 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA06812 for ; Wed, 18 Sep 1996 01:37:53 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id EAA23626; Wed, 18 Sep 1996 04:37:15 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: dg@root.com, current@FreeBSD.org From: "Gary Palmer" Subject: Re: possible vm kernel death In-reply-to: Your message of "Wed, 18 Sep 1996 17:47:12 +0930." <199609180817.RAA05042@genesis.atrad.adelaide.edu.au> Date: Wed, 18 Sep 1996 04:37:15 -0400 Message-ID: <23623.843035835@orion.webspan.net> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith wrote in message ID <199609180817.RAA05042@genesis.atrad.adelaide.edu.au>: > If it's still possible that another LKM could have been loaded then I'll > punt it and try the build again; is there anything I can look at to see > which LKM's are loaded? `modstat' `lsvfs' should show if a FS is in a lkm too AFAIR. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Wed Sep 18 01:41:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA08482 for current-outgoing; Wed, 18 Sep 1996 01:41:46 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA08424; Wed, 18 Sep 1996 01:41:40 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA05342; Wed, 18 Sep 1996 18:11:31 +0930 From: Michael Smith Message-Id: <199609180841.SAA05342@genesis.atrad.adelaide.edu.au> Subject: Re: possible vm kernel death To: gpalmer@FreeBSD.org (Gary Palmer) Date: Wed, 18 Sep 1996 18:11:31 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, dg@root.com, current@FreeBSD.org In-Reply-To: <23623.843035835@orion.webspan.net> from "Gary Palmer" at Sep 18, 96 04:37:15 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Gary Palmer stands accused of saying: > > Michael Smith wrote in message ID > <199609180817.RAA05042@genesis.atrad.adelaide.edu.au>: > > If it's still possible that another LKM could have been loaded then I'll > > punt it and try the build again; is there anything I can look at to see > > which LKM's are loaded? > > `modstat' > > `lsvfs' should show if a FS is in a lkm too AFAIR. DDB doesn't seem to have these commands 8) The issue is academic, as a Luser visiting the office rebooted the machine _despite_ being told not to. *grumble* (the only LKM in the system is the linux emulator, and I've pulled it out now) > Gary Palmer FreeBSD Core Team Member -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 01:47:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA10967 for current-outgoing; Wed, 18 Sep 1996 01:47:38 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA10893; Wed, 18 Sep 1996 01:47:25 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id SAA05373; Wed, 18 Sep 1996 18:17:22 +0930 From: Michael Smith Message-Id: <199609180847.SAA05373@genesis.atrad.adelaide.edu.au> Subject: Re: possible vm kernel death To: msmith@genesis.atrad.adelaide.edu.au (Michael Smith) Date: Wed, 18 Sep 1996 18:17:22 +0930 (CST) Cc: gpalmer@FreeBSD.org, msmith@atrad.adelaide.edu.au, dg@root.com, current@FreeBSD.org In-Reply-To: <199609180841.SAA05342@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Sep 18, 96 06:11:31 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Michael Smith stands accused of saying: > > DDB doesn't seem to have these commands 8) The issue is academic, as > a Luser visiting the office rebooted the machine _despite_ being told not > to. *grumble* > > (the only LKM in the system is the linux emulator, and I've pulled it > out now) *mumble* and now I have the old behaviour back; random 'memory' things expiring compiling libncurses/lib_options.c. It's not like it's a huge file or anything 8( Time, I think, to look for some new memory 8( > > Gary Palmer FreeBSD Core Team Member -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 02:14:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA20087 for current-outgoing; Wed, 18 Sep 1996 02:14:52 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA20067; Wed, 18 Sep 1996 02:14:48 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id LAA13690; Wed, 18 Sep 1996 11:14:14 +0200 Message-Id: <199609180914.LAA13690@ra.dkuug.dk> Subject: Re: possible vm kernel death To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 18 Sep 1996 11:14:13 +0200 (MET DST) Cc: msmith@genesis.atrad.adelaide.edu.au, gpalmer@FreeBSD.org, msmith@atrad.adelaide.edu.au, dg@Root.COM, current@FreeBSD.org In-Reply-To: <199609180847.SAA05373@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Sep 18, 96 06:17:22 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Michael Smith who wrote: > > Michael Smith stands accused of saying: > > > > DDB doesn't seem to have these commands 8) The issue is academic, as > > a Luser visiting the office rebooted the machine _despite_ being told not > > to. *grumble* > > > > (the only LKM in the system is the linux emulator, and I've pulled it > > out now) > > *mumble* and now I have the old behaviour back; random 'memory' things > expiring compiling libncurses/lib_options.c. It's not like it's a > huge file or anything 8( > > Time, I think, to look for some new memory 8( Ahh, I wouldn't throw out the memory just yet, since the latest VM changes NONE repeat NONE of my machines behaves like they should. I'm seeing random sig11's on my p5 box, and my little notebook is almost unusable. The only ones that still work are the ones that I didn't upgrade :( So I'd wait a bit for John to catch the latest bugs, or go install a system from before sep 7 (I think)... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Wed Sep 18 02:31:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA25941 for current-outgoing; Wed, 18 Sep 1996 02:31:08 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA25843; Wed, 18 Sep 1996 02:30:46 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id TAA05519; Wed, 18 Sep 1996 19:00:44 +0930 From: Michael Smith Message-Id: <199609180930.TAA05519@genesis.atrad.adelaide.edu.au> Subject: Re: possible vm kernel death To: sos@FreeBSD.org Date: Wed, 18 Sep 1996 19:00:44 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, gpalmer@FreeBSD.org, dg@Root.COM, current@FreeBSD.org In-Reply-To: <199609180914.LAA13690@ra.dkuug.dk> from "sos@FreeBSD.org" at Sep 18, 96 11:14:13 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk sos@FreeBSD.org stands accused of saying: > > > > Time, I think, to look for some new memory 8( > > Ahh, I wouldn't throw out the memory just yet, since the latest VM changes > NONE repeat NONE of my machines behaves like they should. > I'm seeing random sig11's on my p5 box, and my little notebook is > almost unusable. The only ones that still work are the ones that I didn't > upgrade :( > > So I'd wait a bit for John to catch the latest bugs, or go install > a system from before sep 7 (I think)... Hmm, not really an option. 8( I don't have the CVS repository here (I'm stupid, I know 8( ), and I need to get this box to a state better than it has been (960612-SNAP) before its regular user gets back and needs it again. FWIW, it's back to 8M from 16 on memory borrowed from another machine and so far is tooling along OK. I'm encouraged enough to go home and let it be (with a kernel 3mo out of sync with userland, I can't talk to it from home 8). I don't know whether the lower memory configuration is affecting things or not, but you could go back to 8M and try 8) 8) 8) > Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 02:38:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA27874 for current-outgoing; Wed, 18 Sep 1996 02:38:31 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA27846; Wed, 18 Sep 1996 02:38:24 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id LAA13877; Wed, 18 Sep 1996 11:38:15 +0200 Message-Id: <199609180938.LAA13877@ra.dkuug.dk> Subject: Re: possible vm kernel death To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 18 Sep 1996 11:38:15 +0200 (MET DST) Cc: sos@FreeBSD.org, msmith@atrad.adelaide.edu.au, gpalmer@FreeBSD.org, dg@Root.COM, current@FreeBSD.org In-Reply-To: <199609180930.TAA05519@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Sep 18, 96 07:00:44 pm From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Michael Smith who wrote: > > FWIW, it's back to 8M from 16 on memory borrowed from another machine > and so far is tooling along OK. I'm encouraged enough to go home > and let it be (with a kernel 3mo out of sync with userland, I can't > talk to it from home 8). > > I don't know whether the lower memory configuration is affecting things > or not, but you could go back to 8M and try 8) 8) 8) Hmm, I see much better results on my notebook if I downgrade it to 4M (the only option :) ), but the problem is not totally gone however... (And the poor notebook pages it self to death). But it might be usefull info though, John are you listening ?? -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time. From owner-freebsd-current Wed Sep 18 05:33:01 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA11946 for current-outgoing; Wed, 18 Sep 1996 05:33:01 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA11910; Wed, 18 Sep 1996 05:32:58 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id FAA11866; Wed, 18 Sep 1996 05:33:34 -0700 (PDT) Message-Id: <199609181233.FAA11866@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: sos@FreeBSD.org, gpalmer@FreeBSD.org, current@FreeBSD.org Subject: Re: possible vm kernel death In-reply-to: Your message of "Wed, 18 Sep 1996 19:00:44 +0930." <199609180930.TAA05519@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Wed, 18 Sep 1996 05:33:34 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >sos@FreeBSD.org stands accused of saying: >> > >> > Time, I think, to look for some new memory 8( >> >> Ahh, I wouldn't throw out the memory just yet, since the latest VM changes >> NONE repeat NONE of my machines behaves like they should. >> I'm seeing random sig11's on my p5 box, and my little notebook is >> almost unusable. The only ones that still work are the ones that I didn't >> upgrade :( >> >> So I'd wait a bit for John to catch the latest bugs, or go install >> a system from before sep 7 (I think)... > >Hmm, not really an option. 8( I don't have the CVS repository here >(I'm stupid, I know 8( ), and I need to get this box to a state better >than it has been (960612-SNAP) before its regular user gets back and >needs it again. Ohhh...this machine is running the June 16th SNAP? Yes, that was quite broken. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Wed Sep 18 06:38:47 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA20519 for current-outgoing; Wed, 18 Sep 1996 06:38:47 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA20404; Wed, 18 Sep 1996 06:38:37 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id XAA05989; Wed, 18 Sep 1996 23:07:51 +0930 From: Michael Smith Message-Id: <199609181337.XAA05989@genesis.atrad.adelaide.edu.au> Subject: Re: possible vm kernel death To: dg@root.com Date: Wed, 18 Sep 1996 23:07:50 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, sos@FreeBSD.org, gpalmer@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199609181233.FAA11866@root.com> from "David Greenman" at Sep 18, 96 05:33:34 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk David Greenman stands accused of saying: > > > >Hmm, not really an option. 8( I don't have the CVS repository here > >(I'm stupid, I know 8( ), and I need to get this box to a state better > >than it has been (960612-SNAP) before its regular user gets back and > >needs it again. > > Ohhh...this machine is running the June 16th SNAP? Yes, that was quite > broken. To be more accurate, it had 960612-SNAP userland and a -current-to-the-minute kernel, with everything static. Either the problem is sufficiently masked by only having 8M, or my problem was indeed the RAM, because with 8M it got ~2hrs into a -world before I had to leave, where with the previous memory config (16M) it wouldn't last more than 20-30 minutes. Current plans have me ordering a bag of sticks tomorrow sometime and apologising to the list for wasting bandwidth. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 06:50:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA27497 for current-outgoing; Wed, 18 Sep 1996 06:50:36 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA27449; Wed, 18 Sep 1996 06:50:31 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id IAA00452; Wed, 18 Sep 1996 08:50:26 -0500 (EST) From: "John S. Dyson" Message-Id: <199609181350.IAA00452@dyson.iquest.net> Subject: Re: possible vm kernel death To: sos@FreeBSD.org Date: Wed, 18 Sep 1996 08:50:26 -0500 (EST) Cc: msmith@atrad.adelaide.edu.au, gpalmer@FreeBSD.org, dg@Root.COM, current@FreeBSD.org In-Reply-To: <199609180938.LAA13877@ra.dkuug.dk> from "sos@FreeBSD.org" at Sep 18, 96 11:38:15 am Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > In reply to Michael Smith who wrote: > > > > FWIW, it's back to 8M from 16 on memory borrowed from another machine > > and so far is tooling along OK. I'm encouraged enough to go home > > and let it be (with a kernel 3mo out of sync with userland, I can't > > talk to it from home 8). > > > > I don't know whether the lower memory configuration is affecting things > > or not, but you could go back to 8M and try 8) 8) 8) > > Hmm, I see much better results on my notebook if I downgrade it > to 4M (the only option :) ), but the problem is not totally > gone however... (And the poor notebook pages it self to death). > > But it might be usefull info though, John are you listening ?? > I am listening, but simply have had no luck reproducing ANY problems in current recently. I have downgraded my system to small memory configs, etc... The last set of bugs that I have fixed were found when I ran in 6MBytes of mem. Darn'it the pmap changes are NECESSARY, but the problems are hard to find... :-(. I run normally with 6MB/8MB/40MB, and have absolutely NO crashes. Some laptops are 486's, and I wonder if somehow we/I have broken compat with those? John From owner-freebsd-current Wed Sep 18 06:53:29 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA29161 for current-outgoing; Wed, 18 Sep 1996 06:53:29 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA29121; Wed, 18 Sep 1996 06:53:24 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id IAA00461; Wed, 18 Sep 1996 08:53:21 -0500 (EST) From: "John S. Dyson" Message-Id: <199609181353.IAA00461@dyson.iquest.net> Subject: Re: possible vm kernel death To: sos@FreeBSD.org Date: Wed, 18 Sep 1996 08:53:21 -0500 (EST) Cc: msmith@atrad.adelaide.edu.au, msmith@genesis.atrad.adelaide.edu.au, gpalmer@FreeBSD.org, dg@Root.COM, current@FreeBSD.org In-Reply-To: <199609180914.LAA13690@ra.dkuug.dk> from "sos@FreeBSD.org" at Sep 18, 96 11:14:13 am Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Ahh, I wouldn't throw out the memory just yet, since the latest VM changes > NONE repeat NONE of my machines behaves like they should. > I'm seeing random sig11's on my p5 box, and my little notebook is > almost unusable. The only ones that still work are the ones that I didn't > upgrade :( > > So I'd wait a bit for John to catch the latest bugs, or go install > a system from before sep 7 (I think)... > My machine is rock-solid under current -current, even under strange loads. I have absolutely no local data showing problems. VN and CCD do have problems, and I have been looking at them. CCD is simply too green to use in production on -current (and I have no hardware to test it on.) VN filesystem I/O has been fixed, but paging I/O is still broken. I can fix that... John From owner-freebsd-current Wed Sep 18 07:05:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA05803 for current-outgoing; Wed, 18 Sep 1996 07:05:05 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA05741; Wed, 18 Sep 1996 07:04:59 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id QAA04622; Wed, 18 Sep 1996 16:04:31 +0200 (MET DST) To: dyson@FreeBSD.org cc: current@FreeBSD.org Subject: Re: possible vm kernel death In-reply-to: Your message of "Wed, 18 Sep 1996 08:50:26 CDT." <199609181350.IAA00452@dyson.iquest.net> Date: Wed, 18 Sep 1996 16:04:29 +0200 Message-ID: <4620.843055469@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >I run normally with 6MB/8MB/40MB, and have absolutely NO crashes. Some laptop >s >are 486's, and I wonder if somehow we/I have broken compat with those? I have seen problems on my i486dx2/40 laptop and on my P5/133. -- 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 Wed Sep 18 07:49:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA25775 for current-outgoing; Wed, 18 Sep 1996 07:49:33 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA25723; Wed, 18 Sep 1996 07:49:26 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id AAA06146; Thu, 19 Sep 1996 00:19:23 +0930 From: Michael Smith Message-Id: <199609181449.AAA06146@genesis.atrad.adelaide.edu.au> Subject: Re: possible vm kernel death To: dyson@FreeBSD.org Date: Thu, 19 Sep 1996 00:19:23 +0930 (CST) Cc: sos@FreeBSD.org, msmith@atrad.adelaide.edu.au, gpalmer@FreeBSD.org, dg@Root.COM, current@FreeBSD.org In-Reply-To: <199609181350.IAA00452@dyson.iquest.net> from "John S. Dyson" at Sep 18, 96 08:50:26 am MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk John S. Dyson stands accused of saying: > I am listening, but simply have had no luck reproducing ANY problems > in current recently. I have downgraded my system to small memory > configs, etc... The last set of bugs that I have fixed were found > when I ran in 6MBytes of mem. Darn'it the pmap changes are NECESSARY, > but the problems are hard to find... :-(. I respect this, hence the attempt to provide you with useful information. Looks like a red herring though, so it's hardly anyhelp 8( > John -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 13:21:39 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA06495 for current-outgoing; Wed, 18 Sep 1996 13:21:39 -0700 (PDT) Received: from allmalt.cs.uwm.edu (allmalt.cs.uwm.edu [129.89.35.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA06440 for ; Wed, 18 Sep 1996 13:21:32 -0700 (PDT) Received: (from james@localhost) by allmalt.cs.uwm.edu (8.7.5/8.7.3) id PAA31868 for current@freebsd.org; Wed, 18 Sep 1996 15:21:28 -0500 (CDT) Date: Wed, 18 Sep 1996 15:21:28 -0500 (CDT) From: Jim Lowe Message-Id: <199609182021.PAA31868@allmalt.cs.uwm.edu> To: current@freebsd.org Subject: Diskless/NFS root Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is anyone running FreeBSD-current in a diskless configuration? I am having some trouble getting the nfs swap stuff working correctly under current. Also, does the devfs work well enough for a diskless configuration? -Jim From owner-freebsd-current Wed Sep 18 13:47:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA17283 for current-outgoing; Wed, 18 Sep 1996 13:47:46 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-167.ut.nl.ibm.net [139.92.42.167]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA17180 for ; Wed, 18 Sep 1996 13:47:27 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id PAA06252; Wed, 18 Sep 1996 15:27:53 +0200 (MET DST) Date: Wed, 18 Sep 1996 15:27:53 +0200 (MET DST) Message-Id: <199609181327.PAA06252@vector.jhs.no_domain> To: current@freebsd.org Subject: zero size install files From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone else seeing lots of zero size files on install of current ? (If you'r not, skip this mail :-) I've done 2 make installs recently, last on newest's CTM 2213 I've suffered lots of files truncated to zero size, twice: cd /usr/share; find . -type f -size 0c -print | wc 777 cd /usr ... 1506 lots are manuals, but /usr/share/misc/termcap too, I'm not out of disc space, that drive works fine too, no crashes, gzip -c works OK etc, Zero sizes in parts of /usr/obj, but when I hand make install, it works OK. I'm not looking for help to analyse why, I'll find it eventually, I'm just interested if this unique to my box, or do others see it ? Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Sep 18 13:48:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA17630 for current-outgoing; Wed, 18 Sep 1996 13:48:46 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-167.ut.nl.ibm.net [139.92.42.167]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA17322; Wed, 18 Sep 1996 13:47:52 -0700 (PDT) Received: (from jhs@localhost) by vector.jhs.no_domain (8.7.5/8.6.9) id PAA06161; Wed, 18 Sep 1996 15:10:37 +0200 (MET DST) Date: Wed, 18 Sep 1996 15:10:37 +0200 (MET DST) Message-Id: <199609181310.PAA06161@vector.jhs.no_domain> To: phk@freebsd.org Cc: current@freebsd.org Subject: Re: vm in current is NOT ok yet... From: "Julian H. Stacey" Reply-to: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-address: Holz Strasse 27d, 80469 Munich, Germany X-phone: +49.89.268616 X-fax: +49.89.2608126 X-web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Fri, 13 Sep 1996 19:22:22 +0200." <5638.842635342@critter.tfs.com> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Poul-Henning Kamp > > I just ran a md5 on a 45 mbyte file three times and received 3 > different answers... Just in case ... If you want to exercise your file system (& supporting disc driver) (to be sure it's vn & not a drive becoming ill ), I wrote a program that writes & reads a test pattern file of arbitrary (ie very large) size. It's called Testblock (.c & man). http://www.freebsd.org/~jhs/src/bsd/jhs/bin/public/testblock/ A few of us got nasty unwelcome suprises about supposedly OK drives, after checking with testblock.c, so if you want to be absolutely sure about your drive data reliability, try testblock (runs safely in user mode on file systems, no root or raw devices needed), while simultaneously keeping same disc & other scsi devs busy with other tasks (That's how I got my old supposedly good HP drive to choke & garble data, didnt seem to garble (so much) when less busy). Julian --- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Sep 18 13:54:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA19624 for current-outgoing; Wed, 18 Sep 1996 13:54:17 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA19585; Wed, 18 Sep 1996 13:54:08 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id WAA01173; Wed, 18 Sep 1996 22:53:33 +0200 (MET DST) To: Jim Lowe cc: current@FreeBSD.org Subject: Re: Diskless/NFS root In-reply-to: Your message of "Wed, 18 Sep 1996 15:21:28 CDT." <199609182021.PAA31868@allmalt.cs.uwm.edu> Date: Wed, 18 Sep 1996 22:53:32 +0200 Message-ID: <1171.843080012@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199609182021.PAA31868@allmalt.cs.uwm.edu>, Jim Lowe writes: >Is anyone running FreeBSD-current in a diskless configuration? I am >having some trouble getting the nfs swap stuff working correctly under >current. yes I do: # cat /etc/bootptab: hyst:ht=ethernet:ha=0080ad10e84b:ip=10.0.0.3: # cat /tftpboot/freebsd.10.0.0.3: netmask 255.255.255.0 rootfs 10.0.0.1:/c/diskless_root swapfs 10.0.0.1:/c/diskless_swap swapsize 16384 # ls -l /c/diskl* /c/diskless_root: total 6375 drwxr-xr-x 2 bin bin 512 Jul 7 14:41 bin drwx------ 3 root wheel 10240 Sep 18 21:24 dev drwxr-xr-x 9 root wheel 1536 Sep 14 22:55 etc ... /c/diskless_swap: total 16392 -rw------- 1 root wheel 16777216 Jul 22 20:36 swap.10.0.0.3 # cat /etc/exports ... /c -alldirs -maproot=0:10 10.0.0.3 10.0.0.2 ... >Also, does the devfs work well enough for a diskless configuration? yes. You need to mount it as one of the first things in /sbin/init or earlier. -- 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 Wed Sep 18 14:13:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA26503 for current-outgoing; Wed, 18 Sep 1996 14:13:30 -0700 (PDT) Received: from terd.triskelion.com (root@danj.port.net [205.161.151.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA26463 for ; Wed, 18 Sep 1996 14:13:23 -0700 (PDT) Received: from fnur.triskelion.com (fnur.triskelion.com [180.200.1.3]) by terd.triskelion.com (8.7.5/8.6.12) with SMTP id RAA00835 for ; Wed, 18 Sep 1996 17:12:18 -0400 (EDT) Message-ID: <324065B6.41C67EA6@netcom.com> Date: Wed, 18 Sep 1996 17:12:22 -0400 From: Dan Janowski Organization: Triskelion Systems, Inc. X-Mailer: Mozilla 2.01 (X11; I; FreeBSD 2.1.0-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.org Subject: Various drivers... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk -current and SCSI: Does the buslogic driver support (in addition to the BT-946) the BT-948,958,956? If not, are there plans? Are there any opinions about which SCSI board works best with -current for performance. What is/are the SCSI board(s) that get the most on-going attention, and are therefore the best investments? -current and 10BaseT/100BaseT: Is there any difference between the 10BaseT and the 100BaseT boards and their support level or stability? For those that are working or have worked on the drivers, is there a perceivable difference between the vendors and their respective implementations (a.k.a madness)? -current and multi-port serial cards: Is there any difference in the drivers, functionality, or performance of these things? I can name about five. Why I ask: I appreciate any answers that I get. I am trying to plot a 'course' through the VAST array of hardware available in an effort to come up the 'best' configurations for FreeBSD. It is my opinion that the driver/kernel development community knows more about the quirks and short comings of these cards than anyone; at least there are preferences that have developed. There may also be varying levels of active work on drivers for new stuff, so I would like to make up a reasonable summary of recommendations for harware buyers. I will gladly add, and maintain, this information to the FreeBSD documentation. Thanks to all, Dan -- danj@netcom.com Dan Janowski Triskelion Systems, Inc. Bronx, NY From owner-freebsd-current Wed Sep 18 14:24:32 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA00241 for current-outgoing; Wed, 18 Sep 1996 14:24:32 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA00196; Wed, 18 Sep 1996 14:24:14 -0700 (PDT) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po2.glue.umd.edu (8.7.5/8.7.3) with ESMTP id RAA20804; Wed, 18 Sep 1996 17:24:11 -0400 (EDT) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.7.5/8.7.3) with SMTP id RAA31655; Wed, 18 Sep 1996 17:24:10 -0400 (EDT) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Wed, 18 Sep 1996 17:24:10 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: "Julian H. Stacey" cc: current@freebsd.org Subject: Re: zero size install files In-Reply-To: <199609181327.PAA06252@vector.jhs.no_domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 18 Sep 1996, Julian H. Stacey wrote: > Anyone else seeing lots of zero size files on install of current ? > (If you'r not, skip this mail :-) > > I've done 2 make installs recently, last on newest's CTM 2213 > I've suffered lots of files truncated to zero size, twice: > cd /usr/share; find . -type f -size 0c -print | wc 777 > cd /usr ... 1506 > lots are manuals, but /usr/share/misc/termcap too, I'm not out of disc space, > that drive works fine too, no crashes, gzip -c works OK etc, > Zero sizes in parts of /usr/obj, but when I hand make install, it works OK. > > I'm not looking for help to analyse why, I'll find it eventually, > I'm just interested if this unique to my box, or do others see it ? 3 3 62 Here on a fresh built make world, for the first line above. Did you mean to use wc -l? > > Julian > --- > Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Wed Sep 18 15:12:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA22853 for current-outgoing; Wed, 18 Sep 1996 15:12:25 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA22750; Wed, 18 Sep 1996 15:12:11 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id SAA09657; Wed, 18 Sep 1996 18:12:07 -0400 (EDT) Date: Wed, 18 Sep 1996 18:12:07 -0400 (EDT) From: Brian Tao Reply-To: FREEBSD-SCSI-L To: FREEBSD-SCSI-L , FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Streamlogic RAID array benchmarks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I now have a P166 equipped with an Adaptec AHA-2940UW controller and a 3x4GB RAID 5 subsystem from Streamlogic (kindly lent to us by Tenex Data Systems here in Toronto). The drive comes preformatted and preconfigured with two data drives and one parity drive. It has two 68-pin wide connectors on the back and a nifty little pop-up LCD panel on the front to control various aspects of the RAID. There is also a 9-pin male serial port on the back if you want to hook up a VT-100 terminal to it. The RAID worked right out of the box. I have a narrow 4GB Barracuda plugged into the 50-pin connector on the Adaptec, and the RAID on the external 68-pin connector. The RAID drives themselves are connected via a 10MB/s narrow SCSI bus to the Streamlogic RAID controller, which then interfaces with the host via a F/W bus. It has four narrow busses, allowing for up to 28 drives per RAID controller. The GENERIC kernel recognizes this setup: FreeBSD 2.2-960801-SNAP #0: Sat Aug 3 15:18:25 1996 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC Calibrating clock(s) relative to mc146818A clock... i586 clock: 133663775 Hz, i8254 clock: 1193428 Hz CPU: Pentium (133.63-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 62947328 (61472K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 pci0:7:1: Intel Corporation, device=0x7010, class=storage (ide) [no driver assigned] ahc0 rev 0 int a irq 11 on pci0:8 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST15150N 0022" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4095MB (8388315 512 byte sectors) (ahc0:2:0): "MICROP LTX 011000 7t38" type 0 fixed SCSI 2 sd1(ahc0:2:0): Direct-Access 8189MB (16772017 512 byte sectors) [...] All the usual tools under FreeBSD treat the RAID as a single drive. The default stripe size is 8K, RAID 5 (striping with parity). This can be changed via the LCD keypad on the unit itself, or with a VT-100 interface via the serial port. The problem I have is that it isn't particularly fast on the raw throughput tests. Granted, there is some overhead in calculating the parity, but I would expect it to go at least as fast as the single 4GB drive. Results from various benchmarks are included below. The tests were conducted on newly newfs'd filesystems. sd0 is the single 4GB drive and sd1 is the RAID. A unit from CMD should be arriving next week, so I'll have another product to benchmark. Comments welcome, and please note the Reply-To. -- Brian Tao (BT300, taob@io.org, taob@ican.net) Senior Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't" >>>>> Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0s1d 2847603 4 2619791 0% /single /dev/sd1s1a 8135644 10 7484783 0% /raid Bonnie 1.0 output is shown here. The single drive easily outpaces the RAID for both linear and random accesses. -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU raid 100 1354 25.1 1308 4.5 1056 7.3 3059 55.9 3190 11.5 139.0 5.1 single 100 3506 66.8 3429 12.0 1848 12.5 5367 99.1 6462 25.6 202.5 7.1 Iozone 2.01 from the packages collection showed a dramatic difference in favour of the non-RAID drive. It was over twice as fast as the RAID both in block reads and block writes. I'm a little suspicious of the read numbers for the single drive... I thought the ST15150N's maxed out at around 6.5MB/s (at least on narrow controllers)? I'm seeing over 8MB/s on a single drive. Does the 2940UW make that much difference even on narrow drives? The test file size was 128MB. Size is the data block size, Write and Read are in bytes per second. -------- RAID -------- ------- SINGLE ------- Size Write Read Size Write Read 256 1334877 3420921 256 3551027 7683304 512 1398101 3477002 512 3312101 8134407 1024 1410614 3519022 1024 3372569 8458822 2048 1413748 3575415 2048 3369923 8646134 4096 1414563 3585862 4096 3360694 8729608 8192 1421233 3568730 8192 3356754 8769713 16384 1419941 3554700 16384 3374556 8347847 32768 1419354 3469979 32768 3375219 8751843 65536 1420176 3408028 65536 3367281 8774192 I then ran a simple test that should take advantage of the 4MB write cache on the RAID controller. Create 10000 files in an empty directory, then retouch their inodes, then delete them all. I performed this on synchronously and asynchronously mounted filesystems on both types of drives. The RAID drive is as fast as an async-mounted single drive filesystem. Times are in min:sec. ----- RAID ----- ---- SINGLE ---- Sync Async Sync Async touch 1:42.24 1:23.95 3:57.62 1:27.80 retouch 0:12.37 0:03.24 1:23.72 0:03.26 remove 0:17.58 0:08.55 1:25.80 0:10.19 Synchronous (RAID): # time touch `jot 10000 1` 0.4u 84.6s 1:42.24 83.2% 10+170k 143+20315io 0pf+0w # time touch `jot 10000 1` 0.3u 3.6s 0:12.37 32.8% 22+193k 0+10000io 0pf+0w # time rm * 0.4u 10.0s 0:17.58 59.6% 184+252k 0+10000io 0pf+0w Asynchronous (RAID): # time touch `jot 10000 1` 0.4u 83.3s 1:23.95 99.7% 10+170k 159+315io 0pf+0w # time touch `jot 10000 1` 0.3u 3.2s 0:03.24 110.8% 22+191k 0+0io 0pf+0w # time rm * 0.2u 9.5s 0:08.55 115.2% 186+253k 0+305io 0pf+0w Synchronous (single): # time touch `jot 10000 1` 0.4u 86.9s 3:57.62 36.7% 10+170k 162+20314io 0pf+0w # time touch `jot 10000 1` 0.4u 3.8s 1:23.72 5.1% 21+191k 0+10000io 0pf+0w # time rm * 0.4u 10.4s 1:25.80 12.6% 186+251k 0+10000io 0pf+0w Asynchronous (single): # time touch `jot 10000 1` 0.4u 82.3s 1:27.80 94.3% 10+170k 159+315io 0pf+0w # time touch `jot 10000 1` 0.3u 3.2s 0:03.26 111.0% 22+191k 0+0io 0pf+0w # time rm * 0.4u 9.4s 0:10.19 96.2% 187+254k 0+305io 0pf+0w The last benchmark was to untar the contents of the /usr filesystem (15330 files, 78469120 bytes). The tar file was located on the same filesystem to which it was untarred. As in the previous benchmark, the RAID is much faster with numerous small file operations. RAID: # time tar xf usr-test.tar 1.7u 20.4s 5:02.25 7.3% 285+329k 2472+51582io 0pf+0w # time rm -rf usr 0.5u 11.3s 2:57.98 6.6% 163+569k 2132+29479io 0pf+0w Single: # time tar xf usr-test.tar 1.6u 18.0s 8:49.25 3.7% 287+329k 1995+49819io 10pf+0w # time rm -rf usr 0.5u 9.1s 4:44.14 3.4% 164+569k 2462+29479io 1pf+0w <<<<< From owner-freebsd-current Wed Sep 18 15:23:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA27717 for current-outgoing; Wed, 18 Sep 1996 15:23:37 -0700 (PDT) Received: from vector.jhs.no_domain (slip139-92-42-157.ut.nl.ibm.net [139.92.42.157]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA27441; Wed, 18 Sep 1996 15:22:58 -0700 (PDT) Received: from vector.jhs.no_domain (localhost [127.0.0.1]) by vector.jhs.no_domain (8.7.5/8.6.9) with ESMTP id AAA26312; Thu, 19 Sep 1996 00:20:23 +0200 (MET DST) Message-Id: <199609182220.AAA26312@vector.jhs.no_domain> To: Chuck Robey cc: current@freebsd.org Subject: Re: zero size install files From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Organization: Vector Systems Ltd. Mailer: EXMH 1.6.7, PGP available X-Address: Holz Strasse 27d, 80469 Munich, Germany X-Phone: +49.89.268616 X-Fax: +49.89.2608126 X-Web: http://www.freebsd.org/~jhs/ In-reply-to: Your message of "Wed, 18 Sep 1996 17:24:10 EDT." Date: Thu, 19 Sep 1996 00:20:22 +0200 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Reference: > From: Chuck Robey > > > Anyone else seeing lots of zero size files on install of current ? > > (If you'r not, skip this mail :-) > > > > I've done 2 make installs recently, last on newest's CTM 2213 > > I've suffered lots of files truncated to zero size, twice: > > cd /usr/share; find . -type f -size 0c -print | wc 777 > > cd /usr ... 1506 > > lots are manuals, but /usr/share/misc/termcap too, I'm not out of disc spac - e, > > that drive works fine too, no crashes, gzip -c works OK etc, > > Zero sizes in parts of /usr/obj, but when I hand make install, it works OK. > > > > I'm not looking for help to analyse why, I'll find it eventually, > > I'm just interested if this unique to my box, or do others see it ? > > 3 3 62 > Here on a fresh built make world, for the first line above. Ah it's just my box then, Thanks Chuck > Did you mean > to use wc -l? Yes Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-current Wed Sep 18 15:31:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA00674 for current-outgoing; Wed, 18 Sep 1996 15:31:49 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA00572; Wed, 18 Sep 1996 15:31:31 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id RAA01314; Wed, 18 Sep 1996 17:31:29 -0500 (EST) From: "John S. Dyson" Message-Id: <199609182231.RAA01314@dyson.iquest.net> Subject: Re: Streamlogic RAID array benchmarks To: freebsd-scsi@freebsd.org Date: Wed, 18 Sep 1996 17:31:29 -0500 (EST) Cc: freebsd-current@freebsd.org, freebsd-isp@freebsd.org In-Reply-To: from "Brian Tao" at Sep 18, 96 06:12:07 pm Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Iozone 2.01 from the packages collection showed a dramatic > difference in favour of the non-RAID drive. It was over twice as fast > as the RAID both in block reads and block writes. I'm a little > suspicious of the read numbers for the single drive... I thought the > ST15150N's maxed out at around 6.5MB/s (at least on narrow > controllers)? I'm seeing over 8MB/s on a single drive. Does the > 2940UW make that much difference even on narrow drives? The test file > size was 128MB. Size is the data block size, Write and Read are in > bytes per second. > If you are running -current (I forgot to check), and since you have 64MBytes, the buffer cache will help even though it is overrun. The buffer cache policy is NOT pure LRU, and you will see the effects of it on a 64MByte system even for a 100MByte benchmark. John From owner-freebsd-current Wed Sep 18 15:51:44 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA07711 for current-outgoing; Wed, 18 Sep 1996 15:51:44 -0700 (PDT) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA07659; Wed, 18 Sep 1996 15:51:36 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.7.X/8.7.3) id IAA10384; Thu, 19 Sep 1996 08:51:27 +1000 Received: from pandora.devetir.qld.gov.au by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id IAA03004; Thu, 19 Sep 1996 08:55:09 +1000 (EST) Received: from netfl15a.devetir.qld.gov.au (netfl15a.devetir.qld.gov.au [167.123.24.12]) by pandora.devetir.qld.gov.au (8.6.10/8.6.12) with ESMTP id IAA09906; Thu, 19 Sep 1996 08:53:10 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id WAA09339; Wed, 18 Sep 1996 22:54:19 GMT Message-Id: <199609182254.WAA09339@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6.5 12/11/95 To: dyson@freebsd.org cc: current@freebsd.org Subject: Re: possible vm kernel death In-reply-to: Your message of "Wed, 18 Sep 1996 08:50:26 EST." <199609181350.IAA00452@dyson.iquest.net> X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Sep 1996 08:54:15 +1000 From: Stephen Hocking Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm running upto the minute current on two machines. One has 16Mb, AMD 486/Dx4-100 & 2 IDE drives. The other has 8Mb, 486/66, Adaptec 1542b, 2Gb Barracuda. Both are rock solid & have survived make worlds (or close enough to it) Stephen -- The views expressed above are not those of the Worker's Compensation Board of Queensland, Australia. From owner-freebsd-current Wed Sep 18 18:48:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA18495 for current-outgoing; Wed, 18 Sep 1996 18:48:27 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA18449 for ; Wed, 18 Sep 1996 18:48:21 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA07430 for current@freebsd.org; Thu, 19 Sep 1996 11:18:09 +0930 From: Michael Smith Message-Id: <199609190148.LAA07430@genesis.atrad.adelaide.edu.au> Subject: (more?) vm oddness To: current@freebsd.org Date: Thu, 19 Sep 1996 11:18:08 +0930 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ok, so maybe I'm overdoing it with the reporting... 8) Anyway, the build went smoothly on the machine in question with 8M, so I'm quite happy blaming memory as the cause of the spontaneous bounces. I don't know if the following then is just coincidence, or something else worth pursuing; hit alt-ctrl-del on the console to reboot with the fresh new system, and (paraphrased): panic : vm_page_free : invalid wire count (3), pindex 0xcf40 vm_page_freechk_and_unqueue + 0xac vm_page_free + 0xac vm_object_terminate + 0x19f vrele + 0x30 ffs_unmount + 0xfd dounmount + 0x90 ufs_unmountall + 0x41 boot + 0x117 reboot + 0x29 -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 19:06:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA27472 for current-outgoing; Wed, 18 Sep 1996 19:06:36 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA27417 for ; Wed, 18 Sep 1996 19:06:29 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA07511; Thu, 19 Sep 1996 11:36:08 +0930 From: Michael Smith Message-Id: <199609190206.LAA07511@genesis.atrad.adelaide.edu.au> Subject: Re: Various drivers... To: danj@netcom.com (Dan Janowski) Date: Thu, 19 Sep 1996 11:36:08 +0930 (CST) Cc: current@FreeBSD.org In-Reply-To: <324065B6.41C67EA6@netcom.com> from "Dan Janowski" at Sep 18, 96 05:12:22 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (redirected to -hardware list, where this belongs. All of us with opinions on hardware hang out here 8) Dan Janowski stands accused of saying: > > -current and SCSI: > > Does the buslogic driver support (in addition to the BT-946) > the BT-948,958,956? If not, are there plans? Justin Gibbs (gibbs@freebsd.org) is the person to talk to about this. I wouldn't, at this point in time, recommend using a Buslogic controller. > Are there any opinions about which SCSI board works best > with -current for performance. The Adaptec 2940 range, hotly followed by cards using the NCR 53c8xx range of chips. Both of these support tagged queueing, which gives them a huge advantage over the Buslogic driver, which (AFAIK) currently does not. > What is/are the SCSI board(s) that get the most on-going > attention, and are therefore the best investments? The two above, again. > -current and 10BaseT/100BaseT: > > Is there any difference between the 10BaseT and the 100BaseT > boards and their support level or stability? Er, speed? Matt Thomas's 'de' driver is, when it works (most of the time) probably the best of the bunch (DC21x4x-based cards from people like SMC and Kingston). There's a 100bT driver for one of the Intel cards, but AFAIR it compares slightly unfavourably. > For those that are working or have worked on the drivers, > is there a perceivable difference between the > vendors and their respective implementations (a.k.a > madness)? Um, there are lots of vendors. Many of them are mad. Be more specific and people (like Rod 8) will be able to be more helpful. > -current and multi-port serial cards: > > Is there any difference in the drivers, functionality, or > performance of these things? I can name about five. Unless you're contemplating a _huge_ number of ports, an AST-style multiport card (from someone like PC-Com or Boca) will work well. Most of the cheap "intelligent" cards use the Cirrus Logic UARTs, which are less efficient than the 16550's on a Boca. For higher-end applications, I would look at the Stallion EasyConnection cards; they're supported by a driver maintained (unofficially) by an employee of Stallion. > I appreciate any answers that I get. I am trying to > plot a 'course' through the VAST array of hardware > available in an effort to come up the 'best' > configurations for FreeBSD. It is my opinion that No single such thing; any configuration has its strong and weak points. > work on drivers for new stuff, so I would like to > make up a reasonable summary of recommendations for > harware buyers. A reasonable idea however. > Dan Janowski Hopefully this has been vaguely useful; there's also a wealth of stuff to be learned from reading back-issues of the -hardware mailing list archive. -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[ From owner-freebsd-current Wed Sep 18 20:01:59 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA19976 for current-outgoing; Wed, 18 Sep 1996 20:01:59 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA19937 for ; Wed, 18 Sep 1996 20:01:53 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id WAA01132; Wed, 18 Sep 1996 22:01:11 -0500 (EST) From: "John S. Dyson" Message-Id: <199609190301.WAA01132@dyson.iquest.net> Subject: Re: (more?) vm oddness To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 18 Sep 1996 22:01:11 -0500 (EST) Cc: current@FreeBSD.org In-Reply-To: <199609190148.LAA07430@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Sep 19, 96 11:18:08 am Reply-To: dyson@FreeBSD.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Ok, so maybe I'm overdoing it with the reporting... 8) > > Anyway, the build went smoothly on the machine in question with 8M, so > I'm quite happy blaming memory as the cause of the spontaneous bounces. > > I don't know if the following then is just coincidence, or something > else worth pursuing; hit alt-ctrl-del on the console to reboot with the > fresh new system, and (paraphrased): > > panic : vm_page_free : invalid wire count (3), pindex 0xcf40 > This is a real problem. I haven't seen it recently in -current. If you are seeing it in today's current, then you are *definitely* doing us all a service by reporting it. If it isn't today's current, then you are repeating a known problem, and still doing us all a service by reporting it :-).... Thanks!!! John From owner-freebsd-current Wed Sep 18 20:27:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA00132 for current-outgoing; Wed, 18 Sep 1996 20:27:05 -0700 (PDT) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA29965 for ; Wed, 18 Sep 1996 20:26:55 -0700 (PDT) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id FAA00974; Thu, 19 Sep 1996 05:00:43 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by klemm.gtn.com (8.7.5/8.7.3) with SMTP id WAA05451; Wed, 18 Sep 1996 22:15:20 +0200 (MET DST) Date: Wed, 18 Sep 1996 22:15:19 +0200 (MET DST) From: Andreas Klemm To: Paul Traina cc: Adam David , fenner@parc.xerox.com, freebsd-current@FreeBSD.ORG Subject: Re: heads up! - /bin/rdisc to die In-Reply-To: <199609130332.UAA05580@precipice.shockwave.com> Message-ID: X-try-apsfilter: ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz X-Fax: +49 2137 2018 X-Phone: +49 2137 2020 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 12 Sep 1996, Paul Traina wrote: > I was mulling that over... it also means making it static ... sigh. :-( > Opinions? Votes? > > I think the bloat of making routed static sucks less than having two programs > that need maintenance, IMO. I think so, too. -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-current Wed Sep 18 20:27:52 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA00376 for current-outgoing; Wed, 18 Sep 1996 20:27:52 -0700 (PDT) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id UAA00292 for ; Wed, 18 Sep 1996 20:27:36 -0700 (PDT) Received: from root.com (implode.root.com) by mail.crl.com with SMTP id AA00997 (5.65c/IDA-1.5 for ); Wed, 18 Sep 1996 20:27:38 -0700 Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id UAA01124; Wed, 18 Sep 1996 20:25:00 -0700 (PDT) Message-Id: <199609190325.UAA01124@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Michael Smith Cc: danj@netcom.com (Dan Janowski), current@FreeBSD.org Subject: Re: Various drivers... In-Reply-To: Your message of "Thu, 19 Sep 1996 11:36:08 +0930." <199609190206.LAA07511@genesis.atrad.adelaide.edu.au> From: David Greenman Reply-To: dg@root.com Date: Wed, 18 Sep 1996 20:25:00 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >> Is there any difference between the 10BaseT and the 100BaseT >> boards and their support level or stability? > >Er, speed? Matt Thomas's 'de' driver is, when it works (most of the >time) probably the best of the bunch (DC21x4x-based cards from people >like SMC and Kingston). There's a 100bT driver for one of the Intel >cards, but AFAIR it compares slightly unfavourably. The Pro/100B actually performs better in some benchmarks for raw speed, and the overhead of the fxp driver is significantly lower (10-20%). On the other hand, old Pro/100B's have a bug in the NIC that causes them to lock up when they get garbage, and I haven't implemented (yet?) a work-around for this. In any case, both the DEC-chip based and Intel-chip based cards work well with FreeBSD and the current drivers for both have no known bugs. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Thu Sep 19 00:10:48 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA11666 for current-outgoing; Thu, 19 Sep 1996 00:10:48 -0700 (PDT) Received: from sasami.jurai.net (root@sasami.jurai.net [206.151.208.162]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA11578; Thu, 19 Sep 1996 00:10:38 -0700 (PDT) Received: from localhost (winter@localhost) by sasami.jurai.net (8.7.5/8.7.3) with SMTP id CAA15277; Thu, 19 Sep 1996 02:11:51 -0500 (CDT) Date: Thu, 19 Sep 1996 02:11:50 -0500 (CDT) From: "Matthew N. Dodd" To: Brian Tao cc: FREEBSD-SCSI-L , FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Re: Streamlogic RAID array benchmarks In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk You said you only had 4 meg of write cache on the Streamlogic. I'd be intrested to see the same tests run with 16 or 32 megs of R/W cache on the RAID. I know the CMD 5400s and 5300s support 128m of RAM, and the 5500 supports 512 meg. More RAM should change those numbers a bit. | Matthew N. Dodd | winter@jurai.net | http://www.jurai.net/~winter | | Technical Manager | mdodd@intersurf.net | http://www.intersurf.net | | InterSurf Online | "Welcome to the net Sir, would you like a handbasket?"| From owner-freebsd-current Thu Sep 19 00:35:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA20415 for current-outgoing; Thu, 19 Sep 1996 00:35:07 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA20380 for ; Thu, 19 Sep 1996 00:35:03 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id AAA09117; Thu, 19 Sep 1996 00:35:09 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id AAA07769; Thu, 19 Sep 1996 00:34:49 -0700 (PDT) Message-Id: <199609190734.AAA07769@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Michael Smith cc: danj@netcom.com (Dan Janowski), current@freebsd.org Subject: Re: Various drivers... In-reply-to: Your message of Thu, 19 Sep 96 11:36:08 +0930. <199609190206.LAA07511@genesis.atrad.adelaide.edu.au> Date: Thu, 19 Sep 1996 00:34:48 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >(redirected to -hardware list, where this belongs. All of us with > opinions on hardware hang out here 8) > >Dan Janowski stands accused of saying: >> >> -current and SCSI: >> >> Does the buslogic driver support (in addition to the BT-946) >> the BT-948,958,956? If not, are there plans? The BT946 and BT956 are definitely supported (I've used a BT956 on NetBSD for several months, and the driver is very similar). I see no reason why the BT948 and BT958 wouldn't work, although they might only run in "non-Ultra" mode. I've personally never tried to run the Ultra cards. >Justin Gibbs (gibbs@freebsd.org) is the person to talk to about this. >I wouldn't, at this point in time, recommend using a Buslogic >controller. The BusLogic cards work just fine, and are very stable. >> Are there any opinions about which SCSI board works best >> with -current for performance. >The Adaptec 2940 range, hotly followed by cards using the NCR >53c8xx range of chips. Both of these support tagged queueing, >which gives them a huge advantage over the Buslogic driver, which >(AFAIK) currently does not. If you have drives that support tagged-command-queuing correctly (most modern SCSI drives made in the last year or two), you can get better performance out of an Adaptec 2940(UW) with tags enabled. Without tagged-command-queuing turned on, the Adaptec and BusLogic cards are almost identical in performance. The NCR (Symbios) 53c8xx cards are also good alternatives, and are relatively inexpensive. If you can find one of these for your motherboard, they can usually be purchased for less than the Adaptec and BusLogic counterparts. Their performance should be about the same as what I just described for the Adaptec. >> What is/are the SCSI board(s) that get the most on-going >> attention, and are therefore the best investments? >The two above, again. The three above, again. Although the Adaptec recently seems to be getting the most consistent attention. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Thu Sep 19 00:42:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA23656 for current-outgoing; Thu, 19 Sep 1996 00:42:30 -0700 (PDT) Received: from citrine.cyberstation.net (hannibal@citrine.cyberstation.net [205.167.0.5]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA23638 for ; Thu, 19 Sep 1996 00:42:27 -0700 (PDT) Received: from localhost (hannibal@localhost) by citrine.cyberstation.net (8.6.12/8.6.12) with SMTP id CAA02054 for ; Thu, 19 Sep 1996 02:42:26 -0500 Date: Thu, 19 Sep 1996 02:42:26 -0500 (CDT) From: Dan Walters To: freebsd-current@freebsd.org Subject: patch for ijppp... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ppp won't let you set a filter like "set ifilter 0 tcp estab", you have to specify a port relation of some sort or it just ignores the whole line. Here's a one-liner that seems to fix it... *** usr.sbin/ppp/filter.c.orig Thu Sep 19 02:37:53 1996 --- usr.sbin/ppp/filter.c Thu Sep 19 02:40:04 1996 *************** *** 206,212 **** filterdata.opt.srcop = filterdata.opt.dstop = A_NONE; return(1); } ! if (argc < 3) { #ifdef notdef printf("bad udp syntax.\n"); #endif --- 206,212 ---- filterdata.opt.srcop = filterdata.opt.dstop = A_NONE; return(1); } ! if ((argc < 3) && (argc != 1 || !STREQ(*argv, "estab"))) { #ifdef notdef printf("bad udp syntax.\n"); #endif ====================================================================== Dan Walters hannibal@cyberstation.net ====================================================================== From owner-freebsd-current Thu Sep 19 01:16:49 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA10243 for current-outgoing; Thu, 19 Sep 1996 01:16:49 -0700 (PDT) Received: from gargoyle.carpe.net (root@gargoyle.carpe.net [194.162.243.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA10179; Thu, 19 Sep 1996 01:16:36 -0700 (PDT) Received: from helva.grefen.carpe.net (helva.grefen.carpe.net [194.162.243.129]) by gargoyle.carpe.net (8.7.4/8.7.3) with ESMTP id KAA01437; Thu, 19 Sep 1996 10:19:24 +0200 (MET DST) Received: from hex.grefen.carpe.net (root@hex [194.162.243.130]) by helva.grefen.carpe.net (8.7.5/8.7.3) with ESMTP id KAA04849; Thu, 19 Sep 1996 10:21:02 +0200 (MET DST) Received: from hex.grefen.carpe.net (grefen@localhost [127.0.0.1]) by hex.grefen.carpe.net (8.7.3/8.7.3) with ESMTP id KAA03416; Thu, 19 Sep 1996 10:20:59 +0200 (MET DST) To: FREEBSD-SCSI-L Cc: FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Re: Streamlogic RAID array benchmarks Reply-To: grefen@carpe.net In-reply-to: Brian Tao's message of Wed, 18 Sep 96 18:12:07 EDT. References: Date: Thu, 19 Sep 1996 10:20:56 +0200 Message-ID: <3409.843121256@hex.grefen.carpe.net> From: Stefan Grefen Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message Brian Tao wrote: [...] > > All the usual tools under FreeBSD treat the RAID as a single > drive. The default stripe size is 8K, RAID 5 (striping with parity). > This can be changed via the LCD keypad on the unit itself, or with a > VT-100 interface via the serial port. > > The tests were conducted on newly newfs'd filesystems. sd0 is the > single 4GB drive and sd1 is the RAID. A unit from CMD should be > arriving next week, so I'll have another product to benchmark. > Comments welcome, and please note the Reply-To. You see the benefits of a RAID array only if you access it with stripe-block size or multiple of it. Especially writes suffer from bad performance if you write fractions of a stripe-block (since it first has to read the the remainder of it or the parity block (or both) depending on implementation and where the fractional access occurred). This gives you a high latency which is results in poor performance at least for single-stream access. I assume from your statements that they use the 3 disks as "Data Data Parity" not as a 'true' RAID 5 "Data Data Data Data Parity" (this would have other side effects too). Assuming that 'stripe size is 8K' means that it has 4K blocks on each drive, Every request <8K is SLOW. (it can also mean 8k blocks on each drive which will demand 16k blocks, the phrase 'stripe size' is used different by different vendors). Some of the RAID drives can be configured to complete the SCSI operation when the block is in memory instead when it is commited to disk. This has the same effect as a disk write buffer (with the disadvanatge that it isn't written in case of a power failure). This can't be turned of on some CMD arrays (the recommend to only use it with an UPS). You need to newfs your filesystem to at least 8 (or 16k) blocksize in the default configuration. This ensures that the majority of writes are as fast as possible. If you have large files and writes you can go for even bigger blocksizes. If you have lots of small files reduce the RAID block to the minimum value and use smaller blocksizes. For 'normally' used filesystems a 1-1 mapping of stripe-blocks to filesystem blocks gives (on most systems) the best overall performance. (You have to balance bandwidth versus latency). On the other hand if the Seagate uses a write buffer and tagged queuing and the RAID doesn't it'll loose on any non purely sequential access. To figure out how fast the RAID can go just dd a huge file (/dev/zero) to and from the raw partition with different blocksizes. $ time dd if=/dev/zero of=/dev/rsd1a bs=4196 count=5120 # this will be SLOW $ time dd if=/dev/zero of=/dev/rsd1a bs=8192 count=10240 $ time dd if=/dev/zero of=/dev/rsd1a bs=16384 count=5120 ... Another good test is to talk to Arrays Cache (turn on every bit of performance switch you can find regardless of data-security) and write as above with the minmum possible request size to it. (512). This gives you the upper-limit on scsi-transaction the drives can handle on your bus. (don't be suprised if it maxes out at 500 (250 k) or so :-) )). Stefan > -- > Brian Tao (BT300, taob@io.org, taob@ican.net) > Senior Systems and Network Administrator, Internet Canada Corp. > "Though this be madness, yet there is method in't" > > -- Stefan Grefen Am Grossberg 16, 55130 Mainz, Germany grefen@carpe.net +49 6131 998566 Fax:+49 6131 998568 Living on Earth may be expensive, but it includes an annual free trip around the Sun. From owner-freebsd-current Thu Sep 19 01:44:55 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21379 for current-outgoing; Thu, 19 Sep 1996 01:44:55 -0700 (PDT) Received: (from julian@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA21356 for current; Thu, 19 Sep 1996 01:44:51 -0700 (PDT) Date: Thu, 19 Sep 1996 01:44:51 -0700 (PDT) From: Julian Elischer Message-Id: <199609190844.BAA21356@freefall.freebsd.org> To: current Subject: current hits production Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk well, kinda.. a judiciously selected snapshot of -current (a few weeks ago) is going out in the product we just anounced.. see www.whistle.com in the products document for a pic. julian From owner-freebsd-current Thu Sep 19 06:53:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA15859 for current-outgoing; Thu, 19 Sep 1996 06:53:36 -0700 (PDT) Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA15832 for ; Thu, 19 Sep 1996 06:53:33 -0700 (PDT) Received: by halloran-eldar.lcs.mit.edu; (5.65v3.2/1.1.8.2/19Aug95-0530PM) id AA08715; Thu, 19 Sep 1996 09:53:24 -0400 Date: Thu, 19 Sep 1996 09:53:24 -0400 From: Garrett Wollman Message-Id: <9609191353.AA08715@halloran-eldar.lcs.mit.edu> To: dg@root.com Cc: Michael Smith , danj@netcom.com (Dan Janowski), current@FreeBSD.org Subject: Re: Various drivers... In-Reply-To: <199609190325.UAA01124@root.com> References: <199609190206.LAA07511@genesis.atrad.adelaide.edu.au> <199609190325.UAA01124@root.com> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk < said: > The Pro/100B actually performs better in some benchmarks for raw speed, and > the overhead of the fxp driver is significantly lower (10-20%). Well, hmmm. It is certainly true that the overhead is lower (I have graphs which demonstrate this). It's also true that it's a dog at sending small packets (more graphs). For every NIC, the amount of time to send a packet is determined: C = A + size*B + w(size) For large sizes, the B term dominates. For small sizes, the A term dominates. Based on my experience, the Intel NICs have a very low B factor but a rather hefty A term; the DEC NICs have a much higher B factor, but a much lower A term. The point where the two curves cross is about size==250 bytes. Whether this matters to you depends a great deal on your application; if you are running a Web server, it probably doesn't, but if you are trying to do videoconferencing, the DEC chip is much better. (Having said that, the socket interface is so slow that you are unlikely to notice the effect either way. Our long-term plans here involve rewriting the socket layer to eliminate much of this problem.) >From our results, I would surmise that the Intel chip has a more efficient PCI DMA engine than the DEC chip. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, ANA, or NSA| - Susan Aglukark and Chad Irschick From owner-freebsd-current Thu Sep 19 10:30:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA08817 for current-outgoing; Thu, 19 Sep 1996 10:30:16 -0700 (PDT) Received: from ns.frihet.com (root@frihet.bayarea.net [205.219.92.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA08732; Thu, 19 Sep 1996 10:29:59 -0700 (PDT) Received: from ns.frihet.com (tweten@localhost [127.0.0.1]) by ns.frihet.com (8.7.5/8.6.12) with ESMTP id KAA06675; Thu, 19 Sep 1996 10:29:20 -0700 (PDT) Message-Id: <199609191729.KAA06675@ns.frihet.com> X-Mailer: exmh version 1.6.7 5/3/96 Reply-To: "David E. Tweten" To: grefen@carpe.net cc: FREEBSD-SCSI-L , FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Re: Streamlogic RAID array benchmarks Date: Thu, 19 Sep 1996 10:29:20 -0700 From: "David E. Tweten" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk grefen@carpe.net said: >I assume from your statements that they use the 3 disks as "Data >Data Parity" not as a 'true' RAID 5 "Data Data Data Data Parity" >(this would have other side effects too). If I read this right, it is an interesting, though incorrect, interpretation of the meaning of the various levels of RAID. Garth Gibson's definition, in the original RAID paper written while he was a Berkeley PhD. student, required that RAID 5 have no disk devoted exclusively either to data or to parity. Instead, the responsibility for parity rotated through all disks in the array as a function of sequential block on disk. That way the potential for concentrating parity block accesses on one disk could be avoided in the presence of small writes. Small writes can be handled by reading all the blocks in a parity group that aren't going to be written and combining all data blocks to get a new parity block. They can also be handled by reading (or remembering) the original data and reading the original parity, followed by combining old data, new data, and old parity to get new parity. The statistical effect of it all is to generate more disk traffic for "the parity disk". The "5" had nothing to do with the number of disks. The numbers, 1 through 5 had everything to do with various disk array architectures. If my memory can be trusted (a dubious proposition), it went something like this: RAID 1 mirroring (ie, write the same block on n disks) RAID 2 bitwise SECDED (eg., Thinking Machines Data Vault) RAID 3 multi-disk array with dedicated parity disk RAID 4 ? (something truly awful that I can't remember) RAID 5 multi-disk array with rotating parity assignment So, while designating three disks as "data, data, parity" is certainly not RAID 5, neither is designating five disks as "data, data, data, data, parity". They are both RAID 3 architecture. -- David E. Tweten | 2047-bit PGP Key fingerprint: | tweten@frihet.com 12141 Atrium Drive | E9 59 E7 5C 6B 88 B8 90 | tweten@and.com Saratoga, CA 95070-3162 | 65 30 2A A4 A0 BC 49 AE | (408) 446-4131 Those who make good products sell products; those who don't, sell solutions. From owner-freebsd-current Fri Sep 20 00:07:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA19306 for current-outgoing; Fri, 20 Sep 1996 00:07:46 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA19188; Fri, 20 Sep 1996 00:07:31 -0700 (PDT) Received: by sovcom.kiae.su id AA29086 (5.65.kiae-1 ); Fri, 20 Sep 1996 10:03:50 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Fri, 20 Sep 96 10:03:50 +0300 Received: (from ache@localhost) by nagual.ru (8.7.5/8.7.3) id LAA00544; Fri, 20 Sep 1996 11:01:23 +0400 (MSD) Message-Id: <199609200701.LAA00544@nagual.ru> Subject: Syscons bug with mark To: current@FreeBSD.org (FreeBSD-current), sos@FreeBSD.org (Soren Schmidt) Date: Fri, 20 Sep 1996 11:01:22 +0400 (MSD) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL25 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Steps to reproduce: 1) Use any program which just overwrites text with new one or clear text without scrollig. 2) Mark some lines on the screen with mouse cursor. 3) Change marked text on the screen by pressing some key, without scrolling 4) Oops! Your mark still in place! What result expected: Mark must be cleared when text under it changed or cleared. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Fri Sep 20 00:18:57 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA25376 for current-outgoing; Fri, 20 Sep 1996 00:18:57 -0700 (PDT) Received: from gargoyle.carpe.net (root@gargoyle.carpe.net [194.162.243.7]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA25263; Fri, 20 Sep 1996 00:18:45 -0700 (PDT) Received: from helva.grefen.carpe.net (helva.grefen.carpe.net [194.162.243.129]) by gargoyle.carpe.net (8.7.4/8.7.3) with ESMTP id JAA04536; Fri, 20 Sep 1996 09:19:25 +0200 (MET DST) Received: from hex.grefen.carpe.net (root@hex [194.162.243.130]) by helva.grefen.carpe.net (8.7.5/8.7.3) with ESMTP id JAA07099; Fri, 20 Sep 1996 09:21:21 +0200 (MET DST) Received: from hex.grefen.carpe.net (grefen@localhost [127.0.0.1]) by hex.grefen.carpe.net (8.7.3/8.7.3) with ESMTP id JAA06410; Fri, 20 Sep 1996 09:21:19 +0200 (MET DST) To: "David E. Tweten" Cc: FREEBSD-SCSI-L , FREEBSD-CURRENT-L , FREEBSD-ISP-L Subject: Re: Streamlogic RAID array benchmarks Reply-To: grefen@carpe.net In-reply-to: "David E. Tweten"'s message <199609191729.KAA06675@ns.frihet.com> of Thu, 19 Sep 96 10:29:20 PDT. References: <199609191729.KAA06675@ns.frihet.com> Date: Fri, 20 Sep 1996 09:21:17 +0200 Message-ID: <6407.843204077@hex.grefen.carpe.net> From: Stefan Grefen Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199609191729.KAA06675@ns.frihet.com> "David E. Tweten" wrote: > grefen@carpe.net said: > >I assume from your statements that they use the 3 disks as "Data > >Data Parity" not as a 'true' RAID 5 "Data Data Data Data Parity" > >(this would have other side effects too). > > If I read this right, it is an interesting, though incorrect, > interpretation of the meaning of the various levels of RAID. It didn't wanted to imply that the parity is always on the same disk. As "Data Data Data Data Parity" on a 3 disk system rotes the parity through the disks !!. [...] Stefan -- Stefan Grefen Am Grossberg 16, 55130 Mainz, Germany grefen@carpe.net +49 6131 998566 Fax:+49 6131 998568 Living on Earth may be expensive, but it includes an annual free trip around the Sun. From owner-freebsd-current Fri Sep 20 03:30:43 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA23414 for current-outgoing; Fri, 20 Sep 1996 03:30:43 -0700 (PDT) Received: from meno.uchicago.edu (meno.uchicago.edu [128.135.21.34]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA23381; Fri, 20 Sep 1996 03:30:38 -0700 (PDT) Received: from meno.uchicago.edu (localhost [127.0.0.1]) by meno.uchicago.edu (8.7.5/8.7.3) with ESMTP id FAA19894; Fri, 20 Sep 1996 05:32:47 -0500 (CDT) Message-Id: <199609201032.FAA19894@meno.uchicago.edu> To: freebsd-current@freebsd.org, dyson@freebsd.org Subject: panic recent kernel MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19890.843215566.1@meno.uchicago.edu> Date: Fri, 20 Sep 1996 05:32:47 -0500 From: steve farrell Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk kernel is from freefall sup on september 13 (i've since supped and built a new one); light was light -- 1 compile running on a p6-150. panic: brelse: free buffer onto another queue?? here's what the trace says: _Debugger(f0114d3c) at _Debugger+0x35 _panic(f012dcd6,f3623d88,0,200202b4,56) at _panic+0x5a _brelse(f3623d88,f3b8200,1,f18a2500,f01e57dc) at _brelse+0x248 _bwrite(f3623d88,efbffd40,f012dc78,efbffd38,f01e5804) at _bwrite+0xc8 _vn_bwrite(efbffd38,f01e5804,f3623d88,efbffe5c,f01995b7) at _vn_bwrite+0xe _bawrite(f3623d88) at _bawrite+0x2c _ffs_truncate(efbffe9c,0,f1770200,efbfff54,20) at _ffs_truncate+0x573 _ufs_setattr(efbffed4,f01e6a88,f188c200,0,f1770200) at _ufs_setattr+0x1cb _ftruncate(f188c200,efbfff94,efbfff84,8074060,57000) at _ftruncate+0xfd _syscall(27,27,0,57000,efbfd5e4) at _syscall+0x183 _Xsyscall() at _Xsyscall+0x35 --- syscall 198, eip = 0x80686a1, ebp = 0xefbfd5e4 --- (ughh! what a pain that is to type in off the serial console i'm using. is there other information from the debugger that i should get in this type of case? is there a way to get this saved to disk so one doesn't have to copy it down manually?) (john -- could this have caused the spontaneous reboots i'd mentioned in the past? the difference between now and then being that i now have a serial console to catch what's going on...) --steve farrell From owner-freebsd-current Fri Sep 20 03:42:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA28740 for current-outgoing; Fri, 20 Sep 1996 03:42:46 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA28711 for ; Fri, 20 Sep 1996 03:42:43 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id DAA00327; Fri, 20 Sep 1996 03:44:11 -0700 (PDT) Message-Id: <199609201044.DAA00327@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: steve farrell cc: freebsd-current@FreeBSD.org Subject: Re: panic recent kernel In-reply-to: Your message of "Fri, 20 Sep 1996 05:32:47 CDT." <199609201032.FAA19894@meno.uchicago.edu> From: David Greenman Reply-To: dg@root.com Date: Fri, 20 Sep 1996 03:44:10 -0700 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >kernel is from freefall sup on september 13 (i've since supped >and built a new one); light was light -- 1 compile running on >a p6-150. > >panic: brelse: free buffer onto another queue?? This bug has already been fixed a few days ago....just update to the current stuff. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-current Fri Sep 20 05:03:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA01642 for current-outgoing; Fri, 20 Sep 1996 05:03:25 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA01611; Fri, 20 Sep 1996 05:03:21 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id VAA14548; Fri, 20 Sep 1996 21:54:30 +1000 Date: Fri, 20 Sep 1996 21:54:30 +1000 From: Bruce Evans Message-Id: <199609201154.VAA14548@godzilla.zeta.org.au> To: dyson@FreeBSD.org, freebsd-current@FreeBSD.org, spfarrel@midway.uchicago.edu Subject: Re: panic recent kernel Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >(ughh! what a pain that is to type in off the serial console i'm >using. is there other information from the debugger that i should get >in this type of case? is there a way to get this saved to disk so >one doesn't have to copy it down manually?) I use `serial_program | tee /tmp/foo'. There is no way to save to disk on the system being debugged. Bruce From owner-freebsd-current Fri Sep 20 07:18:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA25345 for current-outgoing; Fri, 20 Sep 1996 07:18:17 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA25322 for ; Fri, 20 Sep 1996 07:18:14 -0700 (PDT) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po2.glue.umd.edu (8.7.5/8.7.3) with ESMTP id KAA04354 for ; Fri, 20 Sep 1996 10:18:11 -0400 (EDT) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.7.5/8.7.3) with SMTP id KAA14109 for ; Fri, 20 Sep 1996 10:18:10 -0400 (EDT) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Fri, 20 Sep 1996 10:18:10 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: FreeBSD current Subject: libgnumalloc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I saw that the recent changes to the compiler and libs deleted libgnumalloc. This means a lot of currently working ports binaries are scragged, as well as the packages behind them. I got important stuff working again by linking libfakegnumalloc to libgnumalloc, but each make world clears that back out. Sure means lots of finding and recompiling. Is it necessary to delete the old libgnumalloc? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Fri Sep 20 11:23:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA24129 for current-outgoing; Fri, 20 Sep 1996 11:23:14 -0700 (PDT) Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA24104 for ; Fri, 20 Sep 1996 11:23:11 -0700 (PDT) Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA25607; Fri, 20 Sep 96 13:23:09 -0500 Received: from fergus-27.dialup.prtel.com by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA26191; Fri, 20 Sep 96 13:23:07 -0500 Received: (from alk@localhost) by compound.Think.COM (8.7.5/8.7.3) id NAA16230; Fri, 20 Sep 1996 13:23:15 -0500 (CDT) Date: Fri, 20 Sep 1996 13:23:15 -0500 (CDT) From: Tony Kimball Message-Id: <199609201823.NAA16230@compound.Think.COM> To: current@freebsd.org Subject: gnu/usr.bin/cc not building Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ctm cvs-cur 2490: struct resword is undefined (first referenced in c-lex.c) I just switched compilers, so I don't have a solution, just an FYI From owner-freebsd-current Fri Sep 20 11:32:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA27511 for current-outgoing; Fri, 20 Sep 1996 11:32:38 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA27477 for ; Fri, 20 Sep 1996 11:32:33 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA11769 for ; Fri, 20 Sep 1996 20:32:30 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA22504 for freebsd-current@FreeBSD.ORG; Fri, 20 Sep 1996 20:32:00 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.4/keltia-uucp-2.9) id UAA20880; Fri, 20 Sep 1996 20:31:38 +0200 (MET DST) Message-Id: <199609201831.UAA20880@keltia.freenix.fr> Date: Fri, 20 Sep 1996 20:31:37 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Subject: CTM cvs-cur #2486.gz doesn't apply cleanly X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk CTM delta from cvs-cur #2486 doesn't apply cleanly because of a MD5 mismatch on CVSROOT/val-tags. I checked freefall's val-tags and after applying the diff manually I get the same checksum. I think something goofed up during the CTM generation. FYI. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-current Fri Sep 20 11:49:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA07930 for current-outgoing; Fri, 20 Sep 1996 11:49:37 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA07887 for ; Fri, 20 Sep 1996 11:49:33 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id UAA11799 for ; Fri, 20 Sep 1996 20:49:30 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id UAA22684 for freebsd-current@FreeBSD.ORG; Fri, 20 Sep 1996 20:48:55 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.4/keltia-uucp-2.9) id UAA20880; Fri, 20 Sep 1996 20:31:38 +0200 (MET DST) Message-Id: <199609201831.UAA20880@keltia.freenix.fr> Date: Fri, 20 Sep 1996 20:31:37 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Subject: CTM cvs-cur #2486.gz doesn't apply cleanly X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk CTM delta from cvs-cur #2486 doesn't apply cleanly because of a MD5 mismatch on CVSROOT/val-tags. I checked freefall's val-tags and after applying the diff manually I get the same checksum. I think something goofed up during the CTM generation. FYI. -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-current Fri Sep 20 12:00:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA14533 for current-outgoing; Fri, 20 Sep 1996 12:00:09 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA14472 for ; Fri, 20 Sep 1996 12:00:03 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.7.6/8.7.3) id UAA15404; Fri, 20 Sep 1996 20:59:46 +0200 (SAT) From: John Hay Message-Id: <199609201859.UAA15404@zibbi.mikom.csir.co.za> Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly In-Reply-To: <199609201831.UAA20880@keltia.freenix.fr> from Ollivier Robert at "Sep 20, 96 08:31:37 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Fri, 20 Sep 1996 20:59:45 +0200 (SAT) Cc: freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL24 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > CTM delta from cvs-cur #2486 doesn't apply cleanly because of a MD5 > mismatch on CVSROOT/val-tags. I checked freefall's val-tags and after > applying the diff manually I get the same checksum. > That is strange. I have three machines that has gone past that up to #2490 with no problems. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Fri Sep 20 12:01:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA15496 for current-outgoing; Fri, 20 Sep 1996 12:01:37 -0700 (PDT) Received: from grumble.grondar.za (root@grumble.grondar.za [196.7.18.130]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA15453 for ; Fri, 20 Sep 1996 12:01:33 -0700 (PDT) Received: from grumble.grondar.za (mark@localhost.grondar.za [127.0.0.1]) by grumble.grondar.za (8.7.5/8.7.3) with ESMTP id VAA11272; Fri, 20 Sep 1996 21:01:11 +0200 (SAT) Message-Id: <199609201901.VAA11272@grumble.grondar.za> To: roberto@keltia.freenix.fr (Ollivier Robert) cc: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly Date: Fri, 20 Sep 1996 21:01:10 +0200 From: Mark Murray Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk wrote: > CTM delta from cvs-cur #2486 doesn't apply cleanly because of a MD5 > mismatch on CVSROOT/val-tags. I checked freefall's val-tags and after > applying the diff manually I get the same checksum. I think the problem may be your side. It worked just fine for me on a 2.2-CURRENT and a 2.1.5-RELEASE machine. I am currnetly at ctm cvs-cur.2489 on one machine and cvs-cur.2490 on the other. M -- Mark Murray 46 Harvey Rd, Claremont, Cape Town 7700, South Africa +27 21 61-3768 GMT+0200 Finger mark@grondar.za for PGP key From owner-freebsd-current Fri Sep 20 12:08:07 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA19535 for current-outgoing; Fri, 20 Sep 1996 12:08:07 -0700 (PDT) Received: from po2.glue.umd.edu (po2.glue.umd.edu [129.2.128.45]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA19510 for ; Fri, 20 Sep 1996 12:08:04 -0700 (PDT) Received: from fiber.eng.umd.edu (fiber.eng.umd.edu [129.2.98.185]) by po2.glue.umd.edu (8.7.5/8.7.3) with ESMTP id PAA12665; Fri, 20 Sep 1996 15:08:00 -0400 (EDT) Received: from localhost (chuckr@localhost) by fiber.eng.umd.edu (8.7.5/8.7.3) with SMTP id PAA20488; Fri, 20 Sep 1996 15:07:59 -0400 (EDT) X-Authentication-Warning: fiber.eng.umd.edu: chuckr owned process doing -bs Date: Fri, 20 Sep 1996 15:07:58 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@fiber.eng.umd.edu To: Tony Kimball cc: current@freebsd.org Subject: Re: gnu/usr.bin/cc not building In-Reply-To: <199609201823.NAA16230@compound.Think.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 20 Sep 1996, Tony Kimball wrote: > > ctm cvs-cur 2490: > struct resword is undefined (first referenced in c-lex.c) > > I just switched compilers, so I don't have a solution, just an FYI Think you might double check your sources, it built fine for me, as soon as i got all of Nate's ts_sec->tv_sec fixes. None of them were in cc. > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD (301) 220-2114 | version 2.2 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-current Fri Sep 20 12:12:02 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA21779 for current-outgoing; Fri, 20 Sep 1996 12:12:02 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA21752 for ; Fri, 20 Sep 1996 12:11:58 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id MAA19881; Fri, 20 Sep 1996 12:11:59 -0700 (PDT) To: Chuck Robey cc: FreeBSD current Subject: Re: libgnumalloc In-reply-to: Your message of "Fri, 20 Sep 1996 10:18:10 EDT." Date: Fri, 20 Sep 1996 12:11:59 -0700 Message-ID: <19879.843246719@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I agree - this change just broke a whole bunch of X installations, including all of mine. I don't think that things should be left in this state. Jordan > I saw that the recent changes to the compiler and libs deleted > libgnumalloc. This means a lot of currently working ports binaries are > scragged, as well as the packages behind them. I got important stuff > working again by linking libfakegnumalloc to libgnumalloc, but each make > world clears that back out. Sure means lots of finding and recompiling. > Is it necessary to delete the old libgnumalloc? > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 9120 Edmonston Ct #302 | > Greenbelt, MD 20770 | I run Journey2 and n3lxx, both FreeBSD > (301) 220-2114 | version 2.2 current -- and great FUN! > ----------------------------+----------------------------------------------- > From owner-freebsd-current Fri Sep 20 12:13:40 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA22661 for current-outgoing; Fri, 20 Sep 1996 12:13:40 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA22601 for ; Fri, 20 Sep 1996 12:13:32 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id VAA11826 for ; Fri, 20 Sep 1996 21:13:30 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id VAA22981 for freebsd-current@FreeBSD.org; Fri, 20 Sep 1996 21:13:01 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.4/keltia-uucp-2.9) id VAA21273; Fri, 20 Sep 1996 21:12:30 +0200 (MET DST) Message-Id: <199609201912.VAA21273@keltia.freenix.fr> Date: Fri, 20 Sep 1996 21:12:30 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly In-Reply-To: <199609201901.VAA11272@grumble.grondar.za>; from Mark Murray on Sep 20, 1996 21:01:10 +0200 References: <199609201901.VAA11272@grumble.grondar.za> X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Mark Murray: > I think the problem may be your side. It worked just fine for me > on a 2.2-CURRENT and a 2.1.5-RELEASE machine. I am currnetly at > ctm cvs-cur.2489 on one machine and cvs-cur.2490 on the other. John Hay just told me the same thing. The entry for val-tags in _my_ cvs-cur.2486.gz is: CTMFN CVSROOT/val-tags 633 552 664 eed79379eed4c3d699540be49ad9e5b3 8f1e5fc47ec0d2efa49234192d1cf9c9 14 a4 1 ALLMAN y Both checksums are wrong: 221 [20:21] root@keltia:/tmp# md5 val* MD5 (val-tags.old) = aa70527111c92e0d8f7098ad86d90675 before #2486 MD5 (val-tags) = 585a72bdc26ac56b94c6dd5a0c77e3dd after #2486 The second one is in agreement with Freefall. Both cvs-cur.2486.gz agree: 206 [12:09] roberto@freefall:CTM/cvs-cur> md5 cvs-cur.2486.gz MD5 (cvs-cur.2486.gz) = d2678654b9240415906f83a83cbd6c28 223 [20:32] root@keltia:/usr/src# md5 cvs-cur.2486.gz MD5 (cvs-cur.2486.gz) = d2678654b9240415906f83a83cbd6c28 Freefall's cvs-cur.2486 contains: CTMFN CVSROOT/val-tags 633 552 664 eed79379eed4c3d699540be49ad9e5b3 8f1e5fc47ec0d2efa49234192d1cf9c9 14 a4 1 ALLMAN y I'm not imagining things. Both contains the _same_ bad checksums... -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-current Fri Sep 20 12:25:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA00660 for current-outgoing; Fri, 20 Sep 1996 12:25:15 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA00562; Fri, 20 Sep 1996 12:25:07 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id VAA14583; Fri, 20 Sep 1996 21:24:29 +0200 (MET DST) To: roberto@keltia.freenix.fr (Ollivier Robert) cc: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly In-reply-to: Your message of "Fri, 20 Sep 1996 20:31:37 +0200." <199609201831.UAA20880@keltia.freenix.fr> Date: Fri, 20 Sep 1996 21:24:29 +0200 Message-ID: <14581.843247469@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199609201831.UAA20880@keltia.freenix.fr>, Ollivier Robert writes: >CTM delta from cvs-cur #2486 doesn't apply cleanly because of a MD5 >mismatch on CVSROOT/val-tags. I checked freefall's val-tags and after >applying the diff manually I get the same checksum. > >I think something goofed up during the CTM generation. FYI. I belive we need at add val-tags to the exclude list, right Peter ? -- 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 Sep 20 12:27:09 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA01832 for current-outgoing; Fri, 20 Sep 1996 12:27:09 -0700 (PDT) Received: from sunrise.cs.berkeley.edu (root@sunrise.CS.Berkeley.EDU [128.32.38.121]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA01812; Fri, 20 Sep 1996 12:27:07 -0700 (PDT) Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.7.5/8.6.12) id MAA14507; Fri, 20 Sep 1996 12:24:09 -0700 (PDT) Date: Fri, 20 Sep 1996 12:24:09 -0700 (PDT) Message-Id: <199609201924.MAA14507@sunrise.cs.berkeley.edu> To: freebsd-scsi@freebsd.org CC: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org In-reply-to: (message from Brian Tao on Wed, 18 Sep 1996 18:12:07 -0400 (EDT)) Subject: Re: Streamlogic RAID array benchmarks From: asami@freebsd.org (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >raid 100 1354 25.1 1308 4.5 1056 7.3 3059 55.9 3190 11.5 139.0 5.1 >single 100 3506 66.8 3429 12.0 1848 12.5 5367 99.1 6462 25.6 202.5 7.1 Just FYI, we've seen close to 30MB/s with ccd (no mirroring). You need two 2940?W's (or one 3940?W) and at least four disks though. Satoshi From owner-freebsd-current Fri Sep 20 12:29:38 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA03523 for current-outgoing; Fri, 20 Sep 1996 12:29:38 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA03472 for ; Fri, 20 Sep 1996 12:29:33 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id VAA11869 for ; Fri, 20 Sep 1996 21:29:30 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id VAA23236 for freebsd-current@FreeBSD.ORG; Fri, 20 Sep 1996 21:29:03 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.4/keltia-uucp-2.9) id VAA22149; Fri, 20 Sep 1996 21:29:02 +0200 (MET DST) Message-Id: <199609201929.VAA22149@keltia.freenix.fr> Date: Fri, 20 Sep 1996 21:29:02 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.ORG (FreeBSD Current Users' list) Subject: libg++ X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I know libg++ will probably be committed soon now that gcc 2.7.2.1 is in but will the old libg++ compile ? -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-current Fri Sep 20 12:31:37 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA04840 for current-outgoing; Fri, 20 Sep 1996 12:31:37 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.177]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id MAA04740; Fri, 20 Sep 1996 12:31:28 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id VAA14632; Fri, 20 Sep 1996 21:28:22 +0200 (MET DST) To: roberto@keltia.freenix.fr (Ollivier Robert) cc: freebsd-current@freebsd.org (FreeBSD Current Users' list) Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly In-reply-to: Your message of "Fri, 20 Sep 1996 21:12:30 +0200." <199609201912.VAA21273@keltia.freenix.fr> Date: Fri, 20 Sep 1996 21:28:21 +0200 Message-ID: <14630.843247701@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199609201912.VAA21273@keltia.freenix.fr>, Ollivier Robert writes: >According to Mark Murray: >> I think the problem may be your side. It worked just fine for me >> on a 2.2-CURRENT and a 2.1.5-RELEASE machine. I am currnetly at >> ctm cvs-cur.2489 on one machine and cvs-cur.2490 on the other. > > >I'm not imagining things. Both contains the _same_ bad checksums... it's an cvs administrative file, you have a locally modified version... -- 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 Sep 20 13:42:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA11483 for current-outgoing; Fri, 20 Sep 1996 13:42:27 -0700 (PDT) Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA11433 for ; Fri, 20 Sep 1996 13:42:20 -0700 (PDT) Received: from uc.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA06896; Fri, 20 Sep 96 15:41:46 -0500 Received: from fergus-27.dialup.prtel.com by uc.msc.edu (5.65/MSC/v3.0z(901212)) id AA27254; Fri, 20 Sep 96 15:41:43 -0500 Received: (from alk@localhost) by compound.Think.COM (8.7.6/8.7.3) id PAA07619; Fri, 20 Sep 1996 15:41:53 -0500 (CDT) Date: Fri, 20 Sep 1996 15:41:53 -0500 (CDT) From: Tony Kimball Message-Id: <199609202041.PAA07619@compound.Think.COM> To: chuckr@glue.umd.edu Cc: current@freebsd.org Subject: Re: gnu/usr.bin/cc not building References: <199609201823.NAA16230@compound.Think.COM> Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoth Chuck Robey on Fri, 20 September: : > ctm cvs-cur 2490: : > struct resword is undefined (first referenced in c-lex.c) : : Think you might double check your sources, it built fine for me, as soon : as i got all of Nate's ts_sec->tv_sec fixes. None of them were in cc. Explanation found, but it raises a question: I made world OK otherwise, but cc would not build for me, so I did a cc -E on c-lex.c: # 1 "/usr/obj/alt/src/gnu/usr.bin/cc/cc1/../cc_tools/c-gperf.h" 1 # 99 "/alt/src/gnu/usr.bin/cc/cc1/../../../../contrib/gcc/c-lex.c" 2 c-gperf.h was empty? Something must've interrupted the generation of that file. It is generated using a shell stdout redirect: ===> cc_tools gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ \ /alt/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf \ > c-gperf.h Should the ${.TARGET} file, c-gperf.h, not have been removed automatically, if gperf returned non-zero status due to an interrupt? From owner-freebsd-current Fri Sep 20 13:50:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA14722 for current-outgoing; Fri, 20 Sep 1996 13:50:14 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA14683 for ; Fri, 20 Sep 1996 13:50:08 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id OAA03644; Fri, 20 Sep 1996 14:49:33 -0600 (MDT) Message-Id: <199609202049.OAA03644@rover.village.org> To: John Hay Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly Cc: roberto@keltia.freenix.fr (Ollivier Robert), freebsd-current@FreeBSD.org In-reply-to: Your message of "Sat, 20 Sep 1996 20:59:45 +0200." <199609201859.UAA15404@zibbi.mikom.csir.co.za> References: <199609201859.UAA15404@zibbi.mikom.csir.co.za> Date: Fri, 20 Sep 1996 14:49:33 -0600 From: Warner Losh Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <199609201859.UAA15404@zibbi.mikom.csir.co.za> John Hay writes: : That is strange. I have three machines that has gone past that up to : #2490 with no problems. Ditto. Maybe the problem is at your end? Warner From owner-freebsd-current Fri Sep 20 15:01:15 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA19884 for current-outgoing; Fri, 20 Sep 1996 15:01:15 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.eu.org [193.56.58.253]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA19831 for ; Fri, 20 Sep 1996 15:01:08 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.eu.org [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id AAA11968 for ; Sat, 21 Sep 1996 00:01:01 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id AAA24755 for freebsd-current@FreeBSD.org; Sat, 21 Sep 1996 00:00:51 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.Beta.4/keltia-uucp-2.9) id XAA09365; Fri, 20 Sep 1996 23:39:56 +0200 (MET DST) Message-Id: <199609202139.XAA09365@keltia.freenix.fr> Date: Fri, 20 Sep 1996 23:39:54 +0200 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-current@FreeBSD.org Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly In-Reply-To: <199609202049.OAA03644@rover.village.org>; from Warner Losh on Sep 20, 1996 14:49:33 -0600 References: <199609202049.OAA03644@rover.village.org> <199609201859.UAA15404@zibbi.mikom.csir.co.za> X-Mailer: Mutt 0.43g Mime-Version: 1.0 X-Operating-System: FreeBSD 2.2-CURRENT ctm#2443 Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Warner Losh: > Ditto. Maybe the problem is at your end? Thanks to Poul-Henning, I now know that val-tags is a file generated by cvs itself so its content/MD5 may vary... Why me ? :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 2.2-CURRENT #21: Sun Sep 8 14:35:00 MET DST 1996 From owner-freebsd-current Fri Sep 20 18:06:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA26354 for current-outgoing; Fri, 20 Sep 1996 18:06:33 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA26272; Fri, 20 Sep 1996 18:06:26 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id SAA25861; Fri, 20 Sep 1996 18:06:21 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id SAA19669; Fri, 20 Sep 1996 18:01:52 -0700 (PDT) Message-Id: <199609210101.SAA19669@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: asami@freebsd.org (Satoshi Asami) cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Streamlogic RAID array benchmarks In-reply-to: Your message of Fri, 20 Sep 96 12:24:09 -0700. <199609201924.MAA14507@sunrise.cs.berkeley.edu> Date: Fri, 20 Sep 1996 18:01:51 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> -------Sequential Output-------- ---Sequential Input-- --Random-- >> -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- >>Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU >>raid 100 1354 25.1 1308 4.5 1056 7.3 3059 55.9 3190 11.5 139.0 5.1 >>single 100 3506 66.8 3429 12.0 1848 12.5 5367 99.1 6462 25.6 202.5 7.1 >Just FYI, we've seen close to 30MB/s with ccd (no mirroring). You >need two 2940?W's (or one 3940?W) and at least four disks though. Just for our edification, what kind of CPU did you use? Also For Everyones' Information, you won't get close to that on a real filesystem unless you use a Pentium or better. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Fri Sep 20 18:44:25 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA20856 for current-outgoing; Fri, 20 Sep 1996 18:44:25 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA20765; Fri, 20 Sep 1996 18:44:16 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.6/8.6.9) id SAA13100; Fri, 20 Sep 1996 18:43:44 -0700 (PDT) Date: Fri, 20 Sep 1996 18:43:44 -0700 (PDT) Message-Id: <199609210143.SAA13100@silvia.HIP.Berkeley.EDU> To: michaelv@MindBender.serv.net CC: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org In-reply-to: <199609210101.SAA19669@MindBender.serv.net> (michaelv@MindBender.serv.net) Subject: Re: Streamlogic RAID array benchmarks From: asami@freebsd.org (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * >Just FYI, we've seen close to 30MB/s with ccd (no mirroring). You * >need two 2940?W's (or one 3940?W) and at least four disks though. * * Just for our edification, what kind of CPU did you use? * * Also For Everyones' Information, you won't get close to that on a real * filesystem unless you use a Pentium or better. Yeah, it's a P5 (133MHz). We got pretty much the same result with the P6 (200MHz) too (which is kinda surprising, given that their memory system is so much slower). Satoshi P.S. http://now.cs.berkeley.edu/Td/bcopy.html for more on the memory thing. From owner-freebsd-current Fri Sep 20 19:41:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA19411 for current-outgoing; Fri, 20 Sep 1996 19:41:54 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA19358 for ; Fri, 20 Sep 1996 19:41:45 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id MAA04692; Sat, 21 Sep 1996 12:32:15 +1000 Date: Sat, 21 Sep 1996 12:32:15 +1000 From: Bruce Evans Message-Id: <199609210232.MAA04692@godzilla.zeta.org.au> To: alk@Think.COM, chuckr@glue.umd.edu Subject: Re: gnu/usr.bin/cc not building Cc: current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >===> cc_tools >gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ \ > /alt/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf \ > > c-gperf.h > >Should the ${.TARGET} file, c-gperf.h, not have been removed >automatically, if gperf returned non-zero status due to an interrupt? Targets are removed automatically if the command to build them is killed, but not if it exits with a nonzero status. Thus make always does the wrong thing for failed targets that are created by simple shell command :-(. This seems to be standard - gmake does the same. Bruce From owner-freebsd-current Fri Sep 20 20:58:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA25908 for current-outgoing; Fri, 20 Sep 1996 20:58:54 -0700 (PDT) Received: from orion.webspan.net (root@orion.webspan.net [206.154.70.41]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA25869 for ; Fri, 20 Sep 1996 20:58:48 -0700 (PDT) Received: from localhost (gpalmer@localhost [127.0.0.1]) by orion.webspan.net (8.7.5/8.6.12) with SMTP id XAA01141; Fri, 20 Sep 1996 23:57:01 -0400 (EDT) X-Authentication-Warning: orion.webspan.net: Host gpalmer@localhost [127.0.0.1] didn't use HELO protocol To: roberto@keltia.freenix.fr (Ollivier Robert) cc: freebsd-current@FreeBSD.org (FreeBSD Current Users' list) From: "Gary Palmer" Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly In-reply-to: Your message of "Fri, 20 Sep 1996 20:31:37 +0200." <199609201831.UAA20880@keltia.freenix.fr> Date: Fri, 20 Sep 1996 23:57:01 -0400 Message-ID: <1138.843278221@orion.webspan.net> Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Ollivier Robert wrote in message ID <199609201831.UAA20880@keltia.freenix.fr>: > CTM delta from cvs-cur #2486 doesn't apply cleanly because of a MD5 > mismatch on CVSROOT/val-tags. I checked freefall's val-tags and after > applying the diff manually I get the same checksum. > > I think something goofed up during the CTM generation. FYI. cvs-cur up to and include 2492 have applied here... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Fri Sep 20 21:11:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA01687 for current-outgoing; Fri, 20 Sep 1996 21:11:58 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA01616; Fri, 20 Sep 1996 21:11:47 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id VAA29382; Fri, 20 Sep 1996 21:11:53 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id VAA20862; Fri, 20 Sep 1996 21:11:37 -0700 (PDT) Message-Id: <199609210411.VAA20862@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: asami@freebsd.org (Satoshi Asami) cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org Subject: Re: Streamlogic RAID array benchmarks In-reply-to: Your message of Fri, 20 Sep 96 18:43:44 -0700. <199609210143.SAA13100@silvia.HIP.Berkeley.EDU> Date: Fri, 20 Sep 1996 21:11:37 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * >Just FYI, we've seen close to 30MB/s with ccd (no mirroring). You > * >need two 2940?W's (or one 3940?W) and at least four disks though. > * > * Just for our edification, what kind of CPU did you use? > * > * Also For Everyones' Information, you won't get close to that on a real > * filesystem unless you use a Pentium or better. >Yeah, it's a P5 (133MHz). We got pretty much the same result with the >P6 (200MHz) too (which is kinda surprising, given that their memory >system is so much slower). How is that surprising? The SCSI controller lives on the other side of the bus, and does the bus-mastering irrespective of the CPU. The CPU does not do bcopies for bus-mastering SCSI transfers. The problems with the 486 is that its slowness causes too great a latency between when work becomes available, and when it has something ready to keep the disk subsystem working, causing less than 100% efficiency. If all have a (working) PCI bus, what happens on the SCSI controller side should not be affected by the CPU, except for how busy the CPU can keep the SCSI controller. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-current Fri Sep 20 21:30:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA09142 for current-outgoing; Fri, 20 Sep 1996 21:30:33 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA09059; Fri, 20 Sep 1996 21:30:21 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.7.6/8.6.9) id VAA14425; Fri, 20 Sep 1996 21:29:42 -0700 (PDT) Date: Fri, 20 Sep 1996 21:29:42 -0700 (PDT) Message-Id: <199609210429.VAA14425@silvia.HIP.Berkeley.EDU> To: michaelv@MindBender.serv.net CC: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org, freebsd-isp@freebsd.org In-reply-to: <199609210411.VAA20862@MindBender.serv.net> (michaelv@MindBender.serv.net) Subject: Re: Streamlogic RAID array benchmarks From: asami@freebsd.org (Satoshi Asami) Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * >Yeah, it's a P5 (133MHz). We got pretty much the same result with the * >P6 (200MHz) too (which is kinda surprising, given that their memory * >system is so much slower). * * How is that surprising? The SCSI controller lives on the other side * of the bus, and does the bus-mastering irrespective of the CPU. The * CPU does not do bcopies for bus-mastering SCSI transfers. It does, because this is a bufferred I/O. We were measuring this through the filesystem, remember? An interesting sidenote of this is that when we were using the same P5-133 with the regular (rep/movsl) copyin/copyout, we got only about 20MB/s. We changed it to the Pentium-optimized copy, and managed to push it up close to 30MB/s. The slow bcopy can move about 40MB/s, the fast one 80MB/s. However, the P6-200, despite its 45MB/s bcopy speed, gives us the same 30MB/s through the filesystem. (For those you like math, 45MB/s is 22.2ns/byte, and 30MB/s is 33.3ns/B, and given that the max transfer rate on of 33MHz PCI is 132MB/s, or 7.5 ns/B, this is really close to the limit (22.2 + 7.5 = 29.7 =~ 33.3)....) Satoshi P.S. Doing parallel reads from raw devices, I could get about 65MB/s on the P5...haven't tried that on the P6. From owner-freebsd-current Fri Sep 20 22:38:33 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA14492 for current-outgoing; Fri, 20 Sep 1996 22:38:33 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA14437 for ; Fri, 20 Sep 1996 22:38:28 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id PAA08542; Sat, 21 Sep 1996 15:29:17 +1000 Date: Sat, 21 Sep 1996 15:29:17 +1000 From: Bruce Evans Message-Id: <199609210529.PAA08542@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.org, roberto@keltia.freenix.fr Subject: Re: CTM cvs-cur #2486.gz doesn't apply cleanly Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >According to Mark Murray: >> I think the problem may be your side. It worked just fine for me >> on a 2.2-CURRENT and a 2.1.5-RELEASE machine. I am currnetly at >> ctm cvs-cur.2489 on one machine and cvs-cur.2490 on the other. > >John Hay just told me the same thing. I've had to edit the ctm update to fix val-tags >= 3 times now. The latest was for #248x. Apparently some local operation changes it (although I never change tags locally) and then the next ctm update that changes it fails. Bruce From owner-freebsd-current Sat Sep 21 03:40:46 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA01808 for current-outgoing; Sat, 21 Sep 1996 03:40:46 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id DAA01773 for ; Sat, 21 Sep 1996 03:40:36 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.7.6/8.7.3) id MAA23552 for current@freebsd.org; Sat, 21 Sep 1996 12:40:33 +0200 (SAT) From: John Hay Message-Id: <199609211040.MAA23552@zibbi.mikom.csir.co.za> Subject: Some shared library problems To: current@freebsd.org Date: Sat, 21 Sep 1996 12:40:33 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL24 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I picked these up while trying to build a -CURRENT SNAP release on a 2.1.5 machine. Now I do understand that it might be considered cheating a little, but it is the only PPro 200MHz that we have here and it must run 2.1.5. I thought that because the make release fase will do a make world in the chrooted area the end result should be an -current snap. :-) The first problem I ran into was the libgnumalloc that gets removed and then reappear as a link to libfakegnumalloc in ${CHROOTDIR}/usr/lib/compat. Maybe there should be a "ldconfig -m /usr/lib/compat" after such a drastic step? I think I can get past this by setting the LD_LIBRARY_PATH envirenment variable. This one does not bother me too much, although I would like a solution to this. The one that I think might bite us somewhere is libgnuregex.so.2.0 that now (in -current) have locale stuff in that needs libc.so.3.0 while the libgnuregex.so.2.0 in 2.1.5 did not have it. The result of this is that a program compiled with libgnuregex.so.2.0 and libc.so.2.x won't run with the new libgnuregex.so.2.0 installed. Where I noticed it was when awk was used during the compilation of usr.bin/kdump. Maybe the major version number of a library should be bumped if it starts to depend on another library? I think this counts as a major interface change. Any ideas anybody? Maybe I should also just say that I do have another machine that runs current and I can probably get by these things manually. It just seem that the latest "make world" target with its inclusion of the bootstrap target is so close to be able to really take you from 2.1.5 to current. John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Sat Sep 21 04:00:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA06858 for current-outgoing; Sat, 21 Sep 1996 04:00:12 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id DAA06480 for ; Sat, 21 Sep 1996 03:58:43 -0700 (PDT) Received: from apocalypse.tky.hut.fi by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0v4Plh-0008vjC; Sat, 21 Sep 96 03:58 PDT Received: (from apl@localhost) by apocalypse.tky.hut.fi (8.7.6/8.7.3) id NAA27875; Sat, 21 Sep 1996 13:55:25 +0300 (EET DST) Date: Sat, 21 Sep 1996 13:55:25 +0300 (EET DST) From: Antti-Pekka Liedes To: current@freebsd.org Subject: gcc 2.7.2.1 of -current does not work with objective-C Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The gcc 2.7.2.1 shipped with current (960920) doesn't compile objective-C correctly. All programs fail with floating point exception, even if there are no floating point operations. Here's a related news article: ------ snip ------ >From nntp.hut.fi!news.csc.fi!news.eunet.fi!EU.net!usenet1.news.uk.psi.net!uknet!tank.news.pipex.net!pipex!newsfeed.internetmci.com!news.mathworks.com!uunet!in2.uu.net!news.voicenet.com!news2.noc.netcom.net!noc.netcom.net!ixnews1.ix.netcom.com!netcom.com!j lemon Wed May 29 19:26:48 1996 Newsgroups: comp.lang.objective-c Path: nntp.hut.fi!news.csc.fi!news.eunet.fi!EU.net!usenet1.news.uk.psi.net!uknet!tank.news.pipex.net!pipex!newsfeed.internetmci.com!news.mathworks.com!uunet!in2.uu.net!news.voicenet.com!news2.noc.netcom.net!noc.netcom.net!ixnews1.ix.netcom.com!netcom.com! jlemon From: jlemon@netcom.com (Jonathan Lemon) Subject: Re: FPE with gcc 2.7.2 on FreeBSD Message-ID: Organization: NETCOM On-line Communication Services (408 261-4700 guest) References: <4o7t8e$rob@nntp.hut.fi> Distribution: inet Date: Tue, 28 May 1996 18:54:18 GMT Lines: 75 Sender: jlemon@netcom22.netcom.com In article <4o7t8e$rob@nntp.hut.fi>, Antti-Pekka Liedes wrote: > >Any ideas why objc runtime system causes FPE on FreeBSD? Gdb says it happens >on line 210 of sendmsg.c. It happens only with gcc 2.7.2, not with 2.6.3. >Both FreeBSD 2.1.0R and 2.2-SNAP-960501 cause the same FPE. The FAQ >mentioned similar problem on Linux, but said nothing about FreeBSD, are the >problems related? Yes - the problem is a bug in gcc 2.7.2, and probably occurrs on all x86 chips. My old posting is attached below. -- Jonathan >From jlemon@netcom.com Sat May 4 11:06:44 PDT 1996 Article: 5087 of comp.lang.objective-c Xref: netcom.com comp.lang.objective-c:5087 Newsgroups: comp.lang.objective-c Path: netcom.com!jlemon From: jlemon@netcom.com (Jonathan Lemon) Subject: ObjC runtime error - FIXED Message-ID: Cc: bug-gcc@prep.ai.mit.edu Organization: NETCOM On-line Communication Services (408 261-4700 guest) Date: Tue, 16 Apr 1996 19:38:38 GMT Lines: 44 Sender: jlemon@netcom22.netcom.com Earlier, I posted about getting SIGFPE on some working ObjC code that I had recompiled under the 2.7.2 compiler. Well, after learning more than I ever wanted to know about the internals of gcc, I managed to track down the problem - patch follows. In summary, when compiling __builtin_apply_args(), gcc turns this into a function call, and then somehow expects the call's return value to appear on the FP stack. When it then pops the stack to store the value in memory, an error condition is set. When the _next_ FP instruction comes along, a SIGFPE is generated. This was on a Sequent Symmetry v2.1.X (i486-based platform), but I imagine that this should fix the problem under linux as well. Does anyone know how to get this patch fed into the compiler distribution? I'm not a compiler expert, so I'm not sure if this is the optimal fix; but it does fix the problem that I was having. -- Jonathan =================================== cut here =================================== *** i386.md.orig Mon Aug 21 12:27:58 1995 --- i386.md Tue Apr 16 09:32:32 1996 *************** *** 5312,5321 **** --- 5312,5327 ---- coprocessor registers as containing a possible return value, simply pretend the untyped call returns a complex long double value. */ + #if 0 + /* this may be part of (set (reg: ..) (call_insn ...)), and we can't + directly set a fp register from the call. so we revert to the + old behavior */ emit_call_insn (TARGET_80387 ? gen_call_value (gen_rtx (REG, XCmode, FIRST_FLOAT_REG), operands[0], const0_rtx) : gen_call (operands[0], const0_rtx)); + #endif + emit_call_insn (gen_call (operands[0], const0_rtx, NULL, const0_rtx)); for (i = 0; i < XVECLEN (operands[2], 0); i++) { ------ snip ------ Applying this patch fixed the problem for me. Antti-Pekka Liedes * apl@IRC * In two hells, there's JMT 7 A 131 * apl@cs.hut.fi * one hell too many 02150 ESPOO * apl@apocalypse.tky.hut.fi * - Lucifer (in God's Army) From owner-freebsd-current Sat Sep 21 06:18:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA22761 for current-outgoing; Sat, 21 Sep 1996 06:18:51 -0700 (PDT) Received: from chain.iafrica.com (root@[196.7.74.174]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA22705 for ; Sat, 21 Sep 1996 06:18:46 -0700 (PDT) Received: from localhost (khetan@localhost [127.0.0.1]) by chain.iafrica.com (8.7.6/8.6.12) with SMTP id PAA00425 for ; Sat, 21 Sep 1996 15:18:24 +0200 (SAT) Date: Sat, 21 Sep 1996 15:18:23 +0200 (SAT) From: Khetan Gajjar Reply-To: Khetan Gajjar To: current@freebsd.org Subject: gnumalloc Message-ID: X-URL: http://www.iafrica.com/~khetan/ X-Alternate-Address: khetan@uunet.co.za X-Alternate-Address2: kg@iafrica.com X-Alternate-Address3: gjjkhe01@sonnenberg.uct.ac.za X-Alternate-Address4: khetan@chain.iafrica.com X-Comment: Telkom sucks huge! X-IRC-nick: chain MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi. I've just applied ctm delta's up to 2490, and made world. I noticed quite a few unreferenced pieces of code, etc, but that's not the problem. I noticed that after the build, the system kept complaining because it couldn't find libgnumalloc.so.2.0 I did notice there was a libfakegnumalloc.so.2.0, so just symlinked it to libgnumalloc.so.2.0 and there it was. Am I doing something wrong here ? I didn't notice anything in -current or cvs-all for the last few days about this. Sorry if this is a "newbie" query. TIA, --- Khetan Gajjar [ http://www.iafrica.com/~khetan] I'm a FreeBSD User! [ http://www.freebsd.org] UUNet Internet Africa [0800-030-002 & help@iafrica.com] From owner-freebsd-current Sat Sep 21 06:19:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA22884 for current-outgoing; Sat, 21 Sep 1996 06:19:03 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA22826 for ; Sat, 21 Sep 1996 06:18:57 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id XAA18586; Sat, 21 Sep 1996 23:17:31 +1000 Date: Sat, 21 Sep 1996 23:17:31 +1000 From: Bruce Evans Message-Id: <199609211317.XAA18586@godzilla.zeta.org.au> To: current@FreeBSD.org, jhay@mikom.csir.co.za Subject: Re: Some shared library problems Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >The first problem I ran into was the libgnumalloc that gets removed and >then reappear as a link to libfakegnumalloc in ${CHROOTDIR}/usr/lib/compat. >Maybe there should be a "ldconfig -m /usr/lib/compat" after such a drastic >step? I think I can get past this by setting the LD_LIBRARY_PATH envirenment >variable. This one does not bother me too much, although I would like a >solution to this. The ldconfig might help for installs into "/" under -current, but there should bes no problem for a separate rootdir. The installation of libfakegnumalloc is currently broken (it deletes all versions of libgnumalloc.so from ${SHLIBDIR}). I think it is supposed to work by leaving old versions alone and putting a guaranteed-newer version in the compat directory for future ld commands to find. It would be cleaner but too hard to mv old versions of libgnumalloc.so to the compar directory. >The one that I think might bite us somewhere is libgnuregex.so.2.0 that >now (in -current) have locale stuff in that needs libc.so.3.0 while >the libgnuregex.so.2.0 in 2.1.5 did not have it. The result of this is >that a program compiled with libgnuregex.so.2.0 and libc.so.2.x won't >run with the new libgnuregex.so.2.0 installed. Where I noticed it was >when awk was used during the compilation of usr.bin/kdump. Maybe the >major version number of a library should be bumped if it starts to >depend on another library? I think this counts as a major interface >change. Some libraries are linked to others (e.g., libg++ is linked to many others), so normal version numbering stuff should apply. Unfortunately, nothing is explicitly linked to libc, because libc is always there. Your example shows that the required version of libc isn't always there. Would always linking libraries to libc be reasonable? What is the equivalent to ldd for libraries? Bruce From owner-freebsd-current Sat Sep 21 06:47:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA08440 for current-outgoing; Sat, 21 Sep 1996 06:47:54 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id GAA08392 for ; Sat, 21 Sep 1996 06:47:49 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id PAA28968 for ; Sat, 21 Sep 1996 15:47:13 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id PAA22293 for freebsd-current@freefall.cdrom.com; Sat, 21 Sep 1996 15:54:02 +0200 Date: Sat, 21 Sep 1996 15:54:02 +0200 From: Christoph Kukulies Message-Id: <199609211354.PAA22293@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.FreeBSD.org Subject: ncr - added a scanner and now this: Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I added a Mustek Paragon 600 II SP scanner to my SCSI bus. This is dmesg: FreeBSD 2.2-CURRENT #5: Sun Sep 1 17:04:15 MET DST 1996 root@isdn-kukulies.dialup.rwth-aachen.de:/usr/src/sys/compile/MONKBISDN Calibrating clock(s) relative to mc146818A clock... i8254 clock: 1205100 Hz CPU: AMD Am5x86 Write-Through (486-class CPU) Origin = "AuthenticAMD" Id = 0x4e4 real memory = 67108864 (65536K bytes) avail memory = 62734336 (61264K bytes) Probing for devices on PCI bus 0: chip0 rev 4 on pci0:0 ncr0 rev 1 int a irq 9 on pci0:1 ncr0 waiting for scsi devices to settle (ncr0:0:0): "QUANTUM FIREBALL1080S 1Q09" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1042MB (2134305 512 byte sectors) (ncr0:1:0): "QUANTUM MAVERICK 540S 0901" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 516MB (1057758 512 byte sectors) (ncr0:6:0): "SCANNER 2.01" type 6 fixed SCSI 1 uk0(ncr0:6:0): Unknown (ncr0:6:1): "SCANNER 2.01" type 6 fixed SCSI 1 uk1(ncr0:6:1): Unknown (ncr0:6:2): "SCANNER 2.01" type 6 fixed SCSI 1 uk2(ncr0:6:2): Unknown (ncr0:6:3): "SCANNER 2.01" type 6 fixed SCSI 1 uk3(ncr0:6:3): Unknown (ncr0:6:4): "SCANNER 2.01" type 6 fixed SCSI 1 uk4(ncr0:6:4): Unknown (ncr0:6:5): "SCANNER 2.01" type 6 fixed SCSI 1 uk5(ncr0:6:5): Unknown (ncr0:6:6): "SCANNER 2.01" type 6 fixed SCSI 1 uk6(ncr0:6:6): Unknown (ncr0:6:7): "SCANNER 2.01" type 6 fixed SCSI 1 uk7(ncr0:6:7): Unknown chip1 rev 3 on pci0:2 vga0 rev 0 on pci0:4 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 5 maddr 0xd0000 msize 8192 on isa ed0: address 00:00:e8:80:79:9c, type WD8003E (8 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A qcam0 at 0x378 on isa qcam0: unidirectional parallel port lpt1 at 0x378-0x37f irq 7 on isa lpt1 not probed due to I/O address conflict with qcam0 at 0x378 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 tel0 at 0xd80 irq 15 on isa tel0: card type Teles S0/16.3 npx0 on motherboard npx0: INT 16 interface gus0 at 0x220 irq 12 drq 1 flags 0x3 on isa at 0x220 irq 12 dma 1,3 changing root device to sd0a WARNING: / was not properly dismounted. ncr0:0: ERROR (80:98) (1-21-83) (8/13) @ (dfc:190002cb). script cmd = 89030000 reg: da 10 80 13 47 08 00 1f 03 01 80 21 80 00 81 00. ncr0: have to clear fifos. ncr0: restart (fatal error). sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f1778e00. ncr0: restart (ncr dead ?). spec_getpages: I/O read error vm_fault: pager input (probably hardware) error, PID 164 failure sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 sd0(ncr0:0:0): Power on, reset, or bus device reset occurred , retries:4 pid 164 (tcsh), uid 0: exited on signal 11 (core dumped) System is a bit flaky since then. I got this ncr bus device reset already twice since last reboot and I'm hurrying up typing to get this message finished before the next occurance and eventual system freeze. Any clues? Also why this probing of logical devices ? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Sat Sep 21 09:22:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA12997 for current-outgoing; Sat, 21 Sep 1996 09:22:36 -0700 (PDT) Received: from freefall.freebsd.org (localhost.cdrom.com [127.0.0.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA12966; Sat, 21 Sep 1996 09:22:31 -0700 (PDT) Message-Id: <199609211622.JAA12966@freefall.freebsd.org> To: Christoph Kukulies cc: freebsd-current@freefall.freebsd.org Subject: Re: ncr - added a scanner and now this: In-reply-to: Your message of "Sat, 21 Sep 1996 15:54:02 +0200." <199609211354.PAA22293@gilberto.physik.rwth-aachen.de> Date: Sat, 21 Sep 1996 09:22:31 -0700 From: "Justin T. Gibbs" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >I added a Mustek Paragon 600 II SP scanner to my SCSI bus. >This is dmesg: > I don't know why we're attempting multiple luns to this target... it must be matching a quirk, but I bet you can shut it up by adding code similar to this in scsi_scsi_cmd: /* * If we are dealing with a SCSI II or prior device, * set the lun in the CDB. Since inqbuf is * initialized to zero during the initial probe * of a device, we always add this information * when looking for new devices. */ if ((sc_link->inqbuf.version & SID_ANSII) <= 2) { xs->cmdstore.bytes[1] = sc_link->lun << SCSI_CMD_LUN_SHIFT; } This has already been added on the 'SCSI' branch. >(ncr0:6:0): "SCANNER 2.01" type 6 fixed SCSI 1 >uk0(ncr0:6:0): Unknown >(ncr0:6:1): "SCANNER 2.01" type 6 fixed SCSI 1 >uk1(ncr0:6:1): Unknown >(ncr0:6:2): "SCANNER 2.01" type 6 fixed SCSI 1 >uk2(ncr0:6:2): Unknown >(ncr0:6:3): "SCANNER 2.01" type 6 fixed SCSI 1 >uk3(ncr0:6:3): Unknown >(ncr0:6:4): "SCANNER 2.01" type 6 fixed SCSI 1 >uk4(ncr0:6:4): Unknown >(ncr0:6:5): "SCANNER 2.01" type 6 fixed SCSI 1 >uk5(ncr0:6:5): Unknown >(ncr0:6:6): "SCANNER 2.01" type 6 fixed SCSI 1 >uk6(ncr0:6:6): Unknown >(ncr0:6:7): "SCANNER 2.01" type 6 fixed SCSI 1 > Stefan will have to help you with the NCR stuff. >changing root device to sd0a >WARNING: / was not properly dismounted. >ncr0:0: ERROR (80:98) (1-21-83) (8/13) @ (dfc:190002cb). > script cmd = 89030000 > reg: da 10 80 13 47 08 00 1f 03 01 80 21 80 00 81 00. >ncr0: have to clear fifos. >ncr0: restart (fatal error). >sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f1778e00. >ncr0: restart (ncr dead ?). >spec_getpages: I/O read error >vm_fault: pager input (probably hardware) error, PID 164 failure >sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. >sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 >sd0(ncr0:0:0): Power on, reset, or bus device reset occurred >, retries:4 >pid 164 (tcsh), uid 0: exited on signal 11 (core dumped) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-current Sat Sep 21 09:55:27 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA02908 for current-outgoing; Sat, 21 Sep 1996 09:55:27 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA02827; Sat, 21 Sep 1996 09:55:17 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id SAA01321; Sat, 21 Sep 1996 18:55:25 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id TAA22826; Sat, 21 Sep 1996 19:02:13 +0200 From: Christoph Kukulies Message-Id: <199609211702.TAA22826@gilberto.physik.rwth-aachen.de> Subject: Re: ncr - added a scanner and now this: In-Reply-To: <199609211622.JAA12966@freefall.freebsd.org> from "Justin T. Gibbs" at "Sep 21, 96 09:22:31 am" To: gibbs@freefall.freebsd.org (Justin T. Gibbs) Date: Sat, 21 Sep 1996 19:02:12 +0200 (MET DST) Cc: kuku@gilberto.physik.rwth-aachen.de, freebsd-current@freefall.freebsd.org Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > >I added a Mustek Paragon 600 II SP scanner to my SCSI bus. > >This is dmesg: > > > > I don't know why we're attempting multiple luns to this target... > it must be matching a quirk, but I bet you can shut it up by > adding code similar to this in scsi_scsi_cmd: > > /* > * If we are dealing with a SCSI II or prior device, > * set the lun in the CDB. Since inqbuf is > * initialized to zero during the initial probe > * of a device, we always add this information > * when looking for new devices. > */ > if ((sc_link->inqbuf.version & SID_ANSII) <= 2) { > xs->cmdstore.bytes[1] = > sc_link->lun << SCSI_CMD_LUN_SHIFT; > } > > This has already been added on the 'SCSI' branch. > > >(ncr0:6:0): "SCANNER 2.01" type 6 fixed SCSI 1 > >uk0(ncr0:6:0): Unknown > >(ncr0:6:1): "SCANNER 2.01" type 6 fixed SCSI 1 > >uk1(ncr0:6:1): Unknown > >(ncr0:6:2): "SCANNER 2.01" type 6 fixed SCSI 1 > >uk2(ncr0:6:2): Unknown > >(ncr0:6:3): "SCANNER 2.01" type 6 fixed SCSI 1 > >uk3(ncr0:6:3): Unknown > >(ncr0:6:4): "SCANNER 2.01" type 6 fixed SCSI 1 > >uk4(ncr0:6:4): Unknown > >(ncr0:6:5): "SCANNER 2.01" type 6 fixed SCSI 1 > >uk5(ncr0:6:5): Unknown > >(ncr0:6:6): "SCANNER 2.01" type 6 fixed SCSI 1 > >uk6(ncr0:6:6): Unknown > >(ncr0:6:7): "SCANNER 2.01" type 6 fixed SCSI 1 > > > > Stefan will have to help you with the NCR stuff. I'm sure he will :-) but before you jump in, Stefan, note that there might have been a missing terminator :-x. So discard the ncr issue until the problem really manifests. > > >changing root device to sd0a > >WARNING: / was not properly dismounted. > >ncr0:0: ERROR (80:98) (1-21-83) (8/13) @ (dfc:190002cb). > > script cmd = 89030000 > > reg: da 10 80 13 47 08 00 1f 03 01 80 21 80 00 81 00. > >ncr0: have to clear fifos. > >ncr0: restart (fatal error). > >sd0(ncr0:0:0): COMMAND FAILED (9 ff) @f1778e00. > >ncr0: restart (ncr dead ?). > >spec_getpages: I/O read error > >vm_fault: pager input (probably hardware) error, PID 164 failure > >sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > >sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 > >sd0(ncr0:0:0): Power on, reset, or bus device reset occurred > >, retries:4 > >pid 164 (tcsh), uid 0: exited on signal 11 (core dumped) > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-current Sat Sep 21 10:06:24 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA08598 for current-outgoing; Sat, 21 Sep 1996 10:06:24 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA08575 for ; Sat, 21 Sep 1996 10:06:22 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.6/8.6.9) with ESMTP id KAA09605; Sat, 21 Sep 1996 10:06:12 -0700 (PDT) To: Christoph Kukulies cc: freebsd-current@freefall.freebsd.org Subject: Re: ncr - added a scanner and now this: In-reply-to: Your message of "Sat, 21 Sep 1996 15:54:02 +0200." <199609211354.PAA22293@gilberto.physik.rwth-aachen.de> Date: Sat, 21 Sep 1996 10:06:11 -0700 Message-ID: <9603.843325571@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I added a Mustek Paragon 600 II SP scanner to my SCSI bus. > This is dmesg: I assume you also terminated it? These scanners are somewhat screwy as they give you a Mac-style SCSI interface and a SCSI-II interface and that's it, meaning that if you use the SCSI-II interface then you've got to find a terminator for other connector. Since those are somewhat hard to find, the other alternative is to get a Mac-to-SCSI-II cable and terminate the SCSI-II connector. Have you done either here? Jordan From owner-freebsd-current Sat Sep 21 20:02:54 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA09316 for current-outgoing; Sat, 21 Sep 1996 20:02:54 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA08161 for ; Sat, 21 Sep 1996 20:00:35 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id VAA18828 for ; Sat, 21 Sep 1996 21:00:24 -0600 (MDT) Message-Id: <199609220300.VAA18828@rover.village.org> To: current@freebsd.org Subject: libgnumalloc Date: Sat, 21 Sep 1996 21:00:23 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk WARNING: make world incorrectly and bogusly removes /usr/lib/libgnumalloc* and /usr/lib/compat/libgnumalloc*. I know that it is being phased out, but that is no reason to kill the shared library on an installed system. I have dozens of the goofy binaries, many that are "hard" to regenerate that reference this. Anyway, the source of this "problem" are the following lines in /usr/src/lib/libfakegnumalloc/Makefile: rm -f ${DESTDIR}${LIBDIR}/libgnumalloc* rm -f ${DESTDIR}${SHLIBDIR}/libgnumalloc* I don't think that you really want to have the * on the end, but rather be more explicit about it? What if I had a libgnumalloc.so.1.0 that I needed for something, it is gone now, had that been the case. Also of note: Since I've not installed /etc/rc in a long time, I didn't have /usr/lib/compat in my ldconfig cache. Others coming accross this trail may also have to update as well. Warner From owner-freebsd-current Sat Sep 21 23:12:03 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA27973 for current-outgoing; Sat, 21 Sep 1996 23:12:03 -0700 (PDT) Received: from sovcom.kiae.su (sovcom.kiae.su [193.125.152.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id XAA27921; Sat, 21 Sep 1996 23:11:59 -0700 (PDT) Received: by sovcom.kiae.su id AA17928 (5.65.kiae-1 ); Sun, 22 Sep 1996 08:57:28 +0300 Received: by sovcom.KIAE.su (UUMAIL/2.0); Sun, 22 Sep 96 08:57:28 +0300 Received: (from ache@localhost) by nagual.ru (8.7.6/8.7.3) id JAA00328; Sun, 22 Sep 1996 09:47:11 +0400 (MSD) Message-Id: <199609220547.JAA00328@nagual.ru> Subject: Default mousepointer position To: sos@freebsd.org (Soren Schmidt) Date: Sun, 22 Sep 1996 09:47:10 +0400 (MSD) Cc: current@freebsd.org (FreeBSD-current) From: =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (Andrey A. Chernov) Organization: self X-Class: Fast X-Mailer: ELM [version 2.4ME+ PL26 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After login, mousepointer appearse at 0,0 Since mouse not actively used, it can stay much time there, maybe forever. The disadvantage of it is that recognition of the character at 0,0 becomes much harder, so I forced to move mouse off without mouse-related reason or look from closer position. I have suggestion to change default mousepointer location to 80,25 instead (lastX-charWidth,lastY-charHeight in pixels). In _very_ rare cases any character appearse there. -- Andrey A. Chernov http://www.nagual.ru/~ache/ From owner-freebsd-current Sat Sep 21 23:13:12 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA28834 for current-outgoing; Sat, 21 Sep 1996 23:13:12 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA28804 for ; Sat, 21 Sep 1996 23:13:09 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.7.6/8.7.3) id IAA02247 for current@freebsd.org; Sun, 22 Sep 1996 08:13:07 +0200 (SAT) From: John Hay Message-Id: <199609220613.IAA02247@zibbi.mikom.csir.co.za> Subject: Ctm still running? To: current@freebsd.org Date: Sun, 22 Sep 1996 08:13:06 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL24 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Is Ctm still running? It has been almost 24 hours since I got the last cvs-cur update. I see there is a lock file /home/ctm/SW/LCK.cvs-cur on freefall. Can somebody have a look at it please? John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Sat Sep 21 23:46:51 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA21058 for current-outgoing; Sat, 21 Sep 1996 23:46:51 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA21028 for ; Sat, 21 Sep 1996 23:46:49 -0700 (PDT) Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.6/8.6.6) with ESMTP id AAA00334 for ; Sun, 22 Sep 1996 00:46:39 -0600 (MDT) Message-Id: <199609220646.AAA00334@rover.village.org> To: current@freebsd.org Subject: Upgrading rc files + CTM outage? Date: Sun, 22 Sep 1996 00:46:38 -0600 From: Warner Losh Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After fighting a little with the upgrade procedure, and finally taking the time to upgrade the rc files, I was wondering if there was a painless way to merge in the current /etc/sysconfig file one might have with the newer ones that defines more things. I recently had a problem with this, and it got me thinking. I can do it by hand, but I'd rather not :-). I fixed one bogon in /etc/rc that required swapfile to be defined, or you'd get a hard to track down syntax error on boot (I hope that is alright, I just put "" around a $swapfile to stop the syntax error). I think there is another bogon lurking with local_dirs, but I didn't fix that one. If not, is there any interest in something that would do this sort of thing? I'd write it if there wasn't already a updsysconfig command out there :-) It shouldn't be hard to generate from the new sysconfig, so long as comments needn't be preserved from the sysconfig file that was being upgraded.... Warner P.S. Has anybody else noticed that a) The new stuff about 11% longer to compile (10hr vs 9hr for me) and b) there have been no new CTMs in several hours (like maybe 20-25)?