From owner-freebsd-current Sun Nov 15 00:13:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04400 for freebsd-current-outgoing; Sun, 15 Nov 1998 00:13:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA04391 for ; Sun, 15 Nov 1998 00:13:07 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem27.masternet.it [194.184.65.37]) by www.giovannelli.it (8.8.8/8.8.5) with SMTP id JAA00903; Sun, 15 Nov 1998 09:12:11 +0100 (MET) Message-Id: <199811150812.JAA00903@www.giovannelli.it> From: "Gianmarco Giovannelli" To: "Jordan K. Hubbard" Date: Sun, 15 Nov 1998 09:20:00 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: hosts before bind in /etc/host.conf? Reply-to: gmarco@giovannelli.it CC: current@FreeBSD.ORG In-reply-to: <26948.911111774@zippy.cdrom.com> X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A lot of folks dive in and change this first thing since it's annoying > to have a non-connected host bring up a ppp connection just to resolve > your own hostname, and sysinstall is careful about putting entries > into /etc/hosts for this. Any objection to changing the default? For I am one of the "lot of folks" so I'll be very happy if you change the default... Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 00:34:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05299 for freebsd-current-outgoing; Sun, 15 Nov 1998 00:34:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05240; Sun, 15 Nov 1998 00:33:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA14297; Sun, 15 Nov 1998 09:31:52 +0100 (CET) To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? In-reply-to: Your message of "Sat, 14 Nov 1998 22:36:14 PST." <26948.911111774@zippy.cdrom.com> Date: Sun, 15 Nov 1998 09:31:52 +0100 Message-ID: <14295.911118712@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <26948.911111774@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >A lot of folks dive in and change this first thing since it's annoying >to have a non-connected host bring up a ppp connection just to resolve >your own hostname, and sysinstall is careful about putting entries >into /etc/hosts for this. Any objection to changing the default? Go for it. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 01:18:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA07632 for freebsd-current-outgoing; Sun, 15 Nov 1998 01:18:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA07627 for ; Sun, 15 Nov 1998 01:18:10 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id TAA07446 for ; Sun, 15 Nov 1998 19:47:45 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id TAA00462; Sun, 15 Nov 1998 19:47:42 +1030 (CST) Message-ID: <19981115194741.A414@freebie.lemis.com> Date: Sun, 15 Nov 1998 19:47:41 +1030 From: Greg Lehey To: FreeBSD current users Subject: Today's -CURRENT dies with "ffs_blkfree: bad size" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just upgraded my kernel to a sup of about 9 hours ago, and have had a number of panics. The first ones happened in X, but I finally got a dump. Here's a trace: #0 boot (howto=262400) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=262400) at ../../kern/kern_shutdown.c:285 #1 0xf013e1e5 in panic (fmt=0xf01cc3e1 "ffs_blkfree: bad size") at ../../kern/kern_shutdown.c:453 #2 0xf01cc53e in ffs_blkfree (ip=0xf1283400, bno=4, size=8192) at ../../ufs/ffs/ffs_alloc.c:1300 #3 0xf01cac04 in ffs_reallocblks (ap=0xf8cc1e14) at ../../ufs/ffs/ffs_alloc.c:523 #4 0xf015e2e3 in cluster_write (bp=0xf461a7e8, filesize=106496) at vnode_if.h:1035 #5 0xf01d2147 in ffs_write (ap=0xf8cc1eec) at ../../ufs/ufs/ufs_readwrite.c:368 #6 0xf0167d5b in vn_write (fp=0xf1233200, uio=0xf8cc1f30, cred=0xf11cac80) at vnode_if.h:331 #7 0xf0146da2 in write (p=0xf8cac880, uap=0xf8cc1f84) at ../../kern/sys_generic.c:270 #8 0xf01fcef3 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 114688, tf_esi = 537546280, tf_ebp = -272642672, tf_isp = -120840236, tf_ebx = 537477216, tf_edx = 537546280, tf_ecx = 0, tf_eax = 4, tf_trapno = 7, tf_err = 7, tf_eip = 537412177, tf_cs = 31, tf_eflags = 514, tf_esp = -272642696, tf_ss = 39}) at ../../i386/i386/trap.c:1031 #9 0x20084251 in ?? () Anybody else seen this? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 01:54:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09537 for freebsd-current-outgoing; Sun, 15 Nov 1998 01:54:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09532 for ; Sun, 15 Nov 1998 01:54:25 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id UAA03303; Sun, 15 Nov 1998 20:55:52 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811150955.UAA03303@cimlogic.com.au> Subject: Re: Today's -CURRENT dies with "ffs_blkfree: bad size" In-Reply-To: <19981115194741.A414@freebie.lemis.com> from Greg Lehey at "Nov 15, 98 07:47:41 pm" To: grog@lemis.com (Greg Lehey) Date: Sun, 15 Nov 1998 20:55:51 +1100 (EST) Cc: FreeBSD-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > I've just upgraded my kernel to a sup of about 9 hours ago, and have > had a number of panics. The first ones happened in X, but I finally > got a dump. Here's a trace: [...] > > Anybody else seen this? Yes. Just once. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 03:33:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16782 for freebsd-current-outgoing; Sun, 15 Nov 1998 03:33:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16774 for ; Sun, 15 Nov 1998 03:33:25 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id OAA25605; Sun, 15 Nov 1998 14:25:39 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.1/8.9.1) with ESMTP id OAA02022; Sun, 15 Nov 1998 14:25:00 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199811151125.OAA02022@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Wolfram Schneider cc: current@FreeBSD.ORG Subject: Re: sort option for find In-reply-to: Your message of "Sat, 14 Nov 1998 20:50:02 +0100." <19981114205002.A27346@panke.de.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Nov 1998 14:24:59 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wolfram Schneider wrote: > +extern int sflag; (This probably should be 'extern int issort;' in extern.h) > + > +/* > + * find_compare -- > + * A function which be used in fts_open() to order the > + * traversal of the hierarchy. > + * This function give you a lexicographical sorted output. > + */ > +static int find_compare(s1, s2) > + const FTSENT **s1, **s2; > +{ > + return strcoll( (*s1)->fts_name, (*s2)->fts_name ); > +} That depends on what do you call "lexicographical order". How do you compare "foo-1.2.3/Makefile" and "foo/Makefile", for example? (Anyhow, strcoll is not supposed to compare in lexicographical order at all. Most implementation don't give lexicographical sorting in non-C locale.). Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 03:33:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16806 for freebsd-current-outgoing; Sun, 15 Nov 1998 03:33:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16798 for ; Sun, 15 Nov 1998 03:33:53 -0800 (PST) (envelope-from regnauld@EU.org) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id MAA10146 for ; Sun, 15 Nov 1998 12:38:07 +0100 (CET) (envelope-from regnauld@EU.org) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id MAA24463 for ; Sun, 15 Nov 1998 12:59:31 +0100 (CET) Received: (from uucp@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id MAA29204 for freebsd-current@freebsd.org; Sun, 15 Nov 1998 12:33:03 +0100 (CET) Received: (from regnauld@localhost) by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id KAA04185; Sun, 15 Nov 1998 10:32:08 +0100 (CET) (envelope-from regnauld) Message-ID: <19981115103207.31226@stimpy.prosa.dk> Date: Sun, 15 Nov 1998 10:32:07 +0100 From: Phil Regnauld To: freebsd-current@FreeBSD.ORG Subject: sysctl -a oddity Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 3.0-CURRENT i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG System is Libretto 70 running 3.0-current (4 days old). For a while now, sysctl -a has given the following: kern.ostype: FreeBSD kern.osrelease: 3.0-CURRENT kern.osrevision: 199506 kern.version: FreeBSD 3.0-CURRENT #0: Sat Nov 14 00:23:55 CET 1998 regnauld@stimpy.prosa.dk:/usr/src/sys/compile/STIMPY.v4.pc kern.maxvnodes: 2192 kern.maxproc: 276 kern.maxfiles: 552 kern.argmax: 65536 kern.securelevel: -1 kern.hostname: stimpy.prosa.dk kern.hostid: 0 kern.clockrate: sysctl: S_clockinfo 20 != 16: Undefined error: 0 [stops here] Anything known ? Some clock bogon, but which ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 04:00:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19064 for freebsd-current-outgoing; Sun, 15 Nov 1998 04:00:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18850 for ; Sun, 15 Nov 1998 04:00:04 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id MAA15376; Sun, 15 Nov 1998 12:57:53 +0100 (CET) To: Phil Regnauld cc: freebsd-current@FreeBSD.ORG Subject: Re: sysctl -a oddity In-reply-to: Your message of "Sun, 15 Nov 1998 10:32:07 +0100." <19981115103207.31226@stimpy.prosa.dk> Date: Sun, 15 Nov 1998 12:57:53 +0100 Message-ID: <15374.911131073@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG recompile sysctl In message <19981115103207.31226@stimpy.prosa.dk>, Phil Regnauld writes: >System is Libretto 70 running 3.0-current (4 days old). > >For a while now, sysctl -a has given the following: > >kern.ostype: FreeBSD >kern.osrelease: 3.0-CURRENT >kern.osrevision: 199506 >kern.version: FreeBSD 3.0-CURRENT #0: Sat Nov 14 00:23:55 CET 1998 > regnauld@stimpy.prosa.dk:/usr/src/sys/compile/STIMPY.v4.pc > >kern.maxvnodes: 2192 >kern.maxproc: 276 >kern.maxfiles: 552 >kern.argmax: 65536 >kern.securelevel: -1 >kern.hostname: stimpy.prosa.dk >kern.hostid: 0 >kern.clockrate: sysctl: S_clockinfo 20 != 16: Undefined error: 0 > > [stops here] > > >Anything known ? Some clock bogon, but which ? > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 04:16:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21584 for freebsd-current-outgoing; Sun, 15 Nov 1998 04:16:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21547; Sun, 15 Nov 1998 04:15:49 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id MAA11713; Sun, 15 Nov 1998 12:15:26 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id LAA09096; Sun, 15 Nov 1998 11:06:48 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811151106.LAA09096@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Dmitry Valdov cc: Brian Somers , Brian Somers , current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd) In-reply-to: Your message of "Sun, 15 Nov 1998 09:29:01 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Nov 1998 11:06:47 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hmmm. I don't did anything with my 'hostname'. It valid.. > I think, I understand the problem. Look here: > If default route exists and connection isn't established than gethostbyname > () trying to get host by name via DNS server which isn't here. > I think You should do anything with it. Please don't advice me to insert my > hostname to /etc/hosts and set 'hosts' first in /etc/host.conf just because > FreeBSD has default with 'bind' prior to 'hosts'. > For what do You want to call function gethostbyname ()? May be it will > better to call it after executing ppp.conf to make user able to 'delete! > default' before gethostbyname () called? You'll find that a lot of programs will expect gethostname() to work, ppp is one of those programs. If you configure your machine correctly, ppp will behave correctly. IMHO, hosts should be before bind in /etc/resolv.conf - if you agree, feel free to try to convince someone to change that. If you don't agree, I suggest you configure and run a nameserver. > On Sat, 14 Nov 1998, Brian Somers wrote: > > > Date: Sat, 14 Nov 1998 00:22:03 +0000 > > From: Brian Somers > > To: Dmitry Valdov > > Cc: Brian Somers , current@FreeBSD.ORG > > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd) > > > > > Hi! > > > > > > > > > There is gdb's output: > > > > > > 0x280d7ea4 in _poll () > > > (gdb) bt > > > #0 0x280d7ea4 in _poll () > > > #1 0x280f4f11 in res_send () > > > #2 0x280f1c57 in res_query () > > > #3 0x280f2101 in __res_querydomain () > > > #4 0x280f1e55 in res_search () > > > #5 0x280eb5c8 in _gethostbydnsname () > > > #6 0x280ea23f in gethostbyname2 () > > > #7 0x280ea1c3 in gethostbyname () > > > #8 0x805cd4e in ipcp_Init (ipcp=0x8078714, bundle=0x80785f0, l=0x80a3000, > > > parent=0x8078648) at ipcp.c:359 > > > #9 0x804c1d1 in bundle_Create (prefix=0x807366d "/dev/tun", type=1, > > > argv=0xefbfdc44) at bundle.c:858 > > > #10 0x8061df5 in main (argc=1, argv=0xefbfdc44) at main.c:324 > > > #11 0x804a34d in _start () > > > > The gethostbyname() is the only thing I know in ppp that causes ppp > > to hang - hence my previous message: > > > > [.....] > > > ---------- Forwarded message ---------- > > > Date: Thu, 12 Nov 1998 01:08:05 +0000 > > > From: Brian Somers > > > To: Dmitry Valdov > > > Cc: Brian Somers , current@FreeBSD.ORG > > > Subject: Re: cvs commit: src/usr.sbin/ppp ip.c (fwd) > > > > > > Are you doing anything funny with ``hostname'' on your machine ? > > > The only reports I've heard where ppp hangs at startup is when your > > > ``hostname'' won't resolve (see http://www.FreeBSD.org/FAQ/userppp.html). > > > > > > If this isn't the problem, I'd appreciate if you could build ppp with > > > -g and when it hangs, run ``gdb -p whatever'' and do a ``bt''. > > [.....] > > > > This is what's causing the problem here. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 04:16:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA21618 for freebsd-current-outgoing; Sun, 15 Nov 1998 04:16:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA21548; Sun, 15 Nov 1998 04:15:51 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id MAA11679; Sun, 15 Nov 1998 12:12:38 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id LAA09177; Sun, 15 Nov 1998 11:27:54 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811151127.LAA09177@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? In-reply-to: Your message of "Sat, 14 Nov 1998 22:36:14 PST." <26948.911111774@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Nov 1998 11:27:53 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A lot of folks dive in and change this first thing since it's annoying > to have a non-connected host bring up a ppp connection just to resolve > your own hostname, and sysinstall is careful about putting entries > into /etc/hosts for this. Any objection to changing the default? For > most folks, it won't even make a difference since all the entries in > /etc/hosts are commented out by default. To shoot yourself in the > foot here still requires deliberate action, and at least /etc/hosts is > a better known location than /etc/host.conf - I still have to explain > that one to folks in this day and age. > > Comments? You took the words right out of my mount :-) A comment in /etc/hosts saying something like ``normally, only the hosts required at boot time are put in /etc/hosts'' and a pointer towards named might be useful too. > - Jordan -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 04:29:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22205 for freebsd-current-outgoing; Sun, 15 Nov 1998 04:29:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22200 for ; Sun, 15 Nov 1998 04:29:11 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id NAA19651 for current@FreeBSD.ORG; Sun, 15 Nov 1998 13:28:49 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 9D8521514; Sun, 15 Nov 1998 13:08:20 +0100 (CET) Date: Sun, 15 Nov 1998 13:08:20 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? Message-ID: <19981115130820.A15386@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <26948.911111774@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <26948.911111774@zippy.cdrom.com>; from Jordan K. Hubbard on Sat, Nov 14, 1998 at 10:36:14PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4805 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Jordan K. Hubbard: > Comments? As one who change the default each time, I vote YES. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 05:18:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24733 for freebsd-current-outgoing; Sun, 15 Nov 1998 05:18:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24727 for ; Sun, 15 Nov 1998 05:18:44 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id IAA04621; Sun, 15 Nov 1998 08:15:53 -0500 (EST) Date: Sun, 15 Nov 1998 08:15:51 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Greg Lehey cc: FreeBSD current users Subject: Re: Today's -CURRENT dies with "ffs_blkfree: bad size" In-Reply-To: <19981115194741.A414@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Nov 1998, Greg Lehey wrote: > Anybody else seen this? Greg, I *BELIEVE* this is related to davids changes that he made 2-3 days ago I think. Turning off a sysctl should work I just cant remember which one. David can tell you though. I think it has to do with non standard block sizes on FS's? I might be wrong. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 06:01:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27194 for freebsd-current-outgoing; Sun, 15 Nov 1998 06:01:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27183; Sun, 15 Nov 1998 06:01:13 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199811151401.GAA27183@hub.freebsd.org> Subject: Re: hosts before bind in /etc/host.conf? In-Reply-To: <26948.911111774@zippy.cdrom.com> from "Jordan K. Hubbard" at "Nov 14, 98 10:36:14 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sun, 15 Nov 1998 06:01:13 -0800 (PST) Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG do it! jmb Jordan K. Hubbard wrote: > A lot of folks dive in and change this first thing since it's annoying > to have a non-connected host bring up a ppp connection just to resolve > your own hostname, and sysinstall is careful about putting entries > into /etc/hosts for this. Any objection to changing the default? For > most folks, it won't even make a difference since all the entries in > /etc/hosts are commented out by default. To shoot yourself in the > foot here still requires deliberate action, and at least /etc/hosts is > a better known location than /etc/host.conf - I still have to explain > that one to folks in this day and age. > > Comments? > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 06:09:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27936 for freebsd-current-outgoing; Sun, 15 Nov 1998 06:09:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27931 for ; Sun, 15 Nov 1998 06:09:30 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id PAA00585; Sun, 15 Nov 1998 15:08:47 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Sun, 15 Nov 1998 15:08:47 +0100 (CET) From: Leif Neland cc: David Greenman , current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: SMP-System panics after recent ffs_alloc changes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Nov 1998, Michael Class wrote: > On Sat, 14 Nov 1998, David Greenman wrote: > > > >the recent changes in vfs_cluster.c, buf.h and ffs_alloc.c cause a > > >panic on my SMP-System. > > ... > > >The panic is"ffs_blkfree: bad size" > > My non-SMP does the same. I have also: dev = 0x40004 block = 0 fs = var panic ffs_blkfree: freeing free block syncing disks... 11 4 4 4 4 4 4 4 4 ... giving up > > Is there anything unusual about your filesystems? Are you using the > > standard 8K/1K block/fragment size? > # /dev/wd0a: type: ESDI disk: wd0s3 label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 381 sectors/unit: 6120765 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 204800 0 4.2BSD 0 0 0 # (Cyl. 0 - 12*) b: 281904 204800 swap # (Cyl. 12*- 30*) c: 6120765 0 unused 0 0 # (Cyl. 0 - 380) e: 61440 486704 4.2BSD 0 0 0 # (Cyl. 30*- 34*) f: 5572621 548144 4.2BSD 0 0 0 # (Cyl. 34*- 380*) /dev/wd0s3a on / (local, writes: sync 18 async 100) /dev/wd0s3f on /usr (local, writes: sync 36 async 224) /dev/wd0s3e on /var (local, writes: sync 100 async 195) /dev/wd0s1 on /c (local) (fat32) procfs on /proc (local) Leif Neland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 07:05:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01804 for freebsd-current-outgoing; Sun, 15 Nov 1998 07:05:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01797 for ; Sun, 15 Nov 1998 07:05:09 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id HAA01894; Sun, 15 Nov 1998 07:04:16 -0800 (PST) Message-Id: <199811151504.HAA01894@root.com> To: Open Systems Networking cc: Greg Lehey , FreeBSD current users Subject: Re: Today's -CURRENT dies with "ffs_blkfree: bad size" In-reply-to: Your message of "Sun, 15 Nov 1998 08:15:51 EST." From: David Greenman Reply-To: dg@root.com Date: Sun, 15 Nov 1998 07:04:16 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Anybody else seen this? > >Greg, > >I *BELIEVE* this is related to davids changes that he made 2-3 days ago I >think. Turning off a sysctl should work I just cant remember which one. >David can tell you though. I think it has to do with non standard block >sizes on FS's? I might be wrong. vfs.ffs.doreallocblks=0 will disable the new code. We don't know what is causing this yet, but if someone could get a crash dump along with a kernel built with -g and make them available on freefall then Kirk McKusick will investigate. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 07:09:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02083 for freebsd-current-outgoing; Sun, 15 Nov 1998 07:09:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-36-dbn.dial-up.net [196.34.155.36]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02076 for ; Sun, 15 Nov 1998 07:09:09 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id RAA24444 for freebsd-current@FreeBSD.ORG; Sun, 15 Nov 1998 17:08:02 +0200 (SAT) From: Robert Nordier Message-Id: <199811151508.RAA24444@ceia.nordier.com> Subject: Re: Help! Recovering from a ELF kernel moveover that didn't work!! In-Reply-To: from "Brian W. Buchanan" at "Nov 14, 98 03:25:09 pm" To: freebsd-current@FreeBSD.ORG Date: Sun, 15 Nov 1998 17:07:59 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian W. Buchanan wrote: > On Sat, 14 Nov 1998, Peter Johnson wrote: > > > Then I did the following: "disklabel -B -b /boot/boot1 -s /boot/boot2 da0a" > > (da0a is my / slice). > > > > Now my system just reboots when I try to boot FreeBSD.. > > Your system is like mine (and those of several others), which doesn't like > the new bootblocks. Boot from a FreeBSD floppy and do > "0:wd(0,a)/boot/loader" and the boot prompt, then "disklabel -B da0a" as > root to reinstall the old boot blocks. You can put "/boot/loader" in > boot.config to use the new bootloader until the new bootblocks are fixed. Just as a general comment (not aimed at anyone in particular): If someone is having a problem with some part of -current that's being actively developed, the best plan is to find out which FreeBSD developer is involved, and send e-mail directly to him, in which you describe (in as much detail as possible) just what is going wrong. If you believe there is a problem with the new boot blocks, for example, I'd be interested in getting mail which includes: o The source revisions you are using [ident(1)] o Drive, slice, and partition details [dmesg(8), fdisk(8), disklabel(8)] o Copies of the master boot record and slice boot sector [dd(1) and hexdump(1)] o A detailed description of exactly what happens (if the machine reboots, is a diagnostic or register dump displayed? At what stage do you think things are going wrong? Does the same thing happen if you boot from a floppy disk? from a floppy disk in a different PC? etc.) If all this seems too much like hard work, at least filing a PR (or adding a "me too", with some level of detail, to an existing PR) is likely to get the problem looked at. Just mentioning the problem on -current, making vague or oblique references to it, or keeping quiet about it in the hope that someone else will eventually get around to doing something: are all pretty effective strategies for keeping bugs around and problems ignored. To a great extent, maintaining and even improving the quality of FreeBSD is something that all -current users (whether active FreeBSD developers or not) can take responsibility for. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 07:36:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05030 for freebsd-current-outgoing; Sun, 15 Nov 1998 07:36:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw1.pl.cp (ppp-pw16.nttca.com [204.160.176.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05024 for ; Sun, 15 Nov 1998 07:36:22 -0800 (PST) (envelope-from astralblue@usa.net) Received: from localhost (gene@localhost) by gw1.pl.cp (8.9.1/8.9.1) with SMTP id HAA09853 for ; Sun, 15 Nov 1998 07:35:48 -0800 (PST) (envelope-from astralblue@usa.net) X-Authentication-Warning: gw1.pl.cp: gene owned process doing -bs Date: Sun, 15 Nov 1998 07:35:48 -0800 (PST) From: "Eugene M. Kim" X-Sender: gene@gw1.pl.cp To: FreeBSD-current Mailing List Subject: NFS memory leak Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was trying to installworld yesterday when the bug popped out. First, suddenly the NFS server stopped to respond, but didn't panic. After some work I found that the server could not send any IP packets; sendto() (which ping uses) returned an error with ENOBUF. Then I rebooted the server, and ran ``systat -vm 1'' and ``ping CLIENT''. The ``free'' (between ``cache'' and ``daefr'') remained stable for a while, but as soon as I started to installworld on the client, the figure suddenly began to erode, and when it finally almost hit zero (I think it was 40 or something) -- ping stopped working. Is this a known bug? I don't remember this reported/discussed on -current. Throw me a stone if it's been. :-) Thanks, Eugene -- Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 08:02:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07453 for freebsd-current-outgoing; Sun, 15 Nov 1998 08:02:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07446 for ; Sun, 15 Nov 1998 08:02:41 -0800 (PST) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id RAA10554; Sun, 15 Nov 1998 17:02:06 +0100 (CET) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id OAA02188; Sun, 15 Nov 1998 14:05:19 +0100 (MET) (envelope-from wosch) Message-ID: <19981115140518.A2166@panke.de.freebsd.org> Date: Sun, 15 Nov 1998 14:05:18 +0100 From: Wolfram Schneider To: Dmitrij Tejblum Cc: current@FreeBSD.ORG Subject: Re: sort option for find References: <19981114205002.A27346@panke.de.freebsd.org> <199811151125.OAA02022@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199811151125.OAA02022@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Sun, Nov 15, 1998 at 02:24:59PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-11-15 14:24:59 +0300, Dmitrij Tejblum wrote: > > + * find_compare -- > > + * A function which be used in fts_open() to order the > > + * traversal of the hierarchy. > > + * This function give you a lexicographical sorted output. > > + */ > > +static int find_compare(s1, s2) > > + const FTSENT **s1, **s2; > > +{ > > + return strcoll( (*s1)->fts_name, (*s2)->fts_name ); > > +} > > That depends on what do you call "lexicographical order". How do you > compare "foo-1.2.3/Makefile" and "foo/Makefile", for example? (Anyhow, I compare the file "foo-1.2.3" with the file "foo" and "foo-1.2.3" is greater. The directory "foo" will be visited first. I don't sort the output - I change the order of the traversal of the file hierarchy. As a side effect, the output will be sorted on a per directory basis. Wolfram > strcoll is not supposed to compare in lexicographical order at all. > Most implementation don't give lexicographical sorting in non-C locale.). > > Dima > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 08:12:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08572 for freebsd-current-outgoing; Sun, 15 Nov 1998 08:12:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08567 for ; Sun, 15 Nov 1998 08:12:09 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA09315; Sun, 15 Nov 1998 11:11:37 -0500 (EST) (envelope-from luoqi) Date: Sun, 15 Nov 1998 11:11:37 -0500 (EST) From: Luoqi Chen Message-Id: <199811151611.LAA09315@lor.watermarkgroup.com> To: FreeBSD-current@FreeBSD.ORG, grog@lemis.com Subject: Re: Today's -CURRENT dies with "ffs_blkfree: bad size" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've just upgraded my kernel to a sup of about 9 hours ago, and have > had a number of panics. The first ones happened in X, but I finally > got a dump. Here's a trace: > > #0 boot (howto=262400) at ../../kern/kern_shutdown.c:285 > 285 dumppcb.pcb_cr3 = rcr3(); > (kgdb) bt > #0 boot (howto=262400) at ../../kern/kern_shutdown.c:285 > #1 0xf013e1e5 in panic (fmt=0xf01cc3e1 "ffs_blkfree: bad size") > at ../../kern/kern_shutdown.c:453 > #2 0xf01cc53e in ffs_blkfree (ip=0xf1283400, bno=4, size=8192) ^^^^^ It could be caused by our delayed bmap binding. Check to see if bp->b_blkno == bp->b_lblkno for this block. > at ../../ufs/ffs/ffs_alloc.c:1300 > #3 0xf01cac04 in ffs_reallocblks (ap=0xf8cc1e14) > at ../../ufs/ffs/ffs_alloc.c:523 > #4 0xf015e2e3 in cluster_write (bp=0xf461a7e8, filesize=106496) > at vnode_if.h:1035 > #5 0xf01d2147 in ffs_write (ap=0xf8cc1eec) > at ../../ufs/ufs/ufs_readwrite.c:368 > #6 0xf0167d5b in vn_write (fp=0xf1233200, uio=0xf8cc1f30, cred=0xf11cac80) > at vnode_if.h:331 > #7 0xf0146da2 in write (p=0xf8cac880, uap=0xf8cc1f84) > at ../../kern/sys_generic.c:270 > #8 0xf01fcef3 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 114688, > tf_esi = 537546280, tf_ebp = -272642672, tf_isp = -120840236, > tf_ebx = 537477216, tf_edx = 537546280, tf_ecx = 0, tf_eax = 4, > tf_trapno = 7, tf_err = 7, tf_eip = 537412177, tf_cs = 31, > tf_eflags = 514, tf_esp = -272642696, tf_ss = 39}) > at ../../i386/i386/trap.c:1031 > #9 0x20084251 in ?? () > > Anybody else seen this? > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 08:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09033 for freebsd-current-outgoing; Sun, 15 Nov 1998 08:17:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09018; Sun, 15 Nov 1998 08:17:08 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA04167; Sun, 15 Nov 1998 09:16:46 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA10530; Sun, 15 Nov 1998 09:16:45 -0700 Date: Sun, 15 Nov 1998 09:16:45 -0700 Message-Id: <199811151616.JAA10530@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? In-Reply-To: <26948.911111774@zippy.cdrom.com> References: <26948.911111774@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > A lot of folks dive in and change this first thing since it's annoying > to have a non-connected host bring up a ppp connection just to resolve > your own hostname, and sysinstall is careful about putting entries > into /etc/hosts for this. Any objection to changing the default? The only issue is the 'localhost' thing, which is not setup correctly. Or do you make sure localhost gets modified to say locahost.do.main in sysinstall now? Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 08:28:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10001 for freebsd-current-outgoing; Sun, 15 Nov 1998 08:28:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09991 for ; Sun, 15 Nov 1998 08:28:51 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id TAA29577; Sun, 15 Nov 1998 19:26:32 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.1/8.9.1) with ESMTP id TAA04794; Sun, 15 Nov 1998 19:26:17 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199811151626.TAA04794@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Wolfram Schneider cc: current@FreeBSD.ORG Subject: Re: sort option for find In-reply-to: Your message of "Sun, 15 Nov 1998 14:05:18 +0100." <19981115140518.A2166@panke.de.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Nov 1998 19:26:16 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wolfram Schneider wrote: > > > > That depends on what do you call "lexicographical order". How do you > > compare "foo-1.2.3/Makefile" and "foo/Makefile", for example? (Anyhow, > > I compare the file "foo-1.2.3" with the file "foo" and > "foo-1.2.3" is greater. The directory "foo" will be visited first. > > I don't sort the output - I change the order > of the traversal of the file hierarchy. As a side effect, the output > will be sorted on a per directory basis. Sure, but did you noticed that strcmp("foo-1.2.3/Makefile", "foo/Makefile") < 0? That is, 'find -s' and 'find | sort' give different results? Is it ok? Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 09:34:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15698 for freebsd-current-outgoing; Sun, 15 Nov 1998 09:34:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from o-o.org (o-o.org [207.252.201.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15682; Sun, 15 Nov 1998 09:34:33 -0800 (PST) (envelope-from licia@o-o.org) Received: from localhost (root@localhost) by o-o.org (8.8.8/8.8.7) with SMTP id LAA04660; Sun, 15 Nov 1998 11:33:58 -0600 (CST) Date: Sun, 15 Nov 1998 11:33:58 -0600 (CST) From: Licia To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? In-Reply-To: <26948.911111774@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I personally think this is a very good idea. On a fairly unrelated note, I would also suggest if possible, to add a default of -s to the syslogd flags in /etc/rc.conf for people who are not aware of the possibility of syslog bombing. On Sat, 14 Nov 1998, Jordan K. Hubbard wrote: > A lot of folks dive in and change this first thing since it's annoying > to have a non-connected host bring up a ppp connection just to resolve > your own hostname, and sysinstall is careful about putting entries > into /etc/hosts for this. Any objection to changing the default? For > most folks, it won't even make a difference since all the entries in > /etc/hosts are commented out by default. To shoot yourself in the > foot here still requires deliberate action, and at least /etc/hosts is > a better known location than /etc/host.conf - I still have to explain > that one to folks in this day and age. > > Comments? > > - Jordan > [ licia@o-o.org ] [ http://www.o-o.org/ ] [ IrcNick : Licia ] [ A happy user of FreeBSD : http://www.freebsd.org/ ] [ Why crawl through windows when you can walk through a door? ] [ This user boycotts all Microsoft products and services ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 10:26:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19662 for freebsd-current-outgoing; Sun, 15 Nov 1998 10:26:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA19657 for ; Sun, 15 Nov 1998 10:26:48 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id TAA12739; Sun, 15 Nov 1998 19:21:21 +0100 (CET) Message-ID: <19981115192121.A12524@foobar.franken.de> Date: Sun, 15 Nov 1998 19:21:21 +0100 From: Harold Gutch To: Poul-Henning Kamp , Phil Regnauld Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysctl -a oddity References: <19981115103207.31226@stimpy.prosa.dk> <15374.911131073@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <15374.911131073@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Nov 15, 1998 at 12:57:53PM +0100 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 15, 1998 at 12:57:53PM +0100, Poul-Henning Kamp wrote: > recompile sysctl > > In message <19981115103207.31226@stimpy.prosa.dk>, Phil Regnauld writes: > >System is Libretto 70 running 3.0-current (4 days old). > > > >For a while now, sysctl -a has given the following: > > > >kern.ostype: FreeBSD > >kern.osrelease: 3.0-CURRENT > >kern.osrevision: 199506 > >kern.version: FreeBSD 3.0-CURRENT #0: Sat Nov 14 00:23:55 CET 1998 > > regnauld@stimpy.prosa.dk:/usr/src/sys/compile/STIMPY.v4.pc > > > >kern.maxvnodes: 2192 > >kern.maxproc: 276 > >kern.maxfiles: 552 > >kern.argmax: 65536 > >kern.securelevel: -1 > >kern.hostname: stimpy.prosa.dk > >kern.hostid: 0 > >kern.clockrate: sysctl: S_clockinfo 20 != 16: Undefined error: 0 > > > > [stops here] > > I experienced exactly the same behaviour on a 3.0-19980916-SNAP system (kernel and world therefore in sync). After a reboot sysctl worked fine again. -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 12:55:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01260 for freebsd-current-outgoing; Sun, 15 Nov 1998 12:55:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from geisha.samurai.com (geisha.samurai.com [205.207.28.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01250 for ; Sun, 15 Nov 1998 12:54:58 -0800 (PST) (envelope-from bryanf@geisha.samurai.com) Received: (from bryanf@localhost) by geisha.samurai.com (8.9.1a/8.9.1) id PAA01739 for freebsd-current@freebsd.org; Sun, 15 Nov 1998 15:54:33 -0500 (EST) Date: Sun, 15 Nov 1998 15:54:33 -0500 From: Bryan Fullerton To: freebsd-current@FreeBSD.ORG Subject: proc changes Message-ID: <19981115155433.A1731@samurai.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did something change recently with the proc routines? I just cvsup'ed my 3.0 kernel and rebuilt and rebooted, and now utils which access proc don't work anymore. For example, when I run ps, I get: ps: proc size mismatch (16128 total, 668 chunks) What do I need to rebuild to get things working again? Just the utilities affected, or also libraries? I'd prefer not to have to rebuild the entire system if possible. Thanks, Bryan -- Bryan Fullerton http://www.samurai.com/ Owner, Lead Consultant http://www.feh.net/ Samurai Consulting http://www.icomm.ca/ "No, we don't do seppuku." Can you feel the Ohmu call? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 13:03:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01972 for freebsd-current-outgoing; Sun, 15 Nov 1998 13:03:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01967 for ; Sun, 15 Nov 1998 13:03:37 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id QAA08950; Sun, 15 Nov 1998 16:02:30 -0500 (EST) Date: Sun, 15 Nov 1998 16:02:28 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Bryan Fullerton cc: freebsd-current@FreeBSD.ORG Subject: Re: proc changes In-Reply-To: <19981115155433.A1731@samurai.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG *grumble* *grumble* Ok for the Nth time :-) You need to rebuild libkvm and associated utils and build a new kernel. Im wondering if anyone reads current. :) Actually ive been guilty of that myself in the past you dont read the HEADS-UP or the repeated threads till your bitten. then its too late cause they threads have died. Oh well maybe one day well get that real-time trouble ticket system on the web :-) Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 13:43:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05544 for freebsd-current-outgoing; Sun, 15 Nov 1998 13:43:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from geisha.samurai.com (geisha.samurai.com [205.207.28.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05534 for ; Sun, 15 Nov 1998 13:43:40 -0800 (PST) (envelope-from bryanf@geisha.samurai.com) Received: (from bryanf@localhost) by geisha.samurai.com (8.9.1a/8.9.1) id QAA01921; Sun, 15 Nov 1998 16:42:49 -0500 (EST) Date: Sun, 15 Nov 1998 16:42:49 -0500 From: Bryan Fullerton To: Open Systems Networking Cc: freebsd-current@FreeBSD.ORG Subject: Re: proc changes Message-ID: <19981115164249.A1874@samurai.com> References: <19981115155433.A1731@samurai.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: ; from Open Systems Networking on Sun, Nov 15, 1998 at 04:02:28PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 15, 1998 at 04:02:28PM -0500, Open Systems Networking wrote: > > Ok for the Nth time :-) > > You need to rebuild libkvm and associated utils and build a new kernel. Right. I was more or less looking for some way of finding out what those 'associated utils' are so I can build just them instead of the entire source tree. > Im wondering if anyone reads current. :) Sorry, must have missed it in all the bantering about /usr/mdec. ;) Thanks anyways - in the mean time I've gone back to a 3.0-R kernel until I can attack this in a more organized fashion. Bryan -- Bryan Fullerton http://www.samurai.com/ Owner, Lead Consultant http://www.feh.net/ Samurai Consulting http://www.icomm.ca/ "No, we don't do seppuku." Can you feel the Ohmu call? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 13:52:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06542 for freebsd-current-outgoing; Sun, 15 Nov 1998 13:52:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06526 for ; Sun, 15 Nov 1998 13:52:44 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id QAA16199; Sun, 15 Nov 1998 16:51:06 -0500 (EST) Date: Sun, 15 Nov 1998 16:51:04 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Bryan Fullerton cc: freebsd-current@FreeBSD.ORG Subject: Re: proc changes In-Reply-To: <19981115164249.A1874@samurai.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Nov 1998, Bryan Fullerton wrote: > Right. I was more or less looking for some way of finding out what those > 'associated utils' are so I can build just them instead of the entire source > tree. Oh sorry, I guess saying those utils that depend on libkvm wont help much either then huh? :-) lesse, ps, w, top, vmstat, and any other util that spits out a kvm* error. > Sorry, must have missed it in all the bantering about /usr/mdec. ;) No worries I have done it plenty myself. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 13:56:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07010 for freebsd-current-outgoing; Sun, 15 Nov 1998 13:56:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07002 for ; Sun, 15 Nov 1998 13:56:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1a/8.9.1) with ESMTP id NAA21152; Sun, 15 Nov 1998 13:55:24 -0800 (PST) To: Bryan Fullerton cc: Open Systems Networking , freebsd-current@FreeBSD.ORG Subject: Re: proc changes In-reply-to: Your message of "Sun, 15 Nov 1998 16:42:49 EST." <19981115164249.A1874@samurai.com> Date: Sun, 15 Nov 1998 13:55:24 -0800 Message-ID: <21148.911166924@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Right. I was more or less looking for some way of finding out what those > 'associated utils' are so I can build just them instead of the entire source > tree. Don't bother. If you're going to update your system, *always* do it via a make world and make kernel. If you have no disk space or time to do this, simply don't update. :-) I know that seems rather strict, but there are so many ways to break your system with partial builds, and so much work has gone into making "world" a target which prevents such occurrances, that we really can't recommend any other course of action. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 14:05:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07846 for freebsd-current-outgoing; Sun, 15 Nov 1998 14:05:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07839; Sun, 15 Nov 1998 14:05:19 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199811152205.OAA07839@hub.freebsd.org> Subject: The FreeBSD UK User Group Oxford dinner To: current, hackers Date: Sun, 15 Nov 1998 14:05:19 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Paul asked me to send this out....bon appetit! jmb FreeBSD UK User Group Oxford dinner --------------------------------------- A FreeBSD night out has been arranged for November 21 in Oxford. We're meeting up for a few beers in the Royal Oak on Woodstock Road at around 7.30 and then heading on for a meal at Jamal's Indian restaurant on Walton St (booked for 10pm). The plan is for as many people from the UK FreeBSD community to get together to informally discuss what we can do as a group in the future. More or less anyone is welcome on this occasion, including partners and other friends who might be interested, such as NetBSD or Linux users who want to come along to a hackers night out. Email me at paul@originative.co.uk if you want to come along but be quick because it's not long to go :-) Here's a web page with directions/maps and a list of who's coming so far, as well as possible accommodation in Oxford for those wanting to stay the night. http://www.originative.co.uk/FreeBSD.htm Paul Richards Ph.D. Originative Solutions Ltd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 14:20:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09688 for freebsd-current-outgoing; Sun, 15 Nov 1998 14:20:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09662 for ; Sun, 15 Nov 1998 14:20:09 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id IAA00590; Mon, 16 Nov 1998 08:49:41 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id IAA00487; Mon, 16 Nov 1998 08:49:34 +1030 (CST) Message-ID: <19981116084934.B445@freebie.lemis.com> Date: Mon, 16 Nov 1998 08:49:34 +1030 From: Greg Lehey To: dg@root.com, Kirk McKusick Cc: FreeBSD current users Subject: Re: Today's -CURRENT dies with "ffs_blkfree: bad size" References: <199811151504.HAA01894@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811151504.HAA01894@root.com>; from David Greenman on Sun, Nov 15, 1998 at 07:04:16AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 X-Mutt-References: <199811151504.HAA01894@root.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 15 November 1998 at 7:04:16 -0800, David Greenman wrote: >>> Anybody else seen this? >> >> Greg, >> >> I *BELIEVE* this is related to davids changes that he made 2-3 days ago I >> think. Turning off a sysctl should work I just cant remember which one. >> David can tell you though. I think it has to do with non standard block >> sizes on FS's? I might be wrong. > > vfs.ffs.doreallocblks=0 will disable the new code. We don't know what is > causing this yet, but if someone could get a crash dump along with a kernel > built with -g and make them available on freefall then Kirk McKusick will > investigate. Well, I have a dump and a -g kernel, but it'll take forever to get a dump to freefall. If Kirk's prepared to debug it locally, he's welcome. Otherwise be prepared for quite a delay. Kirk, let me know. The net connection here's adequate--send me a master.passwd entry if you want to do it. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 15:24:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16348 for freebsd-current-outgoing; Sun, 15 Nov 1998 15:24:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16247; Sun, 15 Nov 1998 15:23:51 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA02583; Sun, 15 Nov 1998 18:23:18 -0500 (EST) Date: Sun, 15 Nov 1998 18:23:18 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? In-Reply-To: <26948.911111774@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Nov 1998, Jordan K. Hubbard wrote: > A lot of folks dive in and change this first thing since it's annoying Yep, I do this too. > to have a non-connected host bring up a ppp connection just to resolve > your own hostname, and sysinstall is careful about putting entries > into /etc/hosts for this. Any objection to changing the default? For > most folks, it won't even make a difference since all the entries in > /etc/hosts are commented out by default. To shoot yourself in the > foot here still requires deliberate action, and at least /etc/hosts is > a better known location than /etc/host.conf - I still have to explain > that one to folks in this day and age. > > Comments? > Sure, it'd make sense to make this default! > - Jordan > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 15:26:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16492 for freebsd-current-outgoing; Sun, 15 Nov 1998 15:26:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16484 for ; Sun, 15 Nov 1998 15:26:06 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id QAA13837; Sun, 15 Nov 1998 16:25:43 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd013819; Sun Nov 15 16:25:35 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA03397; Sun, 15 Nov 1998 16:25:35 -0700 (MST) From: Terry Lambert Message-Id: <199811152325.QAA03397@usr05.primenet.com> Subject: Re: newer gcc? To: imp@village.org (Warner Losh) Date: Sun, 15 Nov 1998 23:25:34 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199811100540.WAA05121@harmony.village.org> from "Warner Losh" at Nov 9, 98 10:40:37 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : That's a bit premature. I'd be more interested if you could even build > : the world from egcs installed in /usr/local. > > As would I. I'm trying to get a cross build environment working, and > am finding that gcc is a hard nut to crack at its current revision > level. You will find that you can not use a C++ compiler from a port to build in trees where DESTDIR is defined. The reason for this is that the use of DESTDIR screws up CFLAGS and CXXINCLUDES to use the DESTDIR relative (and therefore non-port) include directories. So if, for example, you have code that depends on exceptions and RTTI working, you are SOL. See: /usr/share/mk/bsd.prog.mk /usr/share/mk/bsd.lib.mk for details. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 15:29:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16886 for freebsd-current-outgoing; Sun, 15 Nov 1998 15:29:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16875 for ; Sun, 15 Nov 1998 15:29:33 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id QAA10264; Sun, 15 Nov 1998 16:29:07 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd010184; Sun Nov 15 16:28:57 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA03497; Sun, 15 Nov 1998 16:28:51 -0700 (MST) From: Terry Lambert Message-Id: <199811152328.QAA03497@usr05.primenet.com> Subject: Re: newer gcc? To: bright@hotjobs.com (Alfred Perlstein) Date: Sun, 15 Nov 1998 23:28:51 +0000 (GMT) Cc: psalzman@gamefish.pcola.gulf.net, current@FreeBSD.ORG In-Reply-To: from "Alfred Perlstein" at Nov 9, 98 10:07:38 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > a) egcs is a bit more improved than gcc in terms of c++ support, and more > features/optimizations. Except egcs can not support the Standard Temple Library on FreeBSD unless you compile it with threading enabled (unlike g++ 2.8.1, you must choose threading or no threading for resulting binaries at the time you compile the compiler, not at the time you compile the program). If you compile it with threading enabled, be prepared to delete libc entirely and *only* use libc_r, or you will get quirky behaviour from a lot of code. A good yardstick for a C++ compiler is to try to compile and run the Cyrus ACAPD code with the thing, since that code is very gung-ho with regard to use of C++ constructs. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 15:38:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17697 for freebsd-current-outgoing; Sun, 15 Nov 1998 15:38:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17689 for ; Sun, 15 Nov 1998 15:38:20 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA06003; Sun, 15 Nov 1998 16:37:45 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd005991; Sun Nov 15 16:37:39 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id QAA03773; Sun, 15 Nov 1998 16:37:33 -0700 (MST) From: Terry Lambert Message-Id: <199811152337.QAA03773@usr05.primenet.com> Subject: Re: SparQ Drive and 3.0 upgrade To: james@westongold.com (James Mansion) Date: Sun, 15 Nov 1998 23:37:32 +0000 (GMT) Cc: tom@uniserve.com, mike@smith.net.au, sporkl@ix.netcom.com, freebsd-current@FreeBSD.ORG In-Reply-To: <32BABEF63EAED111B2C5204C4F4F50201810@WGP01> from "James Mansion" at Nov 9, 98 08:51:30 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Out of interest, is there a 'recommended' high-capacity > removable device that can be used to boot different OSs on > a single PC? > > Jazz??? I use Jaz drives successfully with many OS's. Note that there is a bug with the Windows 95/98/NT TSD (Type Specific Driver) such that these operating systems have trouble paging to removable devices. Specifically, the PCI bus caching requires the code to do an in* after and out* to flush the bus cache, and the TSD that Microsoft provides doesn't do this. I found this out after installing Windows 95 and NT on JAZ cartridges, and then having problems installing Visual InterDev (their full "professional" developement tools suite) and seeing very odd behaviour trying to install Visual SourceSafe (the revision control system) and Visual J++. Eventually they refunded my support incident when I located the assembly code error in their driver (using WinICE) and pointed it out to them. FreeBSD needs something like WinICE... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 15:57:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19714 for freebsd-current-outgoing; Sun, 15 Nov 1998 15:57:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19546 for ; Sun, 15 Nov 1998 15:57:12 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id AAA01007 for ; Mon, 16 Nov 1998 00:56:43 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Mon, 16 Nov 1998 00:56:42 +0100 (CET) From: Leif Neland To: freebsd-current@FreeBSD.ORG Subject: Why doesn't make world make MAKEDEV? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any reason why MAKEDEV doesn't get installed by make world? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 15:58:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA20006 for freebsd-current-outgoing; Sun, 15 Nov 1998 15:58:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp4.nwnexus.com (smtp4.nwnexus.com [206.63.63.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19981; Sun, 15 Nov 1998 15:58:26 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx101-ip26.nwnexus.net [204.57.235.76]) by smtp4.nwnexus.com (8.8.8/8.8.8) with ESMTP id PAA10571; Sun, 15 Nov 1998 15:58:01 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.1/8.8.8) id PAA03110; Sun, 15 Nov 1998 15:53:46 -0800 (PST) (envelope-from wrsomsky) Message-ID: <19981115155346.A2946@halcyon.com> Date: Sun, 15 Nov 1998 15:53:46 -0800 From: "William R. Somsky" To: Nate Williams , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? References: <26948.911111774@zippy.cdrom.com> <199811151616.JAA10530@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811151616.JAA10530@mt.sri.com>; from Nate Williams on Sun, Nov 15, 1998 at 09:16:45AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 15, 1998 at 09:16:45AM -0700, Nate Williams wrote: > > A lot of folks dive in and change this first thing since it's annoying > > to have a non-connected host bring up a ppp connection just to resolve > > your own hostname, and sysinstall is careful about putting entries > > into /etc/hosts for this. Any objection to changing the default? 1) I say go for it as well... > The only issue is the 'localhost' thing, which is not setup correctly. > Or do you make sure localhost gets modified to say locahost.do.main in > sysinstall now? 2) Hmm... Should localhost have a domain associated with it? I wouldn't think so. Even on "real", full-IP/DNS-membership machines this doesn't seem right. Eg, my machine at work is annwn.phys.washington.edu = 128.95.93.180, on it, should it have localhost.phys.washington.edu = 127.0.0.1? Why does ".phys.washington.edu" have _anything_ to do with it? I don't see it. Am I missing something? ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:00:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20264 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:00:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20247 for ; Sun, 15 Nov 1998 16:00:22 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id SAA08223; Sun, 15 Nov 1998 18:59:48 -0500 (EST) Date: Sun, 15 Nov 1998 18:59:46 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Leif Neland cc: freebsd-current@FreeBSD.ORG Subject: Re: Why doesn't make world make MAKEDEV? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Leif Neland wrote: > Any reason why MAKEDEV doesn't get installed by make world? Because its in /etc and that directory never gets touched unless you do a make release. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:04:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21160 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:04:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21128 for ; Sun, 15 Nov 1998 16:04:02 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA13255; Sun, 15 Nov 1998 17:03:31 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd013216; Sun Nov 15 17:03:23 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA04690; Sun, 15 Nov 1998 17:03:17 -0700 (MST) From: Terry Lambert Message-Id: <199811160003.RAA04690@usr05.primenet.com> Subject: Re: The infamous dying daemons bug To: julian@whistle.com (Julian Elischer) Date: Mon, 16 Nov 1998 00:03:17 +0000 (GMT) Cc: luoqi@watermarkgroup.com, dg@root.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG, eivind@yes.no, jfieber@indiana.edu In-Reply-To: from "Julian Elischer" at Nov 9, 98 01:36:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We;ve been seeing problems since 96/97 > > On Mon, 9 Nov 1998, Luoqi Chen wrote: > > > the offset into account. This piece of code has been there since '95, so > > I can't say if this was responsible for the daemon dying problem. More correctly, we've been seeing this problem ever since moving past FreeBSD 2.2.5, after John's megapatches just before his leaving prevented him from following them up, per SOP. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:04:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21185 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:04:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp4.nwnexus.com (smtp4.nwnexus.com [206.63.63.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20791; Sun, 15 Nov 1998 16:03:36 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx101-ip26.nwnexus.net [204.57.235.76]) by smtp4.nwnexus.com (8.8.8/8.8.8) with ESMTP id QAA10161; Sun, 15 Nov 1998 16:03:11 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.1/8.8.8) id PAA03213; Sun, 15 Nov 1998 15:58:02 -0800 (PST) (envelope-from wrsomsky) Message-ID: <19981115155802.B2946@halcyon.com> Date: Sun, 15 Nov 1998 15:58:02 -0800 From: "William R. Somsky" To: Licia , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? References: <26948.911111774@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Licia on Sun, Nov 15, 1998 at 11:33:58AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 15, 1998 at 11:33:58AM -0600, Licia wrote: > > I personally think this is a very good idea. > > On a fairly unrelated note, I would also suggest if possible, > to add a default of -s to the syslogd flags in /etc/rc.conf for people > who are not aware of the possibility of syslog bombing. Oh, and while we're mentioning things, what about adding "-n" to the "netstat" in the daily status-network script? Until I added this myself, my machine was always dialing out at 2AM, when this script ran. This is with everything I could reasonably think of already added to /etc/hosts... -- ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:07:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22609 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:07:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22602 for ; Sun, 15 Nov 1998 16:07:34 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id RAA14209; Sun, 15 Nov 1998 17:07:11 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp01.primenet.com, id smtpd014191; Sun Nov 15 17:07:05 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA04793; Sun, 15 Nov 1998 17:07:02 -0700 (MST) From: Terry Lambert Message-Id: <199811160007.RAA04793@usr05.primenet.com> Subject: Re: The infamous dying daemons bug To: green@unixhelp.org (Brian Feldman) Date: Mon, 16 Nov 1998 00:07:02 +0000 (GMT) Cc: eivind@yes.no, dg@root.com, jfieber@indiana.edu, current@FreeBSD.ORG In-Reply-To: from "Brian Feldman" at Nov 8, 98 11:45:50 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is it just me or has noone actually captured the corefiles, compiled > whatever died -g, and tried to debug exactly what caused the sig11? Not > the underlying cause, just the "actual" cause (like a certain register > being a wrong value). Julian has, Doug Ambrisko has, I have, and, I think, Archie has. Note that the sig-11's we see occur after a lot of swap thrash not necessarily as a result of an out of memory condition. In general, when debugged, the process in question died from attempting to reference a page for which the mapping existed but for which the page itself did not (but by all rights should have). Someone kyped the page. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:08:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22795 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:08:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22790 for ; Sun, 15 Nov 1998 16:08:28 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA25575; Sun, 15 Nov 1998 17:00:53 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd025498; Sun Nov 15 17:00:42 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA04591; Sun, 15 Nov 1998 17:00:40 -0700 (MST) From: Terry Lambert Message-Id: <199811160000.RAA04591@usr05.primenet.com> Subject: Re: The infamous dying daemons bug To: bde@zeta.org.au (Bruce Evans) Date: Mon, 16 Nov 1998 00:00:40 +0000 (GMT) Cc: archie@whistle.com, phk@critter.freebsd.dk, current@FreeBSD.ORG In-Reply-To: <199811100634.RAA13398@godzilla.zeta.org.au> from "Bruce Evans" at Nov 10, 98 05:34:54 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >A static inetd sounds like a good experiment. > > I couldn't duplicate the dying daemons problem despite trying fairly > hard, and thought that this might be because I link everything in the > world static. I didn't try hard enough to downgrade to a default world. This data point, Dima's information, and the infromation from Garrett about it seeming to affect only swapped processes jives with my own previously stated intuition about the problem being related to mmap. I think we can be even more specific now, and postulate: The problem occurs when an image that is linked shared mmap's a library file and modifies a data page on that file, causing a copy-on-write, and for which the copied page is subsequently swapped to disk. There is apparently a reclaim error involving this page when the system later attempts to recover pages for its own use, and subsequent references to this data page by children of the parent process fail. We already know that there are dragons in the mmap code; I believe I actually slew the one that would under these circumstances: 1) Set up a cron job to run newsyslog once a minute 2) Cause swap to thrash 3) Do sysloging to force the logs to roll as a result of the newsyslog Note: The thrash is heavy swap load (NOT an out-of-swap condition!). Note: The cron program is known to do some evil things; specifically, it modifies return pwent buffers, resulting in copy-on-write, even though the pwent stuff is implemented as pages mapeed from a db file, and POSIX prohibits cron doing this. resulting in: 3) One or more pages from the password file are written to any open file, usually the one most frequently being the crontab because of the newsyslog runs. This one was (apparently) killed when the actual object size was used instead of bogusly rounding the object size to a page boundary. It seems that there is at least one additional case of a problem with mmap() here, given the apparent shared library inetraction... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:15:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23433 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:15:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23421 for ; Sun, 15 Nov 1998 16:15:47 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id BAA01649; Mon, 16 Nov 1998 01:15:20 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Mon, 16 Nov 1998 01:15:20 +0100 (CET) From: Leif Neland To: Open Systems Networking cc: freebsd-current@FreeBSD.ORG Subject: Re: Why doesn't make world make MAKEDEV? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Nov 1998, Open Systems Networking wrote: > On Mon, 16 Nov 1998, Leif Neland wrote: > > > Any reason why MAKEDEV doesn't get installed by make world? > > Because its in /etc and that directory never gets touched unless you do a > make release. > Well, on my system it is in /dev Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:16:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23566 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:16:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23541 for ; Sun, 15 Nov 1998 16:16:43 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id TAA01583; Sun, 15 Nov 1998 19:14:46 -0500 (EST) Date: Sun, 15 Nov 1998 19:14:46 -0500 (EST) From: John Fieber To: "Jordan K. Hubbard" cc: Bryan Fullerton , Open Systems Networking , freebsd-current@FreeBSD.ORG Subject: Re: proc changes In-Reply-To: <21148.911166924@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Nov 1998, Jordan K. Hubbard wrote: > Don't bother. If you're going to update your system, *always* do it > via a make world and make kernel. If you have no disk space or time > to do this, simply don't update. :-) Or go the snapshot-install route. With the right partitioning, this can be quick and nearly painless. Alas, snapshoots seem to have stopped on November 3.... -john (who hasn't done a make world since he ran 386BSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:18:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23679 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:18:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23674 for ; Sun, 15 Nov 1998 16:18:32 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id TAA11712; Sun, 15 Nov 1998 19:18:07 -0500 (EST) Date: Sun, 15 Nov 1998 19:18:05 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Leif Neland cc: freebsd-current@FreeBSD.ORG Subject: Re: Why doesn't make world make MAKEDEV? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Leif Neland wrote: > > Because its in /etc and that directory never gets touched unless you do a > > make release. DOH! So it is. Ok im done answering ?'s today. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23802 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:19:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23787 for ; Sun, 15 Nov 1998 16:19:14 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA26832; Sun, 15 Nov 1998 17:18:50 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd026815; Sun Nov 15 17:18:47 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA05130; Sun, 15 Nov 1998 17:18:41 -0700 (MST) From: Terry Lambert Message-Id: <199811160018.RAA05130@usr05.primenet.com> Subject: Re: Is it soup yet? :-) To: mike@smith.net.au (Mike Smith) Date: Mon, 16 Nov 1998 00:18:41 +0000 (GMT) Cc: obrien@NUXI.com, current@FreeBSD.ORG In-Reply-To: <199811111937.LAA04505@dingo.cdrom.com> from "Mike Smith" at Nov 11, 98 11:37:01 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It is our history to have buggy NFS. It is our history to have a > bogus kernel module subsystem. It is our history to play catch-up to > Linux. > > The good old days weren't always good, and tomorrow's not as bad as it > seems. Actually, the kernel modules were not bogus given the requirement that we not have a kernel linker because of anti-bloat sentiment, and the fact that they are 8 years old. At the time, they were comparable to the state-of-the-art SunOS techmnology (upon whose design I based their functionality and command line tools). Also, we had kernel modules long before Linux; if anything, FreeBSD played cath-up to NetBSD, since NetBSD was the first BSD to integrate my LKM code. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:21:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24041 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:21:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24036 for ; Sun, 15 Nov 1998 16:21:54 -0800 (PST) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id BAA14546; Mon, 16 Nov 1998 01:21:26 +0100 (CET) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id BAA03809; Mon, 16 Nov 1998 01:08:52 +0100 (MET) (envelope-from wosch) Message-ID: <19981116010851.A3284@panke.de.freebsd.org> Date: Mon, 16 Nov 1998 01:08:51 +0100 From: Wolfram Schneider To: Dmitrij Tejblum Cc: current@FreeBSD.ORG Subject: Re: sort option for find References: <19981115140518.A2166@panke.de.freebsd.org> <199811151626.TAA04794@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199811151626.TAA04794@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Sun, Nov 15, 1998 at 07:26:16PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1998-11-15 19:26:16 +0300, Dmitrij Tejblum wrote: > Sure, but did you noticed that strcmp("foo-1.2.3/Makefile", > "foo/Makefile") < 0? That is, 'find -s' and 'find | sort' give > different results? Is it ok? That is ok for locate. There are no real differences in database size (< 1/10000). Wolfram To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:27:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24535 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:27:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24530 for ; Sun, 15 Nov 1998 16:27:15 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA29353; Sun, 15 Nov 1998 17:26:41 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd029294; Sun Nov 15 17:26:31 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA05395; Sun, 15 Nov 1998 17:26:20 -0700 (MST) From: Terry Lambert Message-Id: <199811160026.RAA05395@usr05.primenet.com> Subject: Re: Is it soup yet? :-) To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Mon, 16 Nov 1998 00:26:20 +0000 (GMT) Cc: green@unixhelp.org, peter@netplex.com.au, julian@whistle.com, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <22697.910843875@zippy.cdrom.com> from "Jordan K. Hubbard" at Nov 11, 98 08:11:15 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Call be crazy, but I think I'd almost like to move the "real" kernel to > > > /boot/kernel, providing the search paths were ok. > > > > You're absolutely nuts. > > Can we get postings in -current back on track? I'm seeing enough > Brian Feldman posts to justify a filter. The "mini FFS" used by the boot blocks doesn't know how to traverse subdirectories. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:29:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24805 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:29:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24786 for ; Sun, 15 Nov 1998 16:29:41 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with ESMTP id SAA29002; Sun, 15 Nov 1998 18:28:38 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Sun, 15 Nov 1998 18:28:38 -0600 (CST) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: Greg Lehey cc: dg@root.com, Kirk McKusick , FreeBSD current users Subject: Re: Today's -CURRENT dies with "ffs_blkfree: bad size" In-Reply-To: <19981116084934.B445@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Greg Lehey wrote: > On Sunday, 15 November 1998 at 7:04:16 -0800, David Greenman wrote: > >>> Anybody else seen this? > >> > >> Greg, > >> > >> I *BELIEVE* this is related to davids changes that he made 2-3 days ago I > >> think. Turning off a sysctl should work I just cant remember which one. > >> David can tell you though. I think it has to do with non standard block > >> sizes on FS's? I might be wrong. > > > > vfs.ffs.doreallocblks=0 will disable the new code. We don't know what is > > causing this yet, but if someone could get a crash dump along with a kernel > > built with -g and make them available on freefall then Kirk McKusick will > > investigate. > > Well, I have a dump and a -g kernel, but it'll take forever to get a > dump to freefall. If Kirk's prepared to debug it locally, he's > welcome. Otherwise be prepared for quite a delay. > > Kirk, let me know. The net connection here's adequate--send me a > master.passwd entry if you want to do it. I just got a "ffs_blkfree: freeing free block" while building a world. Is this related? I've had a considerable amount of instability the last few days, but I can't tell if its a hardware problem, or something introduced into the tree lately. It happens mostly when I'm in X, so I never see a panic, if there is one at all, and only 1 out of 3 times I'll get a coredump to go with it. I do have a coredump + debugging kernel for the above, if anyone wants it. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) ( http://www.freebsd.org ) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:31:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25105 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:31:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25099 for ; Sun, 15 Nov 1998 16:31:40 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id RAA03488; Sun, 15 Nov 1998 17:31:17 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd003473; Sun Nov 15 17:31:13 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA05574; Sun, 15 Nov 1998 17:31:12 -0700 (MST) From: Terry Lambert Message-Id: <199811160031.RAA05574@usr05.primenet.com> Subject: Re: Is it soup yet? :-) To: tlambert@primenet.com (Terry Lambert) Date: Mon, 16 Nov 1998 00:31:12 +0000 (GMT) Cc: mike@smith.net.au, obrien@NUXI.com, current@FreeBSD.ORG In-Reply-To: <199811160018.RAA05130@usr05.primenet.com> from "Terry Lambert" at Nov 16, 98 00:18:41 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, the kernel modules were not bogus given the requirement > that we not have a kernel linker because of anti-bloat sentiment, > and the fact that they are 8 years old. Uh, Terry, you idiot, 98 - 94 is 4, not 8... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:49:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26450 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:49:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26429 for ; Sun, 15 Nov 1998 16:48:56 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id LAA05155; Mon, 16 Nov 1998 11:22:29 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811160022.LAA05155@cimlogic.com.au> Subject: Re: Why doesn't make world make MAKEDEV? In-Reply-To: from Leif Neland at "Nov 16, 98 01:15:20 am" To: leifn@swimsuit.internet.dk (Leif Neland) Date: Mon, 16 Nov 1998 11:22:28 +1100 (EST) Cc: opsys@mail.webspan.net, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > > On Sun, 15 Nov 1998, Open Systems Networking wrote: > > > On Mon, 16 Nov 1998, Leif Neland wrote: > > > > > Any reason why MAKEDEV doesn't get installed by make world? > > > > Because its in /etc and that directory never gets touched unless you do a > > make release. > > > > Well, on my system it is in /dev I think Chris meant to say that it is in src/etc and that was only installed with make release. Now that sendmail.cf comes out of there, I think that MAKEDEV should too. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 16:50:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26677 for freebsd-current-outgoing; Sun, 15 Nov 1998 16:50:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26666; Sun, 15 Nov 1998 16:50:52 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id BAA18686; Mon, 16 Nov 1998 01:45:07 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id BAA39497; Mon, 16 Nov 1998 01:43:33 +0100 (CET) (envelope-from andreas) Message-ID: <19981116014332.A22523@klemm.gtn.com> Date: Mon, 16 Nov 1998 01:43:32 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Cc: asami@FreeBSD.ORG Subject: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! How to resolve/address this ? .... /etc/make.conf has the following knobs: #NOPERL= true #NOSUIDPERL= true Some ports still need perl5 from the ports collection. So I set these options and removed perl5 completely from /usr/bin, /usr/share and /usr/libdata ... What happened now ... a) Can't compile a kernel without perl, because makedevopts.pl needs perlt. b) The perl 5 port for -current isn't compileable. Fails building. BTW, since when we are not able to compile perl5 ????? What happened with FreeBSD ? ;-) What is your recommendation for FreeBSD 3.0 ? Use both perl5 in the system AND perl5 from the ports collection for building and installing other ports ? BTW, the perl5 port doesn't compile and install on a -current system by default, because it's in the base system. Question. Is this ok ? What about the other ports, that usually install themselves into a local directory structure under site_perl. Well, seems a bit tricky. What are your recommendations ? Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 18:56:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05455 for freebsd-current-outgoing; Sun, 15 Nov 1998 18:56:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (mg131-065.ricochet.net [204.179.131.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05450 for ; Sun, 15 Nov 1998 18:56:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA00435; Sun, 15 Nov 1998 18:12:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811160212.SAA00435@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), green@unixhelp.org, peter@netplex.com.au, julian@whistle.com, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Is it soup yet? :-) In-reply-to: Your message of "Mon, 16 Nov 1998 00:26:20 GMT." <199811160026.RAA05395@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Nov 1998 18:11:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The "mini FFS" used by the boot blocks doesn't know how to traverse > subdirectories. Care to be a bit more detailed about this, eg. how it fails, some examples, etc? It doesn't seem to have any trouble with /, /boot and /modules, but I haven't tested it much beyond that. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 19:01:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06272 for freebsd-current-outgoing; Sun, 15 Nov 1998 19:01:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06266 for ; Sun, 15 Nov 1998 19:01:24 -0800 (PST) (envelope-from asami@sunrise.cs.berkeley.edu) Received: from bubble.didi.com (sji-ca36-231.ix.netcom.com [207.92.172.231]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id TAA06194; Sun, 15 Nov 1998 19:00:53 -0800 (PST) Received: (from asami@localhost) by bubble.didi.com (8.8.8/8.8.8) id TAA05380; Sun, 15 Nov 1998 19:00:46 -0800 (PST) (envelope-from asami) Date: Sun, 15 Nov 1998 19:00:46 -0800 (PST) Message-Id: <199811160300.TAA05380@bubble.didi.com> To: dima@tejblum.dnttm.rssi.ru CC: wosch@panke.de.freebsd.org, current@FreeBSD.ORG In-reply-to: <199811151626.TAA04794@tejblum.dnttm.rssi.ru> (message from Dmitrij Tejblum on Sun, 15 Nov 1998 19:26:16 +0300) Subject: Re: sort option for find From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Sure, but did you noticed that strcmp("foo-1.2.3/Makefile", * "foo/Makefile") < 0? That is, 'find -s' and 'find | sort' give * different results? Is it ok? I think it's ok, most of the time the purpose of sorting is just to have one consistent ordering. A warning in the manpage that it may not agree with sort(1) should be enough. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 20:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14161 for freebsd-current-outgoing; Sun, 15 Nov 1998 20:15:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sparcy.delanet.com (sparcy.delanet.com [208.9.136.54]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA14150 for ; Sun, 15 Nov 1998 20:14:55 -0800 (PST) (envelope-from stevec@delanet.com) Received: (qmail 28846 invoked from network); 16 Nov 1998 04:10:02 -0000 Received: from unknown (HELO oemcomputer) (208.9.136.17) by sparcy.delanet.com with SMTP; 16 Nov 1998 04:10:02 -0000 Message-ID: <003301bbd373$83d206e0$118809d0@oemcomputer> From: "Stephen Comoletti" To: Cc: Date: Fri, 15 Nov 1996 23:06:15 -0500 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0030_01BBD349.9A435D40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0030_01BBD349.9A435D40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Need a little help tracking down the cause of a crash. I have a web server setup on a HP Pavilion pentium II/333 with 168 megs ram, a 8gig ata33 ide drive, and lynksys 10bt ether. Nothing paticularly unusual. The install went picture perfect aside from a few probs making bsd recognize the ether card (win95 and 98 both had even harder time finding that darn card, so no surprise). It is a test machine for a new web server we plan to setup. I am using Zeus as a web server. I have basically secured the machine. shut off inetd, use ssh only (1.2.26), and applied the nestea patch to ip_input.c, thats about it. I've run it over 8 to 10 hour periods with occasional reboots as I setup the machine for a week. I put it up for the weekend for the first time, starting it friday evening around 4 and leaving a number of pearl scripts setup to pound away on the web server non stop from other machines in the office. It was taking about 16k hits per hour and didnt seem to notice it. So, sunday evening at 22:52 it crashed with the following: Nov 15 22:52:36 <0.2> somnus /kernel: Nov 15 22:52:37 <0.2> somnus /kernel: Nov 15 22:52:37 <0.2> somnus /kernel: Fatal trap 12: page fault while in kernel mode Nov 15 22:52:37 <0.2> somnus /kernel: fault virtual address = 0x13 Nov 15 22:52:37 <0.2> somnus /kernel: fault code = supervisor read, page not present Nov 15 22:52:37 <0.2> somnus /kernel: instruction pointer = 0x8:0xf015deeb Nov 15 22:52:37 <0.2> somnus /kernel: stack pointer = 0x10:0xf01fcf48 Nov 15 22:52:37 <0.2> somnus /kernel: frame pointer = 0x10:0xf01fcf70 Nov 15 22:52:37 <0.2> somnus /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Nov 15 22:52:37 <0.2> somnus /kernel: = DPL 0, pres 1, def32 1, gran 1 Nov 15 22:52:37 <0.2> somnus /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Nov 15 22:52:37 <0.2> somnus /kernel: current process = Idle Nov 15 22:52:37 <0.2> somnus /kernel: interrupt mask = Nov 15 22:52:37 <0.2> somnus /kernel: trap number = 12 Nov 15 22:52:37 <0.2> somnus /kernel: panic: page fault Nov 15 22:52:37 <0.2> somnus /kernel: Nov 15 22:52:37 <0.2> somnus /kernel: syncing disks... Nov 15 22:52:37 <0.2> somnus /kernel: Nov 15 22:52:37 <0.2> somnus /kernel: Fatal trap 12: page fault while in kernel mode Nov 15 22:52:37 <0.2> somnus /kernel: fault virtual address = 0x10 Nov 15 22:52:37 <0.2> somnus /kernel: fault code = supervisor read, page not present Nov 15 22:52:37 <0.2> somnus /kernel: instruction pointer = 0x8:0xf01bad36 Nov 15 22:52:37 <0.2> somnus /kernel: stack pointer = 0x10:0xf01fcbd4 Nov 15 22:52:37 <0.2> somnus /kernel: frame pointer = 0x10:0xf01fcc2c Nov 15 22:52:37 <0.2> somnus /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Nov 15 22:52:37 <0.2> somnus /kernel: = DPL 0, pres 1, def32 1, gran 1 Nov 15 22:52:37 <0.2> somnus /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Nov 15 22:52:37 <0.2> somnus /kernel: current process = Idle Nov 15 22:52:37 <0.2> somnus /kernel: interrupt mask = Nov 15 22:52:37 <0.2> somnus /kernel: trap number = 12 Nov 15 22:52:37 <0.2> somnus /kernel: panic: page fault Nov 15 22:52:37 <0.2> somnus /kernel: Automatic reboot in 15 seconds - press a key on the console to abort Following that was a standard reboot, nothing unusual in the logs. Now I'm not new to bsd but I've never delt with anything quite like this before..I can debug a core, know some C, etc..so if anyone can give a hand tracking this down or perhaps point out how/where to look I'd greatly appreciate it. Also, as I'm not on freebsd-current, if responding please make sure to include me in the cc please? Stephen C. Comoletti DelaNET, Inc. http://www.delanet.com/ PH: (302) 326-5800 FAX: (302) 326-5802 ------=_NextPart_000_0030_01BBD349.9A435D40 Content-Type: text/x-vcard; name="Stephen C. Comoletti.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Stephen C. Comoletti.vcf" BEGIN:VCARD VERSION:2.1 N:Comoletti;Stephen;C. FN:Stephen C. Comoletti ORG:DelaNET, Inc. TITLE:Asst. Systems Administrator TEL;WORK;VOICE:(302) 326-5800 / (888) DELANET TEL;WORK;FAX:(302) 326-5802 ADR;WORK:;;262 Quigley Boulevard;New Castle;DE;19720;USA LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:262 Quigley = Boulevard=3D0D=3D0ANew Castle, DE 19720=3D0D=3D0AUSA URL: URL:http://www.delanet.com/ EMAIL;PREF;INTERNET:stevec@delanet.com REV:19961116T040615Z END:VCARD ------=_NextPart_000_0030_01BBD349.9A435D40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 21:24:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19028 for freebsd-current-outgoing; Sun, 15 Nov 1998 21:24:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19023 for ; Sun, 15 Nov 1998 21:24:22 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (2445 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sun, 15 Nov 1998 21:23:59 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Sun, 15 Nov 1998 21:23:59 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG Subject: kernel make failure in smbus Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout ../../dev/smbus/smbus.c ../../dev/smbus/smbus.c:84: `bus_create_intr_desc' undeclared here (not in a function) ../../dev/smbus/smbus.c:84: initializer element for `smbus_methods[7].desc' is not constant ../../dev/smbus/smbus.c:84: `bus_generic_create_intr' undeclared here (not in a function) ../../dev/smbus/smbus.c:84: initializer element for `smbus_methods[7].func' is not constant ../../dev/smbus/smbus.c:85: `bus_connect_intr_desc' undeclared here (not in a function) ../../dev/smbus/smbus.c:85: initializer element for `smbus_methods[8].desc' is not constant ../../dev/smbus/smbus.c:85: `bus_generic_connect_intr' undeclared here (not in a function) ../../dev/smbus/smbus.c:85: initializer element for `smbus_methods[8].func' is not constant *** Error code 1 Stop. i have what worked the other week, but not this evening # # SMB bus # # System Management Bus support provided by the 'smbus' device. # # Supported devices: # smb standard io # # Supported interfaces: # iicsmb I2C to SMB bridge with any iicbus interface # bktr brooktree848 I2C hardware interface # controller smbus0 device smb0 at smbus? # # I2C Bus # # Philips i2c bus support is provided by the `iicbus' device. # # Supported devices: # ic i2c network interface # iic i2c standard io # iicsmb i2c to smb bridge. Allow i2c i/o with smb commands. # # Supported interfaces: # pcf Philips PCF8584 ISA-bus controller # bktr brooktree848 I2C software interface # # Other: # iicbb generic I2C bit-banging code (needed by lpbb, bktr) # controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? # Brooktree driver has been ported to the new I2C framework. Thus, # you'll need at least iicbus, iicbb and smbus. iic/smb are only needed if you # want to control other I2C slaves connected to the external connector of # some cards. # device bktr0 randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 21:54:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21914 for freebsd-current-outgoing; Sun, 15 Nov 1998 21:54:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sparcy.delanet.com (sparcy.delanet.com [208.9.136.54]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA21738 for ; Sun, 15 Nov 1998 21:54:09 -0800 (PST) (envelope-from stevec@delanet.com) Received: (qmail 13641 invoked from network); 16 Nov 1998 05:49:22 -0000 Received: from unknown (HELO oemcomputer) (208.9.136.17) by sparcy.delanet.com with SMTP; 16 Nov 1998 05:49:22 -0000 Message-ID: <007c01be1124$532b6400$118809d0@oemcomputer> From: "Stephen Comoletti" To: , Subject: Crash problem with new 3.0 release system. Date: Mon, 16 Nov 1998 00:45:31 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Apologies to all for the repost. Neglected to add a subject and which version of bsd I was using in my last post. -----Original Message----- From: Stephen Comoletti To: freebsd-questions@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Date: Friday, November 15, 1996 11:06 PM >Need a little help tracking down the cause of a crash. I have a web server >setup on a HP Pavilion pentium II/333 with 168 megs ram, a 8gig ata33 ide >drive, and lynksys 10bt ether. Nothing paticularly unusual. The install went >picture perfect aside from a few probs making bsd recognize the ether card >(win95 and 98 both had even harder time finding that darn card, so no >surprise). It is a test machine for a new web server we plan to setup. I am >using Zeus as a web server. I have basically secured the machine. shut off >inetd, use ssh only (1.2.26), and applied the nestea patch to ip_input.c, thats >about it. I've run it over 8 to 10 hour periods with occasional reboots as I >setup the machine for a week. I put it up for the weekend for the first time, >starting it friday evening around 4 and leaving a number of pearl scripts setup >to pound away on the web server non stop from other machines in the office. It >was taking about 16k hits per hour and didnt seem to notice it. > >So, sunday evening at 22:52 it crashed with the following: > >Nov 15 22:52:36 <0.2> somnus /kernel: >Nov 15 22:52:37 <0.2> somnus /kernel: >Nov 15 22:52:37 <0.2> somnus /kernel: Fatal trap 12: page fault while in kernel >mode >Nov 15 22:52:37 <0.2> somnus /kernel: fault virtual address = 0x13 >Nov 15 22:52:37 <0.2> somnus /kernel: fault code = supervisor >read, page not present >Nov 15 22:52:37 <0.2> somnus /kernel: instruction pointer = >0x8:0xf015deeb >Nov 15 22:52:37 <0.2> somnus /kernel: stack pointer = >0x10:0xf01fcf48 >Nov 15 22:52:37 <0.2> somnus /kernel: frame pointer = >0x10:0xf01fcf70 >Nov 15 22:52:37 <0.2> somnus /kernel: code segment = base 0x0, >limit 0xfffff, type 0x1b >Nov 15 22:52:37 <0.2> somnus /kernel: = DPL 0, pres 1, def32 1, gran 1 >Nov 15 22:52:37 <0.2> somnus /kernel: processor eflags = interrupt enabled, >resume, IOPL = 0 >Nov 15 22:52:37 <0.2> somnus /kernel: current process = Idle >Nov 15 22:52:37 <0.2> somnus /kernel: interrupt mask = >Nov 15 22:52:37 <0.2> somnus /kernel: trap number = 12 >Nov 15 22:52:37 <0.2> somnus /kernel: panic: page fault >Nov 15 22:52:37 <0.2> somnus /kernel: >Nov 15 22:52:37 <0.2> somnus /kernel: syncing disks... >Nov 15 22:52:37 <0.2> somnus /kernel: >Nov 15 22:52:37 <0.2> somnus /kernel: Fatal trap 12: page fault while in kernel >mode >Nov 15 22:52:37 <0.2> somnus /kernel: fault virtual address = 0x10 >Nov 15 22:52:37 <0.2> somnus /kernel: fault code = supervisor >read, page not present >Nov 15 22:52:37 <0.2> somnus /kernel: instruction pointer = >0x8:0xf01bad36 >Nov 15 22:52:37 <0.2> somnus /kernel: stack pointer = >0x10:0xf01fcbd4 >Nov 15 22:52:37 <0.2> somnus /kernel: frame pointer = >0x10:0xf01fcc2c >Nov 15 22:52:37 <0.2> somnus /kernel: code segment = base 0x0, >limit 0xfffff, type 0x1b >Nov 15 22:52:37 <0.2> somnus /kernel: = DPL 0, pres 1, def32 1, gran 1 >Nov 15 22:52:37 <0.2> somnus /kernel: processor eflags = interrupt enabled, >resume, IOPL = 0 >Nov 15 22:52:37 <0.2> somnus /kernel: current process = Idle >Nov 15 22:52:37 <0.2> somnus /kernel: interrupt mask = >Nov 15 22:52:37 <0.2> somnus /kernel: trap number = 12 >Nov 15 22:52:37 <0.2> somnus /kernel: panic: page fault >Nov 15 22:52:37 <0.2> somnus /kernel: Automatic reboot in 15 seconds - press a >key on the console to > abort > >Following that was a standard reboot, nothing unusual in the logs. Now I'm not >new to bsd but I've never delt with anything quite like this before..I can >debug a core, know some C, etc..so if anyone can give a hand tracking this down >or perhaps point out how/where to look I'd greatly appreciate it. > >Also, as I'm not on freebsd-current, if responding please make sure to include >me in the cc please? > >Stephen C. Comoletti >DelaNET, Inc. http://www.delanet.com/ >PH: (302) 326-5800 FAX: (302) 326-5802 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 21:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22047 for freebsd-current-outgoing; Sun, 15 Nov 1998 21:56:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-17.dialip.mich.net [192.195.231.219]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA22008 for ; Sun, 15 Nov 1998 21:55:27 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811160555.VAA22008@hub.freebsd.org> Received: (qmail 486 invoked from smtpd); 16 Nov 1998 05:53:30 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 16 Nov 1998 05:53:30 -0000 Date: Mon, 16 Nov 1998 00:53:29 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: kernel make failure in smbus To: randy@psg.com cc: freebsd-current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 15 Nov, Randy Bush wrote: > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout ../../dev/smbus/smbus.c > ../../dev/smbus/smbus.c:84: `bus_create_intr_desc' undeclared here (not in a function) > ../../dev/smbus/smbus.c:84: initializer element for `smbus_methods[7].desc' is not constant > ../../dev/smbus/smbus.c:84: `bus_generic_create_intr' undeclared here (not in a function) > ../../dev/smbus/smbus.c:84: initializer element for `smbus_methods[7].func' is not constant > ../../dev/smbus/smbus.c:85: `bus_connect_intr_desc' undeclared here (not in a function) > ../../dev/smbus/smbus.c:85: initializer element for `smbus_methods[8].desc' is not constant > ../../dev/smbus/smbus.c:85: `bus_generic_connect_intr' undeclared here (not in a function) > ../../dev/smbus/smbus.c:85: initializer element for `smbus_methods[8].func' is not constant > *** Error code 1 > a quick-and-dirty way of making those messages disappear is to comment out the offending lines (similar errors will occur in the iicbus.c file as well) -- i did that and the tv seems to still work fine. note that i do not take responsibility if your machine goes up in flames as a result :) enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 22:07:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22790 for freebsd-current-outgoing; Sun, 15 Nov 1998 22:07:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22760; Sun, 15 Nov 1998 22:07:05 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:p0pFRD6WlHspFLp6P07tqNCZekUbj/bH@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id IAA11766; Mon, 16 Nov 1998 08:06:36 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:pWC2n8zNBw5Ik538+TfDf8OriRmaDMRf@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id IAA04093; Mon, 16 Nov 1998 08:06:34 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811160606.IAA04093@greenpeace.grondar.za> To: Andreas Klemm cc: current@FreeBSD.ORG, asami@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? In-Reply-To: Your message of " Mon, 16 Nov 1998 01:43:32 +0100." <19981116014332.A22523@klemm.gtn.com> References: <19981116014332.A22523@klemm.gtn.com> Date: Mon, 16 Nov 1998 08:06:32 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The intention is to use "system" perl for everything. If a port breaks, then fix that port. :-) M Andreas Klemm wrote: > Hi ! > > How to resolve/address this ? .... > > /etc/make.conf has the following knobs: > #NOPERL= true > #NOSUIDPERL= true > > Some ports still need perl5 from the ports collection. > So I set these options and removed perl5 completely from /usr/bin, > /usr/share and /usr/libdata ... > > What happened now ... > > a) Can't compile a kernel without perl, because makedevopts.pl needs > perlt. > > b) The perl 5 port for -current isn't compileable. Fails building. > BTW, since when we are not able to compile perl5 ????? What > happened with FreeBSD ? ;-) > > What is your recommendation for FreeBSD 3.0 ? > > Use both perl5 in the system AND perl5 from the ports collection > for building and installing other ports ? > > BTW, the perl5 port doesn't compile and install on a -current > system by default, because it's in the base system. > > Question. Is this ok ? What about the other ports, that usually > install themselves into a local directory structure under site_perl. > > Well, seems a bit tricky. What are your recommendations ? > > Andreas /// > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > What gives you 90% more speed, for example, in kernel compilation ? > http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html > "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 22:15:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23701 for freebsd-current-outgoing; Sun, 15 Nov 1998 22:15:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23694 for ; Sun, 15 Nov 1998 22:15:30 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id HAA08844 for current@FreeBSD.ORG; Mon, 16 Nov 1998 07:14:57 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 09D061514; Mon, 16 Nov 1998 07:06:33 +0100 (CET) Date: Mon, 16 Nov 1998 07:06:33 +0100 From: Ollivier Robert To: current@FreeBSD.ORG Subject: Re: newer gcc? Message-ID: <19981116070633.A13428@keltia.freenix.fr> Mail-Followup-To: current@FreeBSD.ORG References: <199811152328.QAA03497@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <199811152328.QAA03497@usr05.primenet.com>; from Terry Lambert on Sun, Nov 15, 1998 at 11:28:51PM +0000 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4805 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Terry Lambert: > unless you compile it with threading enabled (unlike g++ 2.8.1, you > must choose threading or no threading for resulting binaries at the > time you compile the compiler, not at the time you compile the > program). Last time I looked at a generic gcc 2.8.1, it also required you to specify --enable-threads for configure. Are you really sure about this big difference between egcs & gcc ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 22:19:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23908 for freebsd-current-outgoing; Sun, 15 Nov 1998 22:19:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23903 for ; Sun, 15 Nov 1998 22:19:19 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca36-231.ix.netcom.com [207.92.172.231]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id WAA06408; Sun, 15 Nov 1998 22:18:47 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id WAA00540; Sun, 15 Nov 1998 22:18:44 -0800 (PST) Date: Sun, 15 Nov 1998 22:18:44 -0800 (PST) Message-Id: <199811160618.WAA00540@silvia.hip.berkeley.edu> To: mark@grondar.za CC: andreas@klemm.gtn.com, current@FreeBSD.ORG In-reply-to: <199811160606.IAA04093@greenpeace.grondar.za> (message from Mark Murray on Mon, 16 Nov 1998 08:06:32 +0200) Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * The intention is to use "system" perl for everything. * * If a port breaks, then fix that port. :-) That's a little terse, Mark. ;) * > Some ports still need perl5 from the ports collection. If that's the case, either system perl5 is broken or the port is broken, and should be fixed. * > So I set these options and removed perl5 completely from /usr/bin, Don't do that. :) * > BTW, the perl5 port doesn't compile and install on a -current * > system by default, because it's in the base system. It shouldn't, and that's fine. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 22:29:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24870 for freebsd-current-outgoing; Sun, 15 Nov 1998 22:29:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.easystreet.com (easystreet.com [206.26.36.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24863 for ; Sun, 15 Nov 1998 22:29:26 -0800 (PST) (envelope-from ctapang@easystreet.com) Received: from apex (dial-56-032.easystreet.com [206.103.56.32]) by mail.easystreet.com (8.8.7/8.8.7) with SMTP id WAA04424; Sun, 15 Nov 1998 22:29:01 -0800 (PST) Message-ID: <009401be1132$86ffca60$0d787880@apex> From: "Carlos C. Tapang" To: "Annelise Anderson" , Subject: Re: aout-elf-build error: ld-elf.so.1 not found Date: Sun, 15 Nov 1998 23:27:11 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How did you fix it? ---Carlos > >Sorry to have bothered you, it's all working fine now. > >Annelise > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 23:02:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28288 for freebsd-current-outgoing; Sun, 15 Nov 1998 23:02:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28189; Sun, 15 Nov 1998 23:01:59 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem28.masternet.it [194.184.65.38]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id IAA10872; Mon, 16 Nov 1998 08:01:11 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <199811160701.IAA10872@scotty.masternet.it> From: "Gianmarco Giovannelli" To: Mark Murray Date: Mon, 16 Nov 1998 08:08:58 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? Reply-to: gmarco@giovannelli.it CC: current@FreeBSD.ORG, asami@FreeBSD.ORG In-reply-to: <199811160606.IAA04093@greenpeace.grondar.za> References: Your message of " Mon, 16 Nov 1998 01:43:32 +0100." <19981116014332.A22523@klemm.gtn.com> X-mailer: Pegasus Mail for Win32 (v3.01b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The intention is to use "system" perl for everything. > > If a port breaks, then fix that port. :-) I think the situation of the FreeBSD ports now is critical... I have to do some work for University with PostgreSql and I found that on my 3.0-current the following things don't work, even if they are not make broken... postgresql-6.3.2 (it is installed and works, but for example a pg_dumpall doesn't work anymore --> don't find library libpg.so.* ) pgacess (complaying about missing library, which are indeed in the aout subdirs) p5-DBD-Pg (marked broken) p5-Pg (doesn't install) I tried to fix all of them but I find it is a too much difficult task for a newbie like me... so I was planning of installed another 2.2.7-STABLE box to do the work. Any hints, suggestion, cheats ? Thanks very much for attention... Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 23:08:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28886 for freebsd-current-outgoing; Sun, 15 Nov 1998 23:08:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28880 for ; Sun, 15 Nov 1998 23:08:31 -0800 (PST) (envelope-from james@westongold.com) Received: from [158.152.96.124] (helo=wgp01.wgold.demon.co.uk) by post.mail.demon.net with esmtp (Exim 2.05demon1 #1) id 0zfIlZ-0003ll-00; Mon, 16 Nov 1998 07:08:06 +0000 Received: by WGP01 with Internet Mail Service (5.5.1960.3) id ; Fri, 13 Nov 1998 07:16:44 -0000 Message-ID: <32BABEF63EAED111B2C5204C4F4F50201817@WGP01> From: James Mansion To: Poul-Henning Kamp , James Mansion Cc: Tom , Mike Smith , sporkl@ix.netcom.com, freebsd-current@FreeBSD.ORG Subject: RE: SparQ Drive and 3.0 upgrade Date: Fri, 13 Nov 1998 07:16:41 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used to do that, but its rather pricey if you have a lot of toys to try, and the drives seem to get fed up uness you are very kind to them. Since I have 18 month old triplets, I like gear that's tough. Really tough. ;-) James > -----Original Message----- > From: Poul-Henning Kamp [mailto:phk@critter.freebsd.dk] > Sent: Thursday, November 12, 1998 9:10 PM > To: James Mansion > Cc: Tom; Mike Smith; sporkl@ix.netcom.com; freebsd-current@FreeBSD.ORG > Subject: Re: SparQ Drive and 3.0 upgrade > > > In message <32BABEF63EAED111B2C5204C4F4F50201810@WGP01>, > James Mansion writes: > > >Out of interest, is there a 'recommended' high-capacity > >removable device that can be used to boot different OSs on > >a single PC? > > standard hard disk in plastic or metal removable tray ? > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on > their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, > hi-res color terminal > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 23:11:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29435 for freebsd-current-outgoing; Sun, 15 Nov 1998 23:11:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29427 for ; Sun, 15 Nov 1998 23:11:42 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA02792; Mon, 16 Nov 1998 17:41:09 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA01890; Mon, 16 Nov 1998 17:41:08 +1030 (CST) Message-ID: <19981116174108.F1768@freebie.lemis.com> Date: Mon, 16 Nov 1998 17:41:08 +1030 From: Greg Lehey To: Luoqi Chen , FreeBSD-current@FreeBSD.ORG Subject: Re: Today's -CURRENT dies with "ffs_blkfree: bad size" References: <199811151611.LAA09315@lor.watermarkgroup.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811151611.LAA09315@lor.watermarkgroup.com>; from Luoqi Chen on Sun, Nov 15, 1998 at 11:11:37AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 15 November 1998 at 11:11:37 -0500, Luoqi Chen wrote: >> I've just upgraded my kernel to a sup of about 9 hours ago, and have >> had a number of panics. The first ones happened in X, but I finally >> got a dump. Here's a trace: >> >> #0 boot (howto=262400) at ../../kern/kern_shutdown.c:285 >> 285 dumppcb.pcb_cr3 = rcr3(); >> (kgdb) bt >> #0 boot (howto=262400) at ../../kern/kern_shutdown.c:285 >> #1 0xf013e1e5 in panic (fmt=0xf01cc3e1 "ffs_blkfree: bad size") >> at ../../kern/kern_shutdown.c:453 >> #2 0xf01cc53e in ffs_blkfree (ip=0xf1283400, bno=4, size=8192) > ^^^^^ > It could be caused by our delayed bmap binding. Check to see if > bp->b_blkno == bp->b_lblkno for this block. bp isn't initialized at this point. It gets initialized by a call to bread() later in the function. Kirk's currently looking at this, so I'll leave him to report. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 23:26:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00889 for freebsd-current-outgoing; Sun, 15 Nov 1998 23:26:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00779; Sun, 15 Nov 1998 23:25:57 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:R7EJuyvpXywhbNa3e/Xe4+B659iJJvRB@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id JAA11874; Mon, 16 Nov 1998 09:25:16 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:MPFF7cTGhTAMYOKIcID93rZj9J4Xauac@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id JAA04397; Mon, 16 Nov 1998 09:25:15 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811160725.JAA04397@greenpeace.grondar.za> To: gmarco@giovannelli.it cc: current@FreeBSD.ORG, asami@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? In-Reply-To: Your message of " Mon, 16 Nov 1998 08:08:58 +0100." <199811160701.IAA10872@scotty.masternet.it> References: Your message of " Mon, 16 Nov 1998 01:43:32 +0100." <19981116014332.A22523@klemm.gtn.com> <199811160701.IAA10872@scotty.masternet.it> Date: Mon, 16 Nov 1998 09:25:10 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Gianmarco Giovannelli" wrote: > I have to do some work for University with PostgreSql and I found > that on my 3.0-current the following things don't work, even if they > are not make broken... > > postgresql-6.3.2 (it is installed and works, but for example a > pg_dumpall doesn't work anymore --> don't find library libpg.so.* ) > > pgacess (complaying about missing library, which are indeed in the > aout subdirs) > > p5-DBD-Pg (marked broken) > > p5-Pg (doesn't install) Sounds like we need to nag the PostgreSQL team a bit.... > I tried to fix all of them but I find it is a too much difficult task for a > newbie like me... so I was planning of installed another 2.2.7-STABLE > box to do the work. > > Any hints, suggestion, cheats ? A 2.2.7 box will probably be the right way to go. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 15 23:51:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04103 for freebsd-current-outgoing; Sun, 15 Nov 1998 23:51:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA04087; Sun, 15 Nov 1998 23:51:12 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id IAA27669; Mon, 16 Nov 1998 08:45:17 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id IAA07427; Mon, 16 Nov 1998 08:30:47 +0100 (CET) (envelope-from andreas) Message-ID: <19981116083046.A4393@klemm.gtn.com> Date: Mon, 16 Nov 1998 08:30:46 +0100 From: Andreas Klemm To: Satoshi Asami , mark@grondar.za Cc: current@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? References: <199811160606.IAA04093@greenpeace.grondar.za> <199811160618.WAA00540@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811160618.WAA00540@silvia.hip.berkeley.edu>; from Satoshi Asami on Sun, Nov 15, 1998 at 10:18:44PM -0800 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 15, 1998 at 10:18:44PM -0800, Satoshi Asami wrote: > * > So I set these options and removed perl5 completely from /usr/bin, > > Don't do that. :) > > * > BTW, the perl5 port doesn't compile and install on a -current > * > system by default, because it's in the base system. > > It shouldn't, and that's fine. So, if perl5 from the base system is definitively needed, then I'd vote to remove the misleading options from /etc/make.conf #NOPERL= true #NOSUIDPERL= true and in the Makefiles where they would take effect. Or what do you think ? Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 00:19:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06572 for freebsd-current-outgoing; Mon, 16 Nov 1998 00:19:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from marathon.tekla.fi (marathon.tekla.fi [192.98.7.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06566 for ; Mon, 16 Nov 1998 00:19:14 -0800 (PST) (envelope-from sja@tekla.fi) Received: from poveri.tekla.fi (poveri.tekla.fi [192.98.7.19]) by marathon.tekla.fi (8.8.7/8.8.7) with SMTP id KAA09333; Mon, 16 Nov 1998 10:18:45 +0200 From: Sakari Jalovaara Received: by poveri.tekla.fi; (5.65v3.2/1.1.8.2/20Aug96-0557PM) id AA20583; Mon, 16 Nov 1998 10:18:58 +0200 Date: Mon, 16 Nov 1998 10:18:58 +0200 Message-Id: <9811160818.AA20583@poveri.tekla.fi> To: ade@supernews.net Cc: current@FreeBSD.ORG, sos@freebsd.dk Subject: Re: ATAPI CD/R driver and Mitsumi CR-2600TE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >..> acd0: rezero failed I see this with an HP 8100 burner - apparently REZERO isn't supported. A hack around it is to use START instead of REZERO. The doc for an older HP model says those two commands are equivalent. In sys/i386/isa/atapi-cd.c: static int acd_rezero_unit(struct acd *cdp) { #if 0 return acd_request_wait(cdp, ATAPI_REZERO_UNIT, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0); #else return acd_request_wait(cdp, ATAPI_START_STOP, 1, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0); #endif } >>>> acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,0,0,0,0,0,0,0,0 ); >>>> acd_request_wait( ..., ATAPI_START_STOP, 1,0,0,1,0,0,0,0,0,0,0 ); > Hmm.. well, I tried that.. it failed on the first acd_request_wait > (for the CDIOCSTOP equivalent), left the disk spinning inside the drive, > and I couldn't get the disk out unless I halted the machine and hit > the physical eject button whilst the machine was at the BIOS. Try it with just the second (start) request. ++sja To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 00:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07909 for freebsd-current-outgoing; Mon, 16 Nov 1998 00:32:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07901 for ; Mon, 16 Nov 1998 00:32:45 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA01081; Mon, 16 Nov 1998 08:31:51 GMT Date: Mon, 16 Nov 1998 08:31:50 +0000 (GMT) From: Doug Rabson To: Terry Lambert cc: "Jordan K. Hubbard" , green@unixhelp.org, peter@netplex.com.au, julian@whistle.com, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Is it soup yet? :-) In-Reply-To: <199811160026.RAA05395@usr05.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Terry Lambert wrote: > > > > Call be crazy, but I think I'd almost like to move the "real" kernel to > > > > /boot/kernel, providing the search paths were ok. > > > > > > You're absolutely nuts. > > > > Can we get postings in -current back on track? I'm seeing enough > > Brian Feldman posts to justify a filter. > > The "mini FFS" used by the boot blocks doesn't know how to traverse > subdirectories. Actually it does. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 00:49:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09009 for freebsd-current-outgoing; Mon, 16 Nov 1998 00:49:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09004 for ; Mon, 16 Nov 1998 00:49:52 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA21007; Mon, 16 Nov 1998 09:44:10 +0100 (CET) To: Open Systems Networking cc: Leif Neland , freebsd-current@FreeBSD.ORG Subject: Re: Why doesn't make world make MAKEDEV? In-reply-to: Your message of "Sun, 15 Nov 1998 18:59:46 EST." Date: Mon, 16 Nov 1998 09:44:10 +0100 Message-ID: <21005.911205850@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Open S ystems Networking writes: >On Mon, 16 Nov 1998, Leif Neland wrote: > >> Any reason why MAKEDEV doesn't get installed by make world? > >Because its in /etc and that directory never gets touched unless you do a >make release. It's actually in /dev, and I don't see a good reason why it isn't... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 00:51:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09326 for freebsd-current-outgoing; Mon, 16 Nov 1998 00:51:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09321 for ; Mon, 16 Nov 1998 00:51:04 -0800 (PST) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.8.8/8.8.8) with SMTP id CAA22498 for ; Mon, 16 Nov 1998 02:50:40 -0600 (CST) (envelope-from tony@dell.com) Message-Id: <3.0.3.32.19981116025037.03461374@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.3 (32) Date: Mon, 16 Nov 1998 02:50:37 -0600 To: current@FreeBSD.ORG From: Tony Overfield Subject: mail -u Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there some trick for getting "mail -u" to work with -current? Logged in as "root" and running "mail -u tony" gets this (paraphrased and shortened): [...] mail NAMI "/var/mail/root" mail RET open -1 errno 2 No such file or directory mail CALL write(0x2, "No mail for tony\n", 0x11) [...] "mail -f /var/mail/tony" works correctly on -current and "mail -u tony" works on my -stable system. I apologize if I'm sending to the wrong list. Please advise. - Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 01:08:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10627 for freebsd-current-outgoing; Mon, 16 Nov 1998 01:08:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10594 for ; Mon, 16 Nov 1998 01:07:45 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru (8.9.1a.NOMIME/8.9.1) with ESMTP id LAA05549 for ; Mon, 16 Nov 1998 11:37:19 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Mon, 16 Nov 1998 11:37:09 +0300 (MSK) From: "Roman V. Palagin" To: current@FreeBSD.ORG Subject: IPv6 and -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Is there are any implementation of IPv6 for FreeBSD-current? I remember about Pierre Beyssac's INRIA-based distribution (ftp://frmug.org/pub/ipv6) , but the last patch was for 1998/05/27 kernel :( ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 01:16:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11238 for freebsd-current-outgoing; Mon, 16 Nov 1998 01:16:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (surf11.cruzers.com [205.215.232.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA11233 for ; Mon, 16 Nov 1998 01:16:22 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 1261 invoked by uid 100); 16 Nov 1998 09:15:37 -0000 Date: Mon, 16 Nov 1998 01:15:37 -0800 To: freebsd-current@FreeBSD.ORG Subject: pcm0 A/V sync off after unusual behavior w/xanim Message-ID: <19981116011537.A1173@top.worldcontrol.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.9i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my laptop, Chembook 9780 P5/233MMX 64MB with yamaha 715 audio chipset, and the pcm0 audio driver, running -current I occasionally get into a state where the audio is out of sync with the video using xanim. Most of the time things work correctly. However, I have noticed the following behavior: I run a script, which does for i in $1.mov ; do xanim +Ae +Ze -Zr +p +f $i done Sometimes I ^C my way out of the program. Usually the ^C is captured by the running xanim, and does not kill the shell script. So I type many ^C's and eventually either hit all the spawned xanim's or hit the shell and things stop. Sometimes after doing this, and then using xanim again, I find the audio is out of sync with the video. The audio is generally about 1000ms late. Nothing helps, except a reboot. Back in the old days when I used the sb0 driver, I had never noticed this behavior. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 01:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11477 for freebsd-current-outgoing; Mon, 16 Nov 1998 01:21:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11472 for ; Mon, 16 Nov 1998 01:21:51 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.Stanford.EDU [127.0.0.1]) by andrsn.stanford.edu (8.9.1/8.9.1) with SMTP id BAA22775; Mon, 16 Nov 1998 01:21:15 -0800 (PST) Date: Mon, 16 Nov 1998 01:21:15 -0800 (PST) From: Annelise Anderson To: "Carlos C. Tapang" cc: freebsd-current@FreeBSD.ORG Subject: Re: aout-elf-build error: ld-elf.so.1 not found In-Reply-To: <009401be1132$86ffca60$0d787880@apex> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Nov 1998, Carlos C. Tapang wrote: > How did you fix it? > ---Carlos Apparently the error is not significant. Both rc.conf and rc need library path information from the new files, but one path that's listed as an elf library path has aout libraries, which I've been adding with ldconfig -aout -m /usr/local/lib. This allows X to run. I can, of course, change the library configuration paths or move the libraries. Although I got a message that it would probably not be necessary to rebuilt the kernel, in fact it was necessary to correct the errors in ps and top (and others), and to make it possible for WordPerfect 7 (linux) to run. I discovered that my old kernel with sd scsi stuff in it worked fine with the "da" names in fstab; and a new kernel with using the new da options didn't need the CAM lines to work. The mistake I made the first time was not making the da devices in enough depth to get all the partitions fstab was trying to mount, i.e., da0, da0s1, da0s2, da0s1a, da0s2a, and similarly for da1. In fact there are probably 100 messages in -current on each of these topics....and a comparable number on boot blocks, elf kernels, and building software, none of which I have yet addressed. Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 01:25:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11751 for freebsd-current-outgoing; Mon, 16 Nov 1998 01:25:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11734 for ; Mon, 16 Nov 1998 01:25:47 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id KAA16982 for ; Mon, 16 Nov 1998 10:31:18 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Mon, 16 Nov 1998 10:31:17 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: Probing devices in bootloader Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I have a (possibly) interesting idea, and I'd like to share it with you. With the advent of the new booloader, I think it's possible now to do device probing from inside the bootloader. Let's suppose that each kernel module would have a special initialization section, which could be used in BTX environment. After all, most probing is just checking for the presence of some signatures at given locations, and this can easily be done in BTX environment, right? Then, once the device has been successfuly probed, we could discard this section when loading it. This special init section would be probably of no use when running normal system, so that a kernel module would contain two of them - one for the normal operation, and one for the initial BTX enviroment. What this would buy us? IMHO, ability to check very early what devices are present, and to load appropriate modules only for them. It could be possible to build quite sophisticated multi-variant scenarios with alternative configurations based on the results of probing. It could also help to avoid memory fragmentation when loading/unloading modules, etc, etc.. Now what\s your opinion on this? Especially those of you who nkow the workings of BTX, kernel modules, and the booting process much better than I do... :-) Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 01:35:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12889 for freebsd-current-outgoing; Mon, 16 Nov 1998 01:35:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-43-dbn.dial-up.net [196.34.155.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12880 for ; Mon, 16 Nov 1998 01:35:50 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA00413; Mon, 16 Nov 1998 11:34:34 +0200 (SAT) From: Robert Nordier Message-Id: <199811160934.LAA00413@ceia.nordier.com> Subject: Re: mail -u In-Reply-To: <3.0.3.32.19981116025037.03461374@bugs.us.dell.com> from Tony Overfield at "Nov 16, 98 02:50:37 am" To: tony@dell.com (Tony Overfield) Date: Mon, 16 Nov 1998 11:34:30 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Overfield wrote: > > Is there some trick for getting "mail -u" to work with -current? > > Logged in as "root" and running "mail -u tony" gets this > (paraphrased and shortened): > > [...] > mail NAMI "/var/mail/root" > mail RET open -1 errno 2 No such file or directory > mail CALL write(0x2, "No mail for tony\n", 0x11) > [...] > > "mail -f /var/mail/tony" works correctly on -current and > "mail -u tony" works on my -stable system. > > I apologize if I'm sending to the wrong list. Please advise. It's a reported bug PR 8665. A workaround is to unsetenv MAIL. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 02:33:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA18187 for freebsd-current-outgoing; Mon, 16 Nov 1998 02:33:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-40-dbn.dial-up.net [196.34.155.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA18141 for ; Mon, 16 Nov 1998 02:33:38 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id MAA00785; Mon, 16 Nov 1998 12:32:07 +0200 (SAT) From: Robert Nordier Message-Id: <199811161032.MAA00785@ceia.nordier.com> Subject: Re: Probing devices in bootloader In-Reply-To: from Andrzej Bialecki at "Nov 16, 98 10:31:17 am" To: abial@nask.pl (Andrzej Bialecki) Date: Mon, 16 Nov 1998 12:32:04 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > Hi all, > > I have a (possibly) interesting idea, and I'd like to share it with you. > > With the advent of the new booloader, I think it's possible now to do > device probing from inside the bootloader. Let's suppose that each kernel > module would have a special initialization section, which could be used in > BTX environment. After all, most probing is just checking for the presence > of some signatures at given locations, and this can easily be done in BTX > environment, right? Some probing is a fair bit more complex than this (see src/sys/isa/sio.c, for example). Currently, BTX is not sophisticated enough to handle various requirements (for instance, the interrupt flag is not virtualized; and interrupts can't be disabled in ring 3). Of course, this doesn't mean it couldn't be done, by enhancing BTX, if we decided this was the route to take. BTX is currently constrained by being needed both for the boot blocks and the boot loader. And the boot blocks can't accommodate much more than BTX's present size of 1744 bytes. So adding further capabilities to BTX would probably require two separate versions. Conditional assembly, by means of #ifdefs or the m4 equivalent, doesn't usually work well for this kind of code; either space efficiency is lost, or things become *extremely* messy. Doing something roughly along these lines has already been been discussed off the lists. > Then, once the device has been successfuly probed, we could discard this > section when loading it. This special init section would be probably of no > use when running normal system, so that a kernel module would contain two > of them - one for the normal operation, and one for the initial BTX > enviroment. A couple of reasons why this may not be a good idea: o It would tend to introduce an architectural change along very hardware-dependent lines (and the BTX environment is deliberately very i386-specific). o As far as debugging is concerned, BTX is fairly minimalist; and can be tiresome to work in. It also requires more familiarity with Intel CPU minutia than many developers have or even want. > What this would buy us? IMHO, ability to check very early what devices are > present, and to load appropriate modules only for them. It could be > possible to build quite sophisticated multi-variant scenarios with > alternative configurations based on the results of probing. It could also > help to avoid memory fragmentation when loading/unloading modules, etc, > etc.. > > Now what\s your opinion on this? Especially those of you who nkow the > workings of BTX, kernel modules, and the booting process much better than > I do... :-) I think it's an interesting possibility, and may be worth exploring. In principle, one could even speed up the boot process (eg. SCSI_DELAY) by doing certain things much earlier, and even in parallel. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 03:17:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23070 for freebsd-current-outgoing; Mon, 16 Nov 1998 03:17:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from roam.psg.com (roam.psg.com [147.28.2.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA23065 for ; Mon, 16 Nov 1998 03:17:21 -0800 (PST) (envelope-from randy@psg.com) Received: by roam.psg.com id m0zfMeP-000014C; Mon, 16 Nov 1998 03:16:57 -0800 (PST) (Smail3.2.0.96#1) Message-Id: Date: Mon, 16 Nov 1998 03:16:57 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG Subject: disk panics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i am getting disk panics (CAM ccd scsi) in -CURRENT of sunday evening. it is bad enough (buildworld exacerbates it badly) that i will probably have to do a partial build to get it fixed enough to do a full build. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 03:52:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26278 for freebsd-current-outgoing; Mon, 16 Nov 1998 03:52:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA26265; Mon, 16 Nov 1998 03:52:12 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:ukhaLRX5EYGyx3/9vYYiPAmzCVQKYJRR@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id NAA12241; Mon, 16 Nov 1998 13:51:29 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:NmE7+ZNs3AMvBZ1JFxzaCsvBSJBxHdo4@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id NAA00668; Mon, 16 Nov 1998 13:51:28 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811161151.NAA00668@greenpeace.grondar.za> To: Andreas Klemm cc: Satoshi Asami , current@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? In-Reply-To: Your message of " Mon, 16 Nov 1998 08:30:46 +0100." <19981116083046.A4393@klemm.gtn.com> References: <199811160606.IAA04093@greenpeace.grondar.za> <199811160618.WAA00540@silvia.hip.berkeley.edu> <19981116083046.A4393@klemm.gtn.com> Date: Mon, 16 Nov 1998 13:51:12 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andreas Klemm wrote: > So, if perl5 from the base system is definitively needed, > then I'd vote to remove the misleading options from /etc/make.conf > > #NOPERL= true > #NOSUIDPERL= true > > and in the Makefiles where they would take effect. The second one can stay, but I cannot think of a use for the first; you make world; you have no perl; you need to build a kernel - oops! I suppose this is an argument for not depending on Perl. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 05:36:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10565 for freebsd-current-outgoing; Mon, 16 Nov 1998 05:36:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10560 for ; Mon, 16 Nov 1998 05:36:57 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id FAA18834; Mon, 16 Nov 1998 05:37:18 -0800 (PST) Message-Id: <199811161337.FAA18834@root.com> To: Randy Bush cc: freebsd-current@FreeBSD.ORG Subject: Re: disk panics In-reply-to: Your message of "Mon, 16 Nov 1998 03:16:57 PST." From: David Greenman Reply-To: dg@root.com Date: Mon, 16 Nov 1998 05:37:18 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >i am getting disk panics (CAM ccd scsi) in -CURRENT of sunday evening. > >it is bad enough (buildworld exacerbates it badly) that i will probably have >to do a partial build to get it fixed enough to do a full build. The temporary solution is "sysctl -w vfs.ffs.doreallocblks=0". A correct fix will be committed soon. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 06:07:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13284 for freebsd-current-outgoing; Mon, 16 Nov 1998 06:07:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13275 for ; Mon, 16 Nov 1998 06:07:31 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id PAA01919 for freebsd-current@freebsd.org; Mon, 16 Nov 1998 15:07:00 +0100 (CET) (envelope-from des) Date: Mon, 16 Nov 1998 15:07:00 +0100 (CET) Message-Id: <199811161407.PAA01919@flood.ping.uio.no> To: freebsd-current@FreeBSD.ORG From: des@ping.uio.no Subject: 3.0 panic Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's a backtrace from a panic I had last night on a 3.0 box. It used to run -stable and has never panicked before AFAIR; I upgraded it to -current last week when I got it colocated. I suspect the panic was caused by overheating, since it doesn't make sense that it should panic in rename() and it was stuck between an ND Uniline 88/20 and a fridge (don't ask). OBTW, it's an Elf kernel. 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.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc...(no debugging symbols found)... IdlePTD 2392064 initial pcb at 1f0634 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x7c fault code = supervisor read, page not present instruction pointer = 0x8:0xf19f4714 stack pointer = 0x10:0xf4f55e7c frame pointer = 0x10:0xf4f55e94 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 = 57518 (mv) interrupt mask = panic: from debugger Fatal trap 12: page fault while in kernel mode fault virtual address = 0x7c fault code = supervisor read, page not present instruction pointer = 0x8:0xf19f4714 stack pointer = 0x10:0xf4f55e7c frame pointer = 0x10:0xf4f55e94 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 = 57518 (mv) interrupt mask = Fatal trap 12: page fault while in kernel mode fault virtual address = 0x7c fault code = supervisor read, page not present instruction pointer = 0x8:0xf19f4714 stack pointer = 0x10:0xf4f55e7c frame pointer = 0x10:0xf4f55e94 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 = 57518 (mv) interrupt mask = panic: from debugger dumping to dev 20001, offset 458752 dump 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 0xf012e0bb in boot () (kgdb) #0 0xf012e0bb in boot () #1 0xf012e354 in at_shutdown () #2 0xf011716d in db_panic () #3 0xf011710d in db_command () #4 0xf01171d2 in db_command_loop () #5 0xf0119533 in db_trap () #6 0xf019567d in kdb_trap () #7 0xf019f207 in trap_fatal () #8 0xf019eef8 in trap_pfault () #9 0xf019eb13 in trap () #10 0xf19f4714 in ?? () #11 0xf015143e in rename () #12 0xf019f42b in syscall () #13 0xf0195fcc in Xint0x80_syscall () #14 0x8048305 in ?? () #15 0x80480c9 in ?? () (kgdb) Here's the kernel config: # Kernel configuration for flood.ping.uio.no # General options machine "i386" cpu "I586_CPU" ident flood config kernel root on da0 maxusers 64 # Networking options "INET" options "IPFIREWALL" options "IPFIREWALL_VERBOSE" options "NMBCLUSTERS=8192" # File system options "FDESC" options "FFS" options "FFS_ROOT" options "PROCFS" options "SOFTUPDATES" # Misc. kernel options options "AUTO_EOI_1" options "AUTO_EOI_2" options "COMPAT_43" options "DDB" options "INCLUDE_CONFIG_FILE" options "USERCONFIG" options "VISUAL_USERCONFIG" # Buses controller isa0 controller pci0 controller pnp0 # Numeric processor extensions device npx0 at isa? port "IO_NPX" irq 13 # Floppy controller controller fdc0 at isa? disable port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 # EIDE controllers controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 flags 0x80ff # System console and mouse device sc0 at isa? port "IO_KBD" tty irq 1 options "MAXCONS=12" options "SC_HISTORY_SIZE=4096" options "MSGBUF_SIZE=32768" # I/O ports device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 controller ppbus0 device nlpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? # Network adapters device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 # Networking pseudo-devices pseudo-device loop pseudo-device ether pseudo-device tun 4 pseudo-device bpfilter 4 # Other pseudo-devices pseudo-device gzip pseudo-device pty 64 pseudo-device vn 4 # Sound hardware (Luigi Rizzo) device pcm0 at isa? port? tty irq 7 drq 1 flags 0x15 DES -- Dag-Erling Smørgrav - des@ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 06:22:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA14766 for freebsd-current-outgoing; Mon, 16 Nov 1998 06:22:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from qix (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA14758 for ; Mon, 16 Nov 1998 06:22:41 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.1/8.8.7) id PAA00612; Mon, 16 Nov 1998 15:23:11 +0100 (MET) Date: Mon, 16 Nov 1998 15:23:11 +0100 (MET) Message-Id: <199811161423.PAA00612@qix> X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f From: Jean-Marc Zucconi To: tony@dell.com CC: current@FreeBSD.ORG In-reply-to: <3.0.3.32.19981116025037.03461374@bugs.us.dell.com> (message from Tony Overfield on Mon, 16 Nov 1998 02:50:37 -0600) Subject: Re: mail -u X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Tony Overfield writes: > Is there some trick for getting "mail -u" to work with -current? You must unset the MAIL env. variable. Or recompile mail with the following patch: Index: main.c =================================================================== RCS file: /home/ncvs/src/usr.bin/mail/main.c,v retrieving revision 1.5 diff -u -r1.5 main.c --- main.c 1998/01/02 16:43:50 1.5 +++ main.c 1998/01/04 07:17:27 @@ -110,6 +110,7 @@ * Next argument is person to pretend to be. */ myname = optarg; + unsetenv("MAIL"); break; case 'i': /* Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 06:37:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16313 for freebsd-current-outgoing; Mon, 16 Nov 1998 06:37:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16301; Mon, 16 Nov 1998 06:37:13 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA01427; Mon, 16 Nov 1998 09:36:05 -0500 (EST) Date: Mon, 16 Nov 1998 09:36:05 -0500 (EST) From: John Fieber To: gmarco@giovannelli.it cc: Mark Murray , current@FreeBSD.ORG, asami@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? In-Reply-To: <199811160701.IAA10872@scotty.masternet.it> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Gianmarco Giovannelli wrote: > > The intention is to use "system" perl for everything. > > > > If a port breaks, then fix that port. :-) > > I think the situation of the FreeBSD ports now is critical... > > I have to do some work for University with PostgreSql and I found > that on my 3.0-current the following things don't work, even if they > are not make broken... Did you compile postgresql on 3.0 or is it a 2.2.* binary? If the latter, do you have the appropriate lib directory configured in ldconfig_paths_aout in /etc/rc.conf? I haven't had any problems with it compiled on 3.0. > p5-DBD-Pg (marked broken) The port depends on some broken modules that are not strictly required. Download the module, build and install by hand and it works okay. > p5-Pg (doesn't install) Again, I installed by hand and it works fine. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 06:39:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA16495 for freebsd-current-outgoing; Mon, 16 Nov 1998 06:39:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spa.kuis.kyoto-u.ac.jp (lab4imgw.kuis.kyoto-u.ac.jp [130.54.23.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA16483 for ; Mon, 16 Nov 1998 06:39:49 -0800 (PST) (envelope-from shige@kuis.kyoto-u.ac.jp) Received: from localhost (sirahama.kuis.kyoto-u.ac.jp [130.54.22.177]) by spa.kuis.kyoto-u.ac.jp (8.8.8/3.6Wspa) with ESMTP id XAA10276; Mon, 16 Nov 1998 23:37:24 +0900 (JST) To: freebsd-current@FreeBSD.ORG Cc: shige@kuis.kyoto-u.ac.jp Subject: mount root problem? on elf kernel X-Mailer: Mew version 1.93 on Emacs 20.3 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-Prom-Mew: Prom-Mew 1.93 (procmail reader for Mew) X-URL: http://www.yuasa.kuis.kyoto-u.ac.jp/~shige/ X-fingerprint: C8 BD 6A A7 CF FF 74 88 A4 B2 CC 5F C7 61 5C 9A X-Pgp-Public-Key-URL: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x56B99BF9 X-Face-Version: X-Face utility v1.3.2 - "The Fool On The Hill" X-Face: 34/1@t8]M!wP}sAw$~XQMzl5'O=lCIM]8=_8CE,|S)Vs4Wy@tU~A'wRi\lgWh-o&'|:zg>Gc?0?{^jo8(|5'Tg`yBH81.:!N9tSq*Sp6>C0q@{|&+FaM;R;KkoW1jA?QIWQ3:gNq {O%`:ww Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981116233923X.shige@kuis.kyoto-u.ac.jp> Date: Mon, 16 Nov 1998 23:39:23 +0900 (JST) From: Shigeyuki FUKUSHIMA X-Dispatcher: imput version 980905(IM100) Lines: 66 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I have an error in booting ELF kernel and mounting root device. I am using 3.0-current(Nov 15, 1998) and ELF kernel on that system. I have the following disks on my pc: wd0, da0. Wd0 only includes DOS slices, and da0 only includes FreeBSD slices. System BIOS probes IDE -> SCSI. Hence, wd0 is drive C, da0 is drive D. BTX loader says: Disk 0 Drive A Disk 1 Drive C Disk 2 Drive D In my configurations: * da0s1a:/boot.config /boot/loader * da0s1a:/boot/boot.conf set rootdev=disk0s1a: * da0s1a:/etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/da0s1a / ufs rw 1 1 (...snip...) The BOOTBIAS problem(?) is solved on the above configurations. # It is enable to change root device (da1s1a -> da0s1a). But, I have an error as follows: (...snip... device probing, changing root device, fsck report) mount: /dev/da0s1a on /: specified device does not match mounted device Filesystem mount failed, startup aborted Enter full pathname of shell or RETURN for /bin/sh: And, I modified da0s1a:/etc/fstab as follows: # Device Mountpoint FStype Options Dump Pass# /dev/da0a / ufs rw 1 1 (...snip...) And reboot again. Then, I have a properly system boot without mounting errors. I should use da0a in /etc/fstab instead of da0s1a, right? Or I have a some mistake in my configulations? Thank you. --- shige Shigeyuki FUKUSHIMA Dept. of Information Science, Kyoto Univ., JAPAN PGP Public Key: http://pgp5.ai.mit.edu:11371/pks/lookup?op=get&search=0x56B99BF9 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 06:51:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17319 for freebsd-current-outgoing; Mon, 16 Nov 1998 06:51:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA17314 for ; Mon, 16 Nov 1998 06:51:14 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id JAA16159; Mon, 16 Nov 1998 09:50:48 -0500 (EST) (envelope-from luoqi) Date: Mon, 16 Nov 1998 09:50:48 -0500 (EST) From: Luoqi Chen Message-Id: <199811161450.JAA16159@lor.watermarkgroup.com> To: FreeBSD-current@FreeBSD.ORG, grog@lemis.com, luoqi@watermarkgroup.com Subject: Re: Today's -CURRENT dies with "ffs_blkfree: bad size" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sunday, 15 November 1998 at 11:11:37 -0500, Luoqi Chen wrote: > >> I've just upgraded my kernel to a sup of about 9 hours ago, and have > >> had a number of panics. The first ones happened in X, but I finally > >> got a dump. Here's a trace: > >> > >> #0 boot (howto=262400) at ../../kern/kern_shutdown.c:285 > >> 285 dumppcb.pcb_cr3 = rcr3(); > >> (kgdb) bt > >> #0 boot (howto=262400) at ../../kern/kern_shutdown.c:285 > >> #1 0xf013e1e5 in panic (fmt=0xf01cc3e1 "ffs_blkfree: bad size") > >> at ../../kern/kern_shutdown.c:453 > >> #2 0xf01cc53e in ffs_blkfree (ip=0xf1283400, bno=4, size=8192) > > ^^^^^ > > It could be caused by our delayed bmap binding. Check to see if > > bp->b_blkno == bp->b_lblkno for this block. > > bp isn't initialized at this point. It gets initialized by a call to > bread() later in the function. > I meant buffers in the list buflist->bs_children[] in ffs_reallocblks(). They were setup earlier in cluster_collectbufs() by bread(). On FreeBSD, bread() does not call VOP_BMAP() to translate logical block number into physical one if the data is in vm cache. -lq > Kirk's currently looking at this, so I'll leave him to report. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 07:21:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21221 for freebsd-current-outgoing; Mon, 16 Nov 1998 07:21:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skraldespand.demos.su (skraldespand.demos.su [194.87.5.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21211 for ; Mon, 16 Nov 1998 07:21:18 -0800 (PST) (envelope-from mishania@skraldespand.demos.su) Received: by skraldespand.demos.su id SAA04026; (8.8.8/D) Mon, 16 Nov 1998 18:19:33 +0300 (MSK) Message-ID: <19981116181933.04674@demos.su> Date: Mon, 16 Nov 1998 18:19:33 +0300 From: "Mikhail A. Sokolov" To: dg@root.com Cc: michael_class@gmx.net, current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: SMP-System panics after recent ffs_alloc changes References: <199811141432.GAA13419@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <199811141432.GAA13419@root.com>; from David Greenman on Sat, Nov 14, 1998 at 06:32:26AM -0800 Organization: Demos Company, Ltd., Moscow, Russian Federation. X-Point-of-View: Gravity is myth, - the earth sucks. X-Useless-Header: Look ma! It's a # sign! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 14, 1998 at 06:32:26AM -0800, David Greenman wrote: # >the recent changes in vfs_cluster.c, buf.h and ffs_alloc.c cause a # >panic on my SMP-System. # ... # >Backing out these changes solves the problem. # > # >The panic is"ffs_blkfree: bad size" I just had this panic on a machine, SMP on, which is from 30 of October, and it doesn't have mentioned sysctl (which is probably ok, i'll have to look to commit logs, but that doesn't matter now, see below why), neither does the one from 13th of November have it, which is odd. Please comment? 1) FreeBSD s.demos.su 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Fri Oct 30 18:23:53 MSK 1998 mishania@s.demos.su:/usr/src/sys/compile/S i386 2) FreeBSD p.demos.net 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Fri Nov 13 15:43:05 MSK 1998 mishania@p.demos.net:/usr/src/sys/compile/P i386 # # No need to back out the changes - there is a sysctl knob to shut off the # code called "vfs.ffs.doreallocblks"...just set it to 0. # Is there anything unusual about your filesystems? Are you using the # standard 8K/1K block/fragment size? in the first case, fs's are unusual. it's 4K/1K. # -DG # # David Greenman # Co-founder/Principal Architect, The FreeBSD Project # # To Unsubscribe: send mail to majordomo@FreeBSD.org # with "unsubscribe freebsd-current" in the body of the message # -- -mishania To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 07:27:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA21962 for freebsd-current-outgoing; Mon, 16 Nov 1998 07:27:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sawmill.grauel.com (sawmill.grauel.com [199.233.104.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA21957 for ; Mon, 16 Nov 1998 07:27:40 -0800 (PST) (envelope-from rjk@sawmill.grauel.com) Received: (from rjk@localhost) by sawmill.grauel.com (8.8.8/8.8.7) id KAA29770; Mon, 16 Nov 1998 10:27:12 -0500 (EST) From: "Richard J. Kuhns" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13904.17488.316938.639031@sawmill.grauel.com> Date: Mon, 16 Nov 1998 10:27:12 -0500 (EST) To: freebsd-current@FreeBSD.ORG Subject: Strangeness with pcm driver... X-Mailer: VM 6.56 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running a recent -current (within the past 4 days), and decided to switch to the new sound code. rplay still apparently works just fine, but games that produce sounds (xboing and xkoules) suffer a 5 to 10 second delay. To be more precise, when I start a game of xkoules, there's no sound for 5 to 10 seconds. Then the sound starts, but it's the sound that should have been at the beginning of the game. As near as I can tell, there's never any loss; it's just 5 seconds out of synch. And yes, the sounds continue for a little while after I terminate the game. Suggestions? Here's the dmesg output for both the old (which works fine) and new: Old: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #15: Sun Nov 15 20:42:27 EST 1998 rjk@moran.grauel.com:/usr/src/sys/compile/MORAN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199432917 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff ... ... sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 6 on isa snd0: sbmidi0 at 0x300 on isa snd0: New: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #14: Thu Nov 12 16:18:11 EST 1998 toor@moran.grauel.com:/usr/src/sys/compile/MORAN Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199433106 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff ... ... pcm0 at 0x220 irq 5 drq 1 flags 0x15 on isa -- Richard Kuhns rjk@grauel.com PO Box 6249 Tel: (765)477-6000 \ 100 Sawmill Road x319 Lafayette, IN 47903 (800)489-4891 / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:02:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25115 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:02:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25109 for ; Mon, 16 Nov 1998 08:02:21 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id IAA20105; Mon, 16 Nov 1998 08:02:42 -0800 (PST) Message-Id: <199811161602.IAA20105@root.com> To: des@ping.uio.no cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 panic In-reply-to: Your message of "Mon, 16 Nov 1998 15:07:00 +0100." <199811161407.PAA01919@flood.ping.uio.no> From: David Greenman Reply-To: dg@root.com Date: Mon, 16 Nov 1998 08:02:41 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >#8 0xf019eef8 in trap_pfault () >#9 0xf019eb13 in trap () >#10 0xf19f4714 in ?? () >#11 0xf015143e in rename () >#12 0xf019f42b in syscall () This seems to be indicating that the rename was occuring on an LKM filesystem. Perhaps the module was stale? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27140 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:21:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27126; Mon, 16 Nov 1998 08:21:29 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id RAA01290; Mon, 16 Nov 1998 17:21:04 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id RAA09460; Mon, 16 Nov 1998 17:21:03 +0100 (MET) Message-ID: <19981116172101.37257@follo.net> Date: Mon, 16 Nov 1998 17:21:01 +0100 From: Eivind Eklund To: Mark Murray Cc: Satoshi Asami , current@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? References: <199811160606.IAA04093@greenpeace.grondar.za> <199811160618.WAA00540@silvia.hip.berkeley.edu> <19981116083046.A4393@klemm.gtn.com> <199811161151.NAA00668@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <199811161151.NAA00668@greenpeace.grondar.za>; from Mark Murray on Mon, Nov 16, 1998 at 01:51:12PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 16, 1998 at 01:51:12PM +0200, Mark Murray wrote: > Andreas Klemm wrote: > > So, if perl5 from the base system is definitively needed, > > then I'd vote to remove the misleading options from /etc/make.conf > > > > #NOPERL= true > > #NOSUIDPERL= true > > > > and in the Makefiles where they would take effect. > > The second one can stay, but I cannot think of a use for the first; > you make world; you have no perl; you need to build a kernel - oops! I think the first one also is nice to have. Some of us want to update perl and the rest of the system independently of each other (e.g, due to local hacks to the perl code, for people doing development of Perl itself). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:34:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25781 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:08:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25776 for ; Mon, 16 Nov 1998 08:08:41 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id IAA20187; Mon, 16 Nov 1998 08:08:57 -0800 (PST) Message-Id: <199811161608.IAA20187@root.com> To: "Mikhail A. Sokolov" cc: dg@root.com, michael_class@gmx.net, current@FreeBSD.ORG, mckusick@mckusick.com Subject: Re: SMP-System panics after recent ffs_alloc changes In-reply-to: Your message of "Mon, 16 Nov 1998 18:19:33 +0300." <19981116181933.04674@demos.su> From: David Greenman Reply-To: dg@root.com Date: Mon, 16 Nov 1998 08:08:56 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sat, Nov 14, 1998 at 06:32:26AM -0800, David Greenman wrote: ># >the recent changes in vfs_cluster.c, buf.h and ffs_alloc.c cause a ># >panic on my SMP-System. ># ... ># >Backing out these changes solves the problem. ># > ># >The panic is"ffs_blkfree: bad size" > >I just had this panic on a machine, SMP on, which is from 30 of October, >and it doesn't have mentioned sysctl (which is probably ok, i'll have to look >to commit logs, but that doesn't matter now, see below why), neither does the >one from 13th of November have it, which is odd. Please comment? That panic is unrelated to the recent ffs_alloc changes, which weren't committed until the 13th. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:37:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28795 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:37:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA28782 for ; Mon, 16 Nov 1998 08:37:52 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id JAA22267; Mon, 16 Nov 1998 09:45:39 -0700 (MST) Message-Id: <199811161645.JAA22267@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: Ollivier Robert cc: current@FreeBSD.ORG Subject: Re: newer gcc? In-reply-to: Your message of "Mon, 16 Nov 1998 07:06:33 +0100." <19981116070633.A13428@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Nov 1998 09:45:38 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > According to Terry Lambert: > > unless you compile it with threading enabled (unlike g++ 2.8.1, you > > must choose threading or no threading for resulting binaries at the > > time you compile the compiler, not at the time you compile the > > program). > > Last time I looked at a generic gcc 2.8.1, it also required you to specify > --enable-threads for configure. Are you really sure about this big > difference between egcs & gcc ? A quick scan of the 2.8.1 source leads me to believe that this is only for objective-c thread support. We are successfully using gcc 2.8.1 with threads in a fairly complex project, didn't need to use 'enable-threads'. However we did need to patch both gcc and libc_r source to handle exceptions (see the archives for my patches). -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:38:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29054 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:38:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29047 for ; Mon, 16 Nov 1998 08:38:43 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id RAA24546; Mon, 16 Nov 1998 17:38:00 +0100 (CET) (envelope-from des) Message-ID: <19981116173759.A24499@ping.uio.no> Date: Mon, 16 Nov 1998 17:37:59 +0100 From: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= To: dg@root.com Cc: current@FreeBSD.ORG Subject: Re: 3.0 panic References: <199811161407.PAA01919@flood.ping.uio.no> <199811161602.IAA20105@root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <199811161602.IAA20105@root.com>; from David Greenman on Mon, Nov 16, 1998 at 08:02:41AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 16, 1998 at 08:02:41AM -0800, David Greenman wrote: > >#8 0xf019eef8 in trap_pfault () > >#9 0xf019eb13 in trap () > >#10 0xf19f4714 in ?? () > >#11 0xf015143e in rename () > >#12 0xf019f42b in syscall () > This seems to be indicating that the rename was occuring on an LKM > filesystem. Perhaps the module was stale? No, the kernel and userland are in sync. DES -- Dag-Erling Smørgrav - des@ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:40:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29332 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:40:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xor.com (xor.com [192.225.33.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29323 for ; Mon, 16 Nov 1998 08:40:56 -0800 (PST) (envelope-from elijah@xor.com) Received: from localhost (elijah@localhost) by xor.com (8.8.5/8.8.5) with ESMTP id JAA04104 for ; Mon, 16 Nov 1998 09:40:23 -0700 (MST) Date: Mon, 16 Nov 1998 09:40:23 -0700 (MST) From: Eli Klein To: current@FreeBSD.ORG Subject: strage happenings with kern.flp/mfsroot.gz Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jordan had committed some things for me to enable me to install onto a 486sx25 laptop, but instead, this is what i got: Please insert MFS root floppy and press enter: - int=0000000d err=003394d0 efl=00010286 eip=001e4017 eax=001e4000 ebx=001c3b8b ecx=00000004 edx=0002784c esi=001ce47e edi=0002767d ebp=00095964 esp=0009e928 cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 cs:eip=cf fe 08 2a b0 b7 6f 74-f8 6b dd 6e ea e2 d8 61 ss:esp=c3 2a fa 9a d2 94 00 00-00 00 00 80 02 00 50 a0 System halted I don't know if the assembler output will help at all, but I thought I'd send it anyways.. again, i have a toshiba T3400C, a 486sx25. Let me know if you have any suggestions.. Thanks a lot for your help.. -Eli elijah@xor.com p.s. the reason for needing the changes is because the straight boot.flp would just hang (not freeze, just sit there) when it was probing hardware (ie. no fpu).. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:45:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29697 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:45:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA29686; Mon, 16 Nov 1998 08:45:00 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? References: <26948.911111774@zippy.cdrom.com> From: "Robert V. Baron" Date: 16 Nov 1998 11:43:48 -0500 In-Reply-To: "Jordan K. Hubbard"'s message of Sat, 14 Nov 1998 22:36:14 -0800 Message-ID: Lines: 15 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > A lot of folks dive in and change this first thing since it's annoying > to have a non-connected host bring up a ppp connection just to resolve > your own hostname, and sysinstall is careful about putting entries > into /etc/hosts for this. Any objection to changing the default? For Actually, I guess this is why life on disconnected laptops is so unpleasant. So definitely do it. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:49:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00200 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:49:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00195 for ; Mon, 16 Nov 1998 08:49:02 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id IAA09980; Mon, 16 Nov 1998 08:48:21 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 08:48:21 -0800 (PST) From: Doug White To: Jeroen Ruigrok van der Werven cc: current@FreeBSD.ORG Subject: Re: Ick, Help! Booting problem? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Nov 1998, Jeroen Ruigrok van der Werven wrote: > when I woke up this morning I wanted to dial in to my ISP to get my > mail. So I had ppp running in one window and just did a dial ISP. > Nothing happened. I looked at all the connectors, nothing weird. So I > 'quit'ted ppp and then started it again. Curiously enough I mentioned > that not enough inodes were available. > > This has never happened before, so I thought (Windows 95 thinking, I > admit), well let's reboot the sucker then. OK, it all detected the > devices and other things again, but at the point where it was supposed > to come up with the login: prompt, I got /stand/sysinstall. The system will fault over to sysinstall if init is corrupted or missing. It sounds like your disk crashed. > OK, I thought, could be a glitch in CURRENT, so I tried rebooting with > -s and that got me the same /stand/sysinstall! Also when I tried to > 'Exit Install' I never got to rebooting, it just caught a lot of SIG > 11's. .. or one of your SIMMs fried. > Could I use a bootdisk to get to my partitions? But even if I do, I > have no idea where the problem might lie... You'll have to reinstall to get init back. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00373 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:50:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megadeth.rtci.com (megadeth.noc.rtci.com [216.27.37.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00330 for ; Mon, 16 Nov 1998 08:50:01 -0800 (PST) (envelope-from dhopkins@rtci.com) Received: from rtci.com (oxygen.schizo.com [216.27.37.251]) by megadeth.rtci.com (8.8.8/8.8.8) with ESMTP id LAA05045; Mon, 16 Nov 1998 11:53:51 -0500 (EST) (envelope-from dhopkins@rtci.com) Message-ID: <36505A1E.8876B72@rtci.com> Date: Mon, 16 Nov 1998 12:00:14 -0500 From: Damon Hopkins Organization: Research Triangle Consultants, Inc. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Curret Mailing list Subject: Random rebooting Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov. 14 at apparently 11:32 pm my box rebooted. this was a saturday and I hadn't touched my box since friday an clues? Last log: reboot ~ Sat Nov. 14 23:32 no messages in /var/log/messages I cvsup'd, did a make world, and remade the kernel all on the 9th Here's my kernel stuff: FreeBSD totally.schizo.com 3.0-CURRENT FreeBSD 3.0-CURRENT #4: Mon Nov 9 14:51:26 EST 1998 oxygen@totally.schizo.com:/usr2/src/sys/compile/TOTALLY i386 And /var/log/messages: Nov 14 23:32:03 totally /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Nov 14 23:32:03 totally /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Nov 14 23:32:03 totally /kernel: The Regents of the University of California. All rights reserved. Nov 14 23:32:03 totally /kernel: FreeBSD 3.0-CURRENT #4: Mon Nov 9 14:51:26 EST 1998 Nov 14 23:32:03 totally /kernel: oxygen@totally.schizo.com:/usr2/src/sys/compile/TOTALLY Nov 14 23:32:03 totally /kernel: Timecounter "i8254" frequency 1193182 Hz Nov 14 23:32:03 totally /kernel: CPU: AMD Am5x86 Write-Back (486-class CPU) Nov 14 23:32:03 totally /kernel: Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Nov 14 23:32:03 totally /kernel: Features=0x1 Nov 14 23:32:03 totally /kernel: real memory = 25165824 (24576K bytes) Nov 14 23:32:03 totally /kernel: config> quit Nov 14 23:32:03 totally /kernel: avail memory = 22159360 (21640K bytes) Nov 14 23:32:03 totally /kernel: Probing for devices on PCI bus 0: Nov 14 23:32:03 totally /kernel: xl0: <3Com 3c900 Etherlink XL 10BaseT Combo> rev 0x00 int a irq 12 on pci0.13.0 Nov 14 23:32:04 totally /kernel: xl0: Ethernet address: 00:60:97:2d:dc:f3 Nov 14 23:32:04 totally /kernel: xl0: selecting 10baseT transceiver, half duplex Nov 14 23:32:04 totally /kernel: vga0: rev 0x06 int a irq 11 on pci0.14.0 Nov 14 23:32:04 totally /kernel: chip0: rev 0x04 on pci0.16.0 Nov 14 23:32:04 totally /kernel: chip1: rev 0x0e on pci0.18.0 Nov 14 23:32:04 totally /kernel: ide_pci0: rev 0x10 on pci0.18.1 Nov 14 23:32:04 totally /kernel: ide_pci: controll Nov 14 23:32:04 totally /kernel: er is simplex, no DMA on secondary channel Nov 14 23:32:04 totally /kernel: Probing for devices on the ISA bus: Nov 14 23:32:04 totally /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Nov 14 23:32:04 totally /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Nov 14 23:32:04 totally /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa Nov 14 23:32:04 totally /kernel: sio0: type 16550A Nov 14 23:32:04 totally /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Nov 14 23:32:04 totally /kernel: sio1 not found at 0x2f8 Nov 14 23:32:04 totally /kernel: lpt0 at 0x378-0x37f irq 7 on isa Nov 14 23:32:04 totally /kernel: lpt0: Interrupt-driven port Nov 14 23:32:04 totally /kernel: lp0: TCP/IP capable interface Nov 14 23:32:04 totally /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Nov 14 23:32:04 totally /kernel: fd0: 1.44MB 3.5in Nov 14 23:32:04 totally /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Nov 14 23:32:04 totally /kernel: wdc0: unit 0 (wd0): Nov 14 23:32:04 totally /kernel: wd0: 1219MB (2496816 sectors), 2477 cyls, 16 heads, 63 S/T, 512 B/S Nov 14 23:32:04 totally /kernel: wdc0: unit 1 (wd1): Nov 14 23:32:04 totally /kernel: wd1: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S Nov 14 23:32:04 totally /kernel: wdc1 not found at 0x170 Nov 14 23:32:04 totally /kernel: npx0 on motherboard Nov 14 23:32:04 totally /kernel: npx0: INT 16 interface Nov 14 23:32:04 totally /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry Nov 14 23:32:04 totally /kernel: IP Filter: initialized. Default = pass all, Logging = enabled Nov 14 23:32:05 totally /kernel: changing root device to wd0s1a Nov 14 23:32:05 totally /kernel: WARNING: Nov 14 23:32:05 totally /kernel: / was not properly dismounted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00897 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:54:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00892 for ; Mon, 16 Nov 1998 08:54:31 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id IAA11251; Mon, 16 Nov 1998 08:54:02 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 08:54:01 -0800 (PST) From: Doug White To: "Steven P. Donegan" cc: Open Systems Networking , current@FreeBSD.ORG Subject: Re: top/w/vmstat weirdness :-) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 14 Nov 1998, Steven P. Donegan wrote: > The question is - why did a make world NOT do these things. I do a make > world on this development box just about daily, and for some reason that > does not seem to really make the world. 'make world' doesn't build kernels. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 08:54:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00945 for freebsd-current-outgoing; Mon, 16 Nov 1998 08:54:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00934 for ; Mon, 16 Nov 1998 08:54:40 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id IAA23372 for current@FreeBSD.ORG; Mon, 16 Nov 1998 08:52:00 -0800 (PST) (envelope-from dhw) Date: Mon, 16 Nov 1998 08:52:00 -0800 (PST) From: David Wolfskill Message-Id: <199811161652.IAA23372@pau-amma.whistle.com> To: current@FreeBSD.ORG Subject: Re: hosts before bind in /etc/host.conf? In-Reply-To: <26948.911111774@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sat, 14 Nov 1998 22:36:14 -0800 >From: "Jordan K. Hubbard" >A lot of folks dive in and change this first thing since it's annoying >to have a non-connected host bring up a ppp connection just to resolve >your own hostname, and sysinstall is careful about putting entries >into /etc/hosts for this. Any objection to changing the default?... >Comments? In looking over responses to the above, I confess that I am surprised. It never occurred to me that the point brought up would be much of an issue, since I tend to run local nameservers. (At home I run a pair of 'em, as a split-horizon nameserver pair. And I only have 2 machines running presently.) But as long as it doesn't break anything for those of us who prefer to ignore /etc/hosts, I have no problem with it. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:00:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01595 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:00:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01590 for ; Mon, 16 Nov 1998 09:00:20 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id IAA12573; Mon, 16 Nov 1998 08:59:51 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 08:59:50 -0800 (PST) From: Doug White To: George Michaelson cc: current@FreeBSD.ORG Subject: Re: once elf transited, does /usr/src/obj/{aout,elf} need to exist? In-Reply-To: <199811150117.LAA01412@azure.dstc.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Nov 1998, George Michaelson wrote: > > I've completed the elf transition. If I blow away obj/{aout,elf,usr} > will I get them back? If you 'make world' without NOAOUT, you will. (obj/usr is deprecated and can disappear anyway.) > I assume the aout build is a once-only, and there won't be a need to keep > re-making the compat state? Unless you want to keep building the aout libs for compatibility reasons, you don't need them anymore. > Hang on. if somebody tweaks something that requires a new libc in elfland > to work, then non-upgraded aout binaries would need to see the change too > wouldn't they? > > Bummer. that 150+mb isn't headroom after all... Depends on how much of your system is aout. The only aout stuff I have left is leftover ports. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:16:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03077 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:16:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03071 for ; Mon, 16 Nov 1998 09:16:19 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA16489; Mon, 16 Nov 1998 09:15:53 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 09:15:52 -0800 (PST) From: Doug White To: "Eugene M. Kim" cc: FreeBSD-current Mailing List Subject: Re: NFS memory leak In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Nov 1998, Eugene M. Kim wrote: > I was trying to installworld yesterday when the bug popped out. > > First, suddenly the NFS server stopped to respond, but didn't panic. > After some work I found that the server could not send any IP packets; > sendto() (which ping uses) returned an error with ENOBUF. Then I > rebooted the server, and ran ``systat -vm 1'' and ``ping CLIENT''. The > ``free'' (between ``cache'' and ``daefr'') remained stable for a while, > but as soon as I started to installworld on the client, the figure > suddenly began to erode, and when it finally almost hit zero (I think it > was 40 or something) -- ping stopped working. > > Is this a known bug? I don't remember this reported/discussed on > -current. Throw me a stone if it's been. :-) ENOBUF implies a couple of things: 1) bad route to the client so that packets are getting backed up waiting for somewhere to go. 2) Incorrect interrupt configuration on your network card. NFS has problems, but my gut feeling is that it's not the sole culprit here. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:17:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03143 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:17:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03136 for ; Mon, 16 Nov 1998 09:17:46 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id MAA00288 for ; Mon, 16 Nov 1998 12:17:22 -0500 (EST) Message-Id: <4.1.19981116111511.00b92100@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 16 Nov 1998 11:18:27 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Nasty rebooting in 3.0 current Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As of this weekend's CVS update (current to the timestamp of this message) there appears to be a problem with rebooting on FreeBSD-3.0-CURRENT. I first noticed something awry last night. Essentially, during any significant network traffic (like CVSup) the system will suddenly hang... and then reboot. There don't appear to be any revealing messages in the logs, either. The system is running ipfw also, and I noted that this and some of the tcp_* files had been updated this weekend. Anyone else having this problem? Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:22:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03634 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:22:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA03625 for ; Mon, 16 Nov 1998 09:22:51 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id LAA00972; Mon, 16 Nov 1998 11:22:15 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma000954; Mon, 16 Nov 98 11:22:06 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id LAA03389; Mon, 16 Nov 1998 11:22:04 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Mon, 16 Nov 1998 11:22:03 -0600 (CST) From: Kyle Mestery To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: <4.1.19981116111511.00b92100@206.25.93.69> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As of this weekend's CVS update (current to the timestamp of this message) > there appears to be a problem with rebooting on FreeBSD-3.0-CURRENT. > I noticed this over the weekend also. I am running a current kernel from Saturday night around 5PM CST, on a dual PPro machine. On both Sunday morning and this morning I awoke to find the machine in a hung state, no video output, nohting. Required a hard reset. I havent had time to investivate, but will tonite. Very strange. Mine appears to be caused by a lot of network traffic also, asa CVSup this morning caused the same thing to happen. -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:26:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04046 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:26:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04041 for ; Mon, 16 Nov 1998 09:26:24 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA17887; Mon, 16 Nov 1998 09:24:23 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 09:24:22 -0800 (PST) From: Doug White To: "Roman V. Palagin" cc: current@FreeBSD.ORG Subject: Re: IPv6 and -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Roman V. Palagin wrote: > Hello! > > Is there are any implementation of IPv6 for FreeBSD-current? There's a couple at least, see http://www.freebsd.org/projects. AFAIK both projects are against -STABLE code. > I remember about Pierre Beyssac's INRIA-based distribution > (ftp://frmug.org/pub/ipv6) , but the last patch was for 1998/05/27 > kernel :( Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:35:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05085 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:35:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net (oldnews.quick.net [207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05073 for ; Mon, 16 Nov 1998 09:35:34 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id JAA11143; Mon, 16 Nov 1998 09:34:58 -0800 (PST) Date: Mon, 16 Nov 1998 09:34:58 -0800 (PST) From: "Steven P. Donegan" To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: <4.1.19981116111511.00b92100@206.25.93.69> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Forrest Aldrich wrote: > > As of this weekend's CVS update (current to the timestamp of this message) > there appears to be a problem with rebooting on FreeBSD-3.0-CURRENT. > > I first noticed something awry last night. Essentially, during any > significant > network traffic (like CVSup) the system will suddenly hang... and then reboot. > There don't appear to be any revealing messages in the logs, either. > > The system is running ipfw also, and I noted that this and some of the tcp_* > files had been updated this weekend. > > Anyone else having this problem? > > I have noted hang's - no tombstone, panic's - ffs_blkfree: bad size, and other minor weirdness this weekend. No pointers towards any fixes yet, sorry. Steven P. Donegan email: donegan@quick.net Sr. Network Infrastructure Engineer ICBM: N 33' 47.538/W 117' 59.687 WANG Global (within 1 meter - 133 ASL) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:42:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05894 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:42:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05778 for ; Mon, 16 Nov 1998 09:42:13 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id MAA00377; Mon, 16 Nov 1998 12:41:42 -0500 (EST) Message-Id: <4.1.19981116114107.00b99350@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 16 Nov 1998 11:42:34 -0500 To: "Steven P. Donegan" From: Forrest Aldrich Subject: Re: Nasty rebooting in 3.0 current Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <4.1.19981116111511.00b92100@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One more detail with regards to this reboot. I discovered (overlooked) a comment from /var/log/messages that / was not unmounted cleanly. I brought the machine into single-user mode and found that the other filesystems had not been unmounted cleanly. I suppose this could have been the result of the panic reboot. Previously, though, the boot sequence would automatically perform the appropriate fsck. I did this manually in single-user mode and will keep an eye on it. Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:45:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA06270 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:45:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA06252 for ; Mon, 16 Nov 1998 09:45:34 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id JAA19119; Mon, 16 Nov 1998 09:29:20 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 09:29:19 -0800 (PST) From: Doug White To: Damon Hopkins cc: Curret Mailing list Subject: Re: Random rebooting In-Reply-To: <36505A1E.8876B72@rtci.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Damon Hopkins wrote: > On Nov. 14 at apparently 11:32 pm my box rebooted. this was a saturday > and I hadn't touched my box since friday an clues? > Here's my kernel stuff: > FreeBSD totally.schizo.com 3.0-CURRENT > FreeBSD 3.0-CURRENT #4: Mon Nov 9 14:51:26 EST 1998 My system was perfectly stable at that time; perhaps it was a power fluctuation? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 09:54:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08003 for freebsd-current-outgoing; Mon, 16 Nov 1998 09:54:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA07691; Mon, 16 Nov 1998 09:53:48 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:0KNn3hTUpQMmgvPosumm9lxEjJpccpo4@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id TAA12770; Mon, 16 Nov 1998 19:52:44 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:YQJtevRk5VXRhz1a71xAAW8ELLzkOaCf@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id TAA01647; Mon, 16 Nov 1998 19:52:39 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811161752.TAA01647@greenpeace.grondar.za> To: Eivind Eklund cc: Satoshi Asami , current@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? In-Reply-To: Your message of " Mon, 16 Nov 1998 17:21:01 +0100." <19981116172101.37257@follo.net> References: <199811160606.IAA04093@greenpeace.grondar.za> <199811160618.WAA00540@silvia.hip.berkeley.edu> <19981116083046.A4393@klemm.gtn.com> <199811161151.NAA00668@greenpeace.grondar.za> <19981116172101.37257@follo.net> Date: Mon, 16 Nov 1998 19:52:37 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund wrote: > I think the first one also is nice to have. Some of us want to update perl > and the rest of the system independently of each other (e.g, due to local > hacks to the perl code, for people doing development of Perl itself). OK - I'll buy that. I'd prefer it to be undocumented, so people won't find the switch, frob it, and get burnt. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 10:06:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09663 for freebsd-current-outgoing; Mon, 16 Nov 1998 10:06:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PaLaDiN7.ml.org (PaLaDiN7.ml.org [208.132.240.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09641 for ; Mon, 16 Nov 1998 10:06:30 -0800 (PST) (envelope-from pal@PaLaDiN7.ml.org) Received: from localhost (localhost [127.0.0.1]) by PaLaDiN7.ml.org (8.9.1/8.9.1) with ESMTP id NAA00368 for ; Mon, 16 Nov 1998 13:02:50 -0500 (EST) (envelope-from pal@PaLaDiN7.ml.org) Date: Mon, 16 Nov 1998 13:02:48 -0500 (EST) From: pal To: current@FreeBSD.ORG Subject: Re: Random rebooting In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG getting reboots too.. Just wanted to write that after recompiling kernel yesterday its seems to be ok - and got another one :)))))))))))))))) FreeBSD PaLaDiN7.ml.org 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Sun Nov 15 20:37:37 i did make world Saturday, Nov. 14... It's looks like it more stable now in compare to several reboots yesterday but... Regards, pal On Mon, 16 Nov 1998, Doug White wrote: > On Mon, 16 Nov 1998, Damon Hopkins wrote: > > > On Nov. 14 at apparently 11:32 pm my box rebooted. this was a saturday > > and I hadn't touched my box since friday an clues? > > > Here's my kernel stuff: > > FreeBSD totally.schizo.com 3.0-CURRENT > > FreeBSD 3.0-CURRENT #4: Mon Nov 9 14:51:26 EST 1998 > > My system was perfectly stable at that time; perhaps it was a power > fluctuation? > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 10:07:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09740 for freebsd-current-outgoing; Mon, 16 Nov 1998 10:07:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PaLaDiN7.ml.org (PaLaDiN7.ml.org [208.132.240.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA09735 for ; Mon, 16 Nov 1998 10:07:11 -0800 (PST) (envelope-from pal@PaLaDiN7.ml.org) Received: from localhost (localhost.my.domain [127.0.0.1]) by PaLaDiN7.ml.org (8.9.1/8.9.1) with ESMTP id MAA11655; Mon, 16 Nov 1998 12:33:25 -0500 (EST) (envelope-from pal@PaLaDiN7.ml.org) Date: Mon, 16 Nov 1998 12:33:23 -0500 (EST) From: pal To: Kyle Mestery cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Don't know about network traffic - but I was expiriencing several reboots too, however after cvsuping and recompiling kernel yesterday - its seems to be ok now On Mon, 16 Nov 1998, Kyle Mestery wrote: > > As of this weekend's CVS update (current to the timestamp of this message) > > there appears to be a problem with rebooting on FreeBSD-3.0-CURRENT. > > > I noticed this over the weekend also. I am running a current kernel from > Saturday night around 5PM CST, on a dual PPro machine. On both Sunday > morning and this morning I awoke to find the machine in a hung state, no > video output, nohting. Required a hard reset. I havent had time to > investivate, but will tonite. Very strange. Mine appears to be caused by > a lot of network traffic also, asa CVSup this morning caused the same thing to > happen. > > -- > Kyle Mestery > StorageTek's Storage Networking Group > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 10:20:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA10839 for freebsd-current-outgoing; Mon, 16 Nov 1998 10:20:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA10831 for ; Mon, 16 Nov 1998 10:20:30 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.9.1) with ESMTP id NAA01843; Mon, 16 Nov 1998 13:19:17 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Mon, 16 Nov 1998 13:19:17 -0500 (EST) From: "Alok K. Dhir" To: Kyle Mestery cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I saw the same problem. Setting the sysctl variable 'vfs.ffs.doreallocblks' to 0 seems to have solved it for me.... Al On Mon, 16 Nov 1998, Kyle Mestery wrote: > > As of this weekend's CVS update (current to the timestamp of this > message) > > there appears to be a problem with rebooting on FreeBSD-3.0-CURRENT. > > > I noticed this over the weekend also. I am running a current kernel from > Saturday night around 5PM CST, on a dual PPro machine. On both Sunday > morning and this morning I awoke to find the machine in a hung state, no > video output, nohting. Required a hard reset. I havent had time to > investivate, but will tonite. Very strange. Mine appears to be caused by > a lot of network traffic also, asa CVSup this morning caused the same thing > to > happen. > > -- > Kyle Mestery > StorageTek's Storage Networking Group > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 10:31:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11957 for freebsd-current-outgoing; Mon, 16 Nov 1998 10:31:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11949 for ; Mon, 16 Nov 1998 10:31:00 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id MAA16210 for current@freebsd.org; Mon, 16 Nov 1998 12:30:32 -0600 (CST) From: Kevin Day Message-Id: <199811161830.MAA16210@home.dragondata.com> Subject: MediaGX and calcru: negative time To: current@FreeBSD.ORG Date: Mon, 16 Nov 1998 12:30:32 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok... I'm using a Media GXm in an embedded product with FreeBSD... I'm getting the annoying 'calcru' messages, and processes dying. Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.7-RELEASE #0: Wed Oct 21 16:22:35 CDT 1998 devel@kevin1.touchmaster:/usr/src/sys/compile/DEVEL CPU: Cyrix GXm (0.00-MHz 586-class CPU) Origin = "CyrixInstead" Id = 0x540 DIR=0x3346 Stepping=3 Revision=3 real memory = 63963136 (62464K bytes) avail memory = 60252160 (58840K bytes) Probing for devices on PCI bus 0: chip0 rev 0 on pci0:0:0 de0 rev 34 int a irq 11 on pci0:7:0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:43:26:d8 chip1 rev 0 on pci0:18:0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm: keyboard controller failed. psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa wdc0 at 0x1f0-0x1f7 irq 14 flags 0xff00ff on isa wdc0: unit 0 (wd0): , multi-block-16 wd0: 3079MB (6306048 sectors), 6256 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, dma, iordis wcd0: 5512Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 flags 0x1 on motherboard npx0: INT 16 interface de0: enabling 10baseT port calcru: negative time: -6644 usec pid 8197 (dl), uid 0: exited on signal 11 (core dumped) calcru: negative time: -6644 usec pid 8211 (dl), uid 0: exited on signal 11 (core dumped) calcru: negative time: -6644 usec pid 8211 (dl), uid 0: exited on signal 11 (core dumped) calcru: negative time: -6644 usec pid 8211 (dl), uid 0: exited on signal 11 (core dumped) /kernel: file: table is full syslogd: /var/run/utmp: Too many open files in system syslogd: /var/run/utmp: Too many open files in system /kernel: file: table is full syslogd: /var/run/utmp: Too many open files in system last message repeated 3 times /kernel: file: table is full syslogd: /var/run/utmp: Too many open files in system last message repeated 3 times /kernel: file: table is full Now, since Cyrix is supporting us with this product, are there any questions I can ask them that may shed some light? It appears that the problem is brought out by lots of IDE access. The IDE interface is done internaly, in the CPU. Could timeouts/delays in the IDE side be slowing the clock somehow? Tell me what to ask, and I will. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 11:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22758 for freebsd-current-outgoing; Mon, 16 Nov 1998 11:17:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-26-dbn.dial-up.net [196.34.155.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22746 for ; Mon, 16 Nov 1998 11:17:51 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA03516; Mon, 16 Nov 1998 21:16:37 +0200 (SAT) From: Robert Nordier Message-Id: <199811161916.VAA03516@ceia.nordier.com> Subject: Re: strage happenings with kern.flp/mfsroot.gz In-Reply-To: from Eli Klein at "Nov 16, 98 09:40:23 am" To: elijah@xor.com (Eli Klein) Date: Mon, 16 Nov 1998 21:16:34 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eli Klein wrote: > jordan had committed some things for me to enable me to install onto a > 486sx25 laptop, but instead, this is what i got: > > Please insert MFS root floppy and press enter: > > - > int=0000000d err=003394d0 efl=00010286 eip=001e4017 > eax=001e4000 ebx=001c3b8b ecx=00000004 edx=0002784c > esi=001ce47e edi=0002767d ebp=00095964 esp=0009e928 > cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 > cs:eip=cf fe 08 2a b0 b7 6f 74-f8 6b dd 6e ea e2 d8 61 > ss:esp=c3 2a fa 9a d2 94 00 00-00 00 00 80 02 00 50 a0 > System halted > > I don't know if the assembler output will help at all, but I thought I'd > send it anyways.. again, i have a toshiba T3400C, a 486sx25. Although this is a BTX-generated register dump, the exception is actually happening a few bytes into the kernel startup code. Or what should be the kernel startup code: cs:eip isn't pointing at anything valid. BTX has been told to pass control to the kernel (the 0x94d2 on the stack is the return address of the BTX "exec" syscall) but I'd suspect the kernel just hasn't been loaded correctly. It looks as though the BTX client thinks the kernel entry point is 0x1e4000, but that's just a guess (eax may have been altered). Doubt that this helps much in itself, but that's what can be gotten from the register dump. Maybe Jordan, or someone else, has some ideas based on this. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 11:39:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27514 for freebsd-current-outgoing; Mon, 16 Nov 1998 11:39:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27496 for ; Mon, 16 Nov 1998 11:39:40 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id OAA22299; Mon, 16 Nov 1998 14:39:11 -0500 (EST) Message-Id: <4.1.19981116133745.00a63100@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 16 Nov 1998 13:38:42 -0500 To: pal , Kyle Mestery From: Forrest Aldrich Subject: Re: Nasty rebooting in 3.0 current Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm performing a make world now from this a.m.'s CVSUP, and will keep a close eye on it. Nothing has happened since I manually fsck'd the filesystem (recall my earlier posting about the filesystems not being properly unmounted), so perhaps there is a connection... as CVSup does traverse the /usr/src filesystem to compare timestamps, etc. etc. Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 11:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29927 for freebsd-current-outgoing; Mon, 16 Nov 1998 11:53:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megadeth.rtci.com (megadeth.noc.rtci.com [216.27.37.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29920 for ; Mon, 16 Nov 1998 11:53:03 -0800 (PST) (envelope-from dhopkins@rtci.com) Received: from rtci.com (oxygen.schizo.com [216.27.37.251]) by megadeth.rtci.com (8.8.8/8.8.8) with ESMTP id OAA06893; Mon, 16 Nov 1998 14:56:24 -0500 (EST) (envelope-from dhopkins@rtci.com) Message-ID: <365084E6.8AB61657@rtci.com> Date: Mon, 16 Nov 1998 15:02:46 -0500 From: Damon Hopkins Organization: Research Triangle Consultants, Inc. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Current Mailing list Subject: Re: Random rebooting References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think it was power as other machines in my office connected to the same outlets did not reboot. I'm going to cvsup today anyways and see what happens.. Damon Hopkins -- [-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=-] [ Damon Hopkins mailto: dhopkins@rtci.com ] [ Software Developer http://totally.schizo.com ] [ Research Triangle Consultants, Inc. http://www.rtci.com ] [ -- In search of the elusive 50 sided triangle. -- ] [-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=-] Doug White wrote: > > On Mon, 16 Nov 1998, Damon Hopkins wrote: > > > On Nov. 14 at apparently 11:32 pm my box rebooted. this was a saturday > > and I hadn't touched my box since friday an clues? > > > Here's my kernel stuff: > > FreeBSD totally.schizo.com 3.0-CURRENT > > FreeBSD 3.0-CURRENT #4: Mon Nov 9 14:51:26 EST 1998 > > My system was perfectly stable at that time; perhaps it was a power > fluctuation? > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 12:05:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01700 for freebsd-current-outgoing; Mon, 16 Nov 1998 12:05:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01621 for ; Mon, 16 Nov 1998 12:04:45 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.8]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1E1B; Mon, 16 Nov 1998 20:35:17 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 16 Nov 1998 20:39:42 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Doug White Subject: Re: Ick, Help! Booting problem? Cc: current@FreeBSD.ORG, Jeroen Ruigrok van der Werven Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Nov-98 Doug White wrote: > On Sat, 14 Nov 1998, Jeroen Ruigrok van der Werven wrote: >> This has never happened before, so I thought (Windows 95 thinking, I >> admit), well let's reboot the sucker then. OK, it all detected the >> devices and other things again, but at the point where it was supposed >> to come up with the login: prompt, I got /stand/sysinstall. > > The system will fault over to sysinstall if init is corrupted or missing. After using a disk/holographic shell I tried to ls /sbin/init and it gave me an error I cannot remember. > It sounds like your disk crashed. Yeah, wonder how/why though... I also verify media/low level format before using them, brand new disk too... >> OK, I thought, could be a glitch in CURRENT, so I tried rebooting with >> -s and that got me the same /stand/sysinstall! Also when I tried to >> 'Exit Install' I never got to rebooting, it just caught a lot of SIG >> 11's. > > .. or one of your SIMMs fried. Nah... I used to have SIMM problems until I got these new ones which are all tested... besides else I had to have them way sooner... >> Could I use a bootdisk to get to my partitions? But even if I do, I >> have no idea where the problem might lie... > > You'll have to reinstall to get init back. That's a conclusion I reached myself ;) Thanks anyway... Conclusion: reinstall minimal system, then make world from latest cvsup sources on one of my slices, plus made new kernel... All working again... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 12:13:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA03005 for freebsd-current-outgoing; Mon, 16 Nov 1998 12:13:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02984 for ; Mon, 16 Nov 1998 12:13:30 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id MAA22314; Mon, 16 Nov 1998 12:12:21 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 12:12:20 -0800 (PST) From: Doug White To: Jeroen Ruigrok/Asmodai cc: current@FreeBSD.ORG, Jeroen Ruigrok van der Werven Subject: Re: Ick, Help! Booting problem? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > On 16-Nov-98 Doug White wrote: > > On Sat, 14 Nov 1998, Jeroen Ruigrok van der Werven wrote: > >> This has never happened before, so I thought (Windows 95 thinking, I > >> admit), well let's reboot the sucker then. OK, it all detected the > >> devices and other things again, but at the point where it was supposed > >> to come up with the login: prompt, I got /stand/sysinstall. > > > > The system will fault over to sysinstall if init is corrupted or missing. > > After using a disk/holographic shell I tried to ls /sbin/init and it gave me an > error I cannot remember. > > > It sounds like your disk crashed. > > Yeah, wonder how/why though... I also verify media/low level format before > using them, brand new disk too... Sounds like an initial failure .. warranty replacement. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 12:56:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08798 for freebsd-current-outgoing; Mon, 16 Nov 1998 12:56:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08793 for ; Mon, 16 Nov 1998 12:56:33 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id NAA02909; Mon, 16 Nov 1998 13:55:32 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd002828; Mon Nov 16 13:55:24 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id NAA02699; Mon, 16 Nov 1998 13:54:54 -0700 (MST) From: Terry Lambert Message-Id: <199811162054.NAA02699@usr08.primenet.com> Subject: Re: Is it soup yet? :-) To: dfr@nlsystems.com (Doug Rabson) Date: Mon, 16 Nov 1998 20:54:53 +0000 (GMT) Cc: tlambert@primenet.com, jkh@zippy.cdrom.com, green@unixhelp.org, peter@netplex.com.au, julian@whistle.com, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: from "Doug Rabson" at Nov 16, 98 08:31:50 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > Call be crazy, but I think I'd almost like to move the "real" kernel to > > > > > /boot/kernel, providing the search paths were ok. > > > > > > > > You're absolutely nuts. > > > > > > Can we get postings in -current back on track? I'm seeing enough > > > Brian Feldman posts to justify a filter. > > > > The "mini FFS" used by the boot blocks doesn't know how to traverse > > subdirectories. > > Actually it does. Then someone added it more recently than the original version from CSRG. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 13:18:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12595 for freebsd-current-outgoing; Mon, 16 Nov 1998 13:18:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12590 for ; Mon, 16 Nov 1998 13:18:20 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA06493; Mon, 16 Nov 1998 13:08:50 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdUl6487; Mon Nov 16 21:08:40 1998 Message-ID: <36509430.2781E494@whistle.com> Date: Mon, 16 Nov 1998 13:08:00 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Terry Lambert CC: Doug Rabson , jkh@zippy.cdrom.com, green@unixhelp.org, peter@netplex.com.au, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Is it soup yet? :-) References: <199811162054.NAA02699@usr08.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > > > > > Call be crazy, but I think I'd almost like to move the "real" kernel to > > > > > > /boot/kernel, providing the search paths were ok. > > > > > > > > > > You're absolutely nuts. > > > > > > > > Can we get postings in -current back on track? I'm seeing enough > > > > Brian Feldman posts to justify a filter. > > > > > > The "mini FFS" used by the boot blocks doesn't know how to traverse > > > subdirectories. > > > > Actually it does. > > Then someone added it more recently than the original version > from CSRG. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. I think you're confusing two bits of code.. the miniFFS came via me, from the MACH bootblocks the stuff from CSRG (via Bill Jolitz) was junked in 92. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 13:34:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16287 for freebsd-current-outgoing; Mon, 16 Nov 1998 13:34:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hotrats.apl.washington.edu (hotrats.apl.washington.edu [128.95.76.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16269 for ; Mon, 16 Nov 1998 13:33:58 -0800 (PST) (envelope-from kargl@hotrats.apl.washington.edu) Received: (from kargl@localhost) by hotrats.apl.washington.edu (8.9.1/8.8.8) id NAA11987 for freebsd-current@freebsd.org; Mon, 16 Nov 1998 13:37:49 -0800 (PST) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <199811162137.NAA11987@hotrats.apl.washington.edu> Subject: kernel panics with SMP To: freebsd-current@FreeBSD.ORG Date: Mon, 16 Nov 1998 13:37:49 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD-current, cvsup'd on Saturday 14 Nov 98. SMP system, Micron Millenium Pro2 (dual Pentium Pro) with 256 MB memory, Adaptec 2940 controller, 1 $.3 GB seagate drive. DDB message: dev=0x20405, bno = 13, bsize = 8192, size = 8192, fs = /usr panic: ffs_blkfree: bad size mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 Debugger("panic") Stopped at _Debugger+0x35: movb $0, _in_Debugger.98 db> trace _Debugger(f0137c1e) at _Debugger+0x35 _panic(f01c52d1,f01c529b,20405,d,2000) at _panic+0x9f _ffs_blkfree(f09d4990,d,2000) at _ffs_blkfree+0xc2 _ffs_reallocblks(f85c2e24) at _ffs_reallocblks+0x420 _cluster_write(f5c87c98,38000,0) at _cluster_write+0x15f _ffs_write(f85c2efc,f84f57c0,41,f85c2f94,f012f448) at _ffs_write+0x56f _vn_write(f0da7a80,f85c2f40,f0d4fa80,f84f57c0,f0241dac) at _vn_write+0xef _write(f84f57c0,f85c2f94,805d100,41,805d100) at _write+0xba _syscall(27,27,805d100,41,efbfdc28) at _syscall+0x187 _Xint0x80_syscall() at _Xint0x80_syscall+0x4c /usr was mounted with async option. /usr is roughly a 3.5 GB partition. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 13:50:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19752 for freebsd-current-outgoing; Mon, 16 Nov 1998 13:50:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19738 for ; Mon, 16 Nov 1998 13:50:07 -0800 (PST) (envelope-from regnauld@EU.org) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id WAA26571; Mon, 16 Nov 1998 22:53:53 +0100 (CET) (envelope-from regnauld@EU.org) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id XAA26805; Mon, 16 Nov 1998 23:15:35 +0100 (CET) Received: (from uucp@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id WAA10358; Mon, 16 Nov 1998 22:49:14 +0100 (CET) Received: (from regnauld@localhost) by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id WAA00916; Mon, 16 Nov 1998 22:49:29 +0100 (CET) (envelope-from regnauld) Message-ID: <19981116224929.52241@stimpy.prosa.dk> Date: Mon, 16 Nov 1998 22:49:29 +0100 From: Phil Regnauld To: Doug White Cc: "Roman V. Palagin" , current@FreeBSD.ORG Subject: Re: IPv6 and -current References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Doug White on Mon, Nov 16, 1998 at 09:24:22AM -0800 X-Operating-System: FreeBSD 3.0-CURRENT i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White writes: > > There's a couple at least, see http://www.freebsd.org/projects. AFAIK > both projects are against -STABLE code. Actually the INRIA stuff (from Francis Dupont/INRIA in fact) was ported to -current twice by Pierre Beyssac. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 13:51:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19838 for freebsd-current-outgoing; Mon, 16 Nov 1998 13:51:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19829 for ; Mon, 16 Nov 1998 13:50:54 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA27457; Mon, 16 Nov 1998 14:50:29 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd027330; Mon Nov 16 14:50:18 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA04517; Mon, 16 Nov 1998 14:50:11 -0700 (MST) From: Terry Lambert Message-Id: <199811162150.OAA04517@usr08.primenet.com> Subject: Re: kernel compile problem To: rkw@nomad.dataplex.net (User RKW) Date: Mon, 16 Nov 1998 21:50:11 +0000 (GMT) Cc: jabley@clear.co.nz, freebsd-current@FreeBSD.ORG In-Reply-To: from "User RKW" at Nov 1, 98 07:02:10 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Terry (and I) would argue that the committer should not be allowed to > remove the lock himself. That privledge/duty would belong to the QA > dept whose daemon would make at least some rudimentary checks before > pulling the lock. No. I would allow the user to remove the lock; as in: cvs lock w cvs ci cvs unlock Where the cvs unlock forced you to comment on the content of your commit, as a group (I would subscribe to *only* the list of log messages from this, if it were available). The QA issue is one of forcing developers to test-build before doing commits, as in: cvs lock w cvs update make # modify code and repeat previous command, as necesssary cvs ci cvs unlock This is a developer thing. You could also do: cvs lock r cvs update cvs unlock ...a read lock; the lock does not force a comment. You could also do: cvs update ...with no read lock. Obviously, most developers would do this, while cvsup would mirror the latter. This has effectively been discussed to death before; most committers are unwilling to type the two additional CVS commands, and they fear that concurrent developement would be stymied (the lock should apply against the module, so this is a specious argument given the infrequency of concurrent commits). The purpose of the locks is *only* to ensure complete snapshots, so that buildability is a function of the contents of the tree not currently undergoing modification by a developer instead of a mater of chance. If you are going to talk about hacking up cvs and cvsup, the single most useful hack would be to allow the cvsup of the FreeBSD sources directly into a local vendor branch, such that you could make local modifications to the source tree without fear of getting stomped, and (unlike the "magic revision" hack for supporting local changes) you would have a simple method of "merge-to-head" to update your code to track FreeBSD's progress. Unfortunately, it's been years since I've done Modula II, and cvsup is in Modula III anyway... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 13:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20841 for freebsd-current-outgoing; Mon, 16 Nov 1998 13:56:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20826 for ; Mon, 16 Nov 1998 13:56:03 -0800 (PST) (envelope-from regnauld@EU.org) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id WAA26574; Mon, 16 Nov 1998 22:53:54 +0100 (CET) (envelope-from regnauld@EU.org) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id XAA26797; Mon, 16 Nov 1998 23:15:32 +0100 (CET) Received: (from uucp@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) with UUCP id WAA10356; Mon, 16 Nov 1998 22:49:11 +0100 (CET) Received: (from regnauld@localhost) by stimpy.prosa.dk (8.9.1/8.9.1/stimpy-1.0) id WAA00878; Mon, 16 Nov 1998 22:26:50 +0100 (CET) (envelope-from regnauld) Message-ID: <19981116222650.00624@stimpy.prosa.dk> Date: Mon, 16 Nov 1998 22:26:50 +0100 From: Phil Regnauld To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysctl -a oddity References: <19981115103207.31226@stimpy.prosa.dk> <15374.911131073@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <15374.911131073@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Nov 15, 1998 at 12:57:53PM +0100 X-Operating-System: FreeBSD 3.0-CURRENT i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp writes: > > recompile sysctl No go: kernel + sources + obj in sync: [root]# make [usr.sbin/sysctl] Warning: Object directory not changed from original /usr/src/usr.sbin/sysctl cc -O -pipe -c sysctl.c cc -O -pipe -static -o sysctl sysctl.o gzip -cn sysctl.8 > sysctl.8.gz [root]# make install [usr.sbin/sysctl] install -c -s -o root -g wheel -m 555 sysctl /sbin install -c -o root -g wheel -m 444 sysctl.8.gz /usr/share/man/man8 [root]# sysctl -a [usr.sbin/sysctl] kern.ostype: FreeBSD kern.osrelease: 3.0-CURRENT kern.osrevision: 199506 kern.version: FreeBSD 3.0-CURRENT #0: Sun Nov 15 12:51:45 CET 1998 regnauld@stimpy.prosa.dk:/usr/src/sys/compile/STIMPY.v4.pc kern.maxvnodes: 2186 kern.maxproc: 276 kern.maxfiles: 552 kern.argmax: 65536 kern.securelevel: -1 kern.hostname: stimpy.prosa.dk kern.hostid: 0 kern.clockrate: sysctl: S_clockinfo 20 != 16: Undefined error: 0 [root]# [usr.sbin/sysctl] Now, do you mean I should cvsup _then_ recompile sysctl ? This has been happening since 3.0-R. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 14:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29672 for freebsd-current-outgoing; Mon, 16 Nov 1998 14:55:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29659 for ; Mon, 16 Nov 1998 14:55:46 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA06254; Tue, 17 Nov 1998 09:24:55 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id JAA02488; Tue, 17 Nov 1998 09:24:46 +1030 (CST) Message-ID: <19981117092446.M717@freebie.lemis.com> Date: Tue, 17 Nov 1998 09:24:46 +1030 From: Greg Lehey To: Damon Hopkins , Current Mailing list Subject: Re: Random rebooting References: <36505A1E.8876B72@rtci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <36505A1E.8876B72@rtci.com>; from Damon Hopkins on Mon, Nov 16, 1998 at 12:00:14PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 16 November 1998 at 12:00:14 -0500, Damon Hopkins wrote: > On Nov. 14 at apparently 11:32 pm my box rebooted. this was a saturday > and I hadn't touched my box since friday an clues? Not really. Your machine probably rebooted because of something like a panic, but you don't mention that. If you're running -CURRENT, you should at least have dumps enabled, and preferably a debug kernel so you can do something with the dumps. The only thing I can see from the messages you added was that you didn't have dumps enabled. Also, you appear not to be following this list, or you would have seen a number of messages on panics in the last few days. We appear to have fixed one, but there's no way of knowing whether it had anything to do with your problem. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:00:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00969 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:00:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00818 for ; Mon, 16 Nov 1998 15:00:19 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA06276; Tue, 17 Nov 1998 09:29:42 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id JAA02513; Tue, 17 Nov 1998 09:29:42 +1030 (CST) Message-ID: <19981117092941.N717@freebie.lemis.com> Date: Tue, 17 Nov 1998 09:29:41 +1030 From: Greg Lehey To: "Steven G. Kargl" , freebsd-current@FreeBSD.ORG Subject: Re: kernel panics with SMP References: <199811162137.NAA11987@hotrats.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811162137.NAA11987@hotrats.apl.washington.edu>; from Steven G. Kargl on Mon, Nov 16, 1998 at 01:37:49PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 16 November 1998 at 13:37:49 -0800, Steven G. Kargl wrote: > FreeBSD-current, cvsup'd on Saturday 14 Nov 98. > > SMP system, Micron Millenium Pro2 (dual Pentium Pro) with > 256 MB memory, Adaptec 2940 controller, 1 $.3 GB seagate drive. > > DDB message: > > dev=0x20405, bno = 13, bsize = 8192, size = 8192, fs = /usr > panic: ffs_blkfree: bad size > mp_lock = 00000001; cpuid = 0; lapic.id = 01000000 > Debugger("panic") > Stopped at _Debugger+0x35: movb $0, _in_Debugger.98 > db> trace > _Debugger(f0137c1e) at _Debugger+0x35 > _panic(f01c52d1,f01c529b,20405,d,2000) at _panic+0x9f > _ffs_blkfree(f09d4990,d,2000) at _ffs_blkfree+0xc2 > _ffs_reallocblks(f85c2e24) at _ffs_reallocblks+0x420 > _cluster_write(f5c87c98,38000,0) at _cluster_write+0x15f > _ffs_write(f85c2efc,f84f57c0,41,f85c2f94,f012f448) at _ffs_write+0x56f > _vn_write(f0da7a80,f85c2f40,f0d4fa80,f84f57c0,f0241dac) at _vn_write+0xef > _write(f84f57c0,f85c2f94,805d100,41,805d100) at _write+0xba > _syscall(27,27,805d100,41,efbfdc28) at _syscall+0x187 > _Xint0x80_syscall() at _Xint0x80_syscall+0x4c It would be nice to see the panic string, but it's pretty sure to be "ffs_blkfree: bad size". It looks as if it's fixed; wait a day or so. In the meantime, you can work around it with # sysctl -w vfs.ffs.doreallocblks=0 Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:03:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01341 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:03:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [192.109.159.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01333 for ; Mon, 16 Nov 1998 15:03:26 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id AAA28410; Tue, 17 Nov 1998 00:00:09 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id UAA08978; Mon, 16 Nov 1998 20:03:12 +0100 (CET) (envelope-from andreas) Message-ID: <19981116200312.A8700@klemm.gtn.com> Date: Mon, 16 Nov 1998 20:03:12 +0100 From: Andreas Klemm To: Kyle Mestery , Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current References: <4.1.19981116111511.00b92100@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kyle Mestery on Mon, Nov 16, 1998 at 11:22:03AM -0600 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 16, 1998 at 11:22:03AM -0600, Kyle Mestery wrote: > > As of this weekend's CVS update (current to the timestamp of this message) > > there appears to be a problem with rebooting on FreeBSD-3.0-CURRENT. > > > I noticed this over the weekend also. I am running a current kernel from > Saturday night around 5PM CST, on a dual PPro machine. On both Sunday > morning and this morning I awoke to find the machine in a hung state, no > video output, nohting. Required a hard reset. I havent had time to > investivate, but will tonite. Very strange. Mine appears to be caused by > a lot of network traffic also, asa CVSup this morning caused the same thing to > happen. Same for me on make worlds and other occasion (happened 3-4 times). panic: ffs_blkfree: bad size, fs=/var -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:12:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02973 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:12:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02927 for ; Mon, 16 Nov 1998 15:12:18 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id RAA09337; Mon, 16 Nov 1998 17:11:54 -0600 (CST) From: Kevin Day Message-Id: <199811162311.RAA09337@home.dragondata.com> Subject: Re: MediaGX and calcru: negative time In-Reply-To: <199811161830.MAA16210@home.dragondata.com> from Kevin Day at "Nov 16, 98 12:30:32 pm" To: toasty@home.dragondata.com (Kevin Day) Date: Mon, 16 Nov 1998 17:11:54 -0600 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a possibly related note, after upgrading to -current: > FreeBSD 2.2.7-RELEASE #0: Wed Oct 21 16:22:35 CDT 1998 > devel@kevin1.touchmaster:/usr/src/sys/compile/DEVEL > CPU: Cyrix GXm (0.00-MHz 586-class CPU) > Origin = "CyrixInstead" Id = 0x540 DIR=0x3346 Stepping=3 Revision=3 > real memory = 63963136 (62464K bytes) > avail memory = 60252160 (58840K bytes) FreeBSD 3.0-RELEASE #0: Mon Nov 16 16:10:02 CST 1998 root@kevin1.touchmaster:/usr/src/sys/compile/DEVEL Timecounter "i8254" frequency 1193182 Hz cost 40336 ns Timecounter "TSC" frequency 20172892 Hz cost 180 ns CPU: Cyrix GXm (20.17-MHz 586-class CPU) Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 Features=0x808131 real memory = 63963136 (62464K bytes) avail memory = 60243968 (58832K bytes) The clock now runs super fast. su-2.02# vmstat -i interrupt total rate clk0 irq0 179183 8 rtc0 irq8 229312 11 pci irq11 13297 0 wdc0 irq14 341357 16 sc0 irq1 70 0 sio0 irq4 30 0 Total 763249 36 According to date, i'm running about 15-30x the speed I should be. Has anyone else reported this for a GXm? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:12:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03027 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:12:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from liquid.tpb.net (drum-n-bass.party-animals.com [194.134.94.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03014 for ; Mon, 16 Nov 1998 15:12:43 -0800 (PST) (envelope-from niels@bakker.net) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.1a/8.8.8/Debian/GNU) with SMTP id AAA01649 for ; Tue, 17 Nov 1998 00:12:14 +0100 Date: Tue, 17 Nov 1998 00:12:13 +0100 (CET) From: N To: current@FreeBSD.ORG Subject: Re: Random rebooting In-Reply-To: <19981117092446.M717@freebie.lemis.com> Message-ID: <981117000318.1544A-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Monday, 16 November 1998 at 12:00:14 -0500, Damon Hopkins wrote: >> On Nov. 14 at apparently 11:32 pm my box rebooted. this was a saturday >> and I hadn't touched my box since friday an clues? Quoth Greg Lehey: > Not really. Your machine probably rebooted because of something like > a panic, but you don't mention that. If you're running -CURRENT, you > should at least have dumps enabled, and preferably a debug kernel so > you can do something with the dumps. The only thing I can see from > the messages you added was that you didn't have dumps enabled. I definitely have dumps enabled on a certain 3.0-CURRENT box (as of Nov 5), yet no dump took place. As far as I know, I let a ktrace run for a while on a process that did a *lot* of I/O, and then did a 'ktrace -C', got myself one last '$ ' prompt, and nothing more. This happened this afternoon, so no go for you simultaneous unrelated but linked events weirdos :-) Sorry, nothing more, AFAIK it wasn't even writing to a softupdates filesystem... Setting dumpdev in /etc/rc.conf should be enough, no? And that should (could) translate to the following being visible during runtime: % sysctl -a | grep dump kern.dumpdev: { major = 4, minor = 131073 } kern.sugid_coredump: 0 machdep.do_dump: 1 that corresponds with my swap device (/dev/da0s1b, which is large enough to contain a complete dump), /var/crash has enough free, savecore did run according to my syslog (and produced an identical result when run later by hand). Anyway, sorry that I can't be of more help... did that NFS patch get committed? I'd like to try an installworld from an NFS-mounted /usr/obj. (It should be possible to do the actual build on another machine and then only install the result on other machines, right?) -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:13:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03116 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:13:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hotrats.apl.washington.edu (hotrats.apl.washington.edu [128.95.76.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03111 for ; Mon, 16 Nov 1998 15:13:25 -0800 (PST) (envelope-from kargl@hotrats.apl.washington.edu) Received: (from kargl@localhost) by hotrats.apl.washington.edu (8.9.1/8.8.8) id PAA12153; Mon, 16 Nov 1998 15:17:03 -0800 (PST) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <199811162317.PAA12153@hotrats.apl.washington.edu> Subject: Re: kernel panics with SMP In-Reply-To: <19981117092941.N717@freebie.lemis.com> from Greg Lehey at "Nov 17, 1998 9:29:41 am" To: grog@lemis.com (Greg Lehey) Date: Mon, 16 Nov 1998 15:17:03 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Greg Lehey: > On Monday, 16 November 1998 at 13:37:49 -0800, Steven G. Kargl wrote: > > FreeBSD-current, cvsup'd on Saturday 14 Nov 98. > > > > SMP system, Micron Millenium Pro2 (dual Pentium Pro) with > > 256 MB memory, Adaptec 2940 controller, 1 $.3 GB seagate drive. > > > > DDB message: > > [trace deleted] > > It would be nice to see the panic string, but it's pretty sure to be > "ffs_blkfree: bad size". It looks as if it's fixed; wait a day or > so. In the meantime, you can work around it with > > # sysctl -w vfs.ffs.doreallocblks=0 > Thanks. My problem may be a combination of a broken BIOS and a out-of-date config(8). On the bright side, I've learned about the dangers with an async mount option. Luckily, this is a new install, and I did not lose anything of importance. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:22:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04063 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:22:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04057 for ; Mon, 16 Nov 1998 15:22:14 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id SAA00382 for ; Mon, 16 Nov 1998 18:21:50 -0500 (EST) Message-Id: <4.1.19981116174945.00a5fa00@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 16 Nov 1998 18:00:25 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: <19981116200312.A8700@klemm.gtn.com> References: <4.1.19981116111511.00b92100@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem is not resolved as of a build world done today around noonish (EST). I've been experimenting with different network activity... ran a CVSup and it happened again (the system rebooted). Other activity that was present included small mail traffic, and MP3's being served via httpd (apache_1.3.3). Platform is 300mhz Pentium II with 128meg of RAM, ahc scsi interface. I am beginning to suspect a filesystem bug. When this happens, something doesn't get handled correctly with the standard fsck. I end up having to bring my machine into single-user mode to perform the fsck manually. Anyone else? (cvsup.freebsd.org seems to be overloaded with cvs connections, I can't get in right now) Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:37:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05630 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:37:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05620; Mon, 16 Nov 1998 15:37:00 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id PAA04930; Mon, 16 Nov 1998 15:36:29 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 16 Nov 1998 15:36:29 -0800 (PST) From: Doug White To: Stephen Comoletti cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <003301bbd373$83d206e0$118809d0@oemcomputer> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Nov 1996, Stephen Comoletti wrote: > Need a little help tracking down the cause of a crash. I have a web server > setup on a HP Pavilion pentium II/333 with 168 megs ram, a 8gig ata33 ide > drive, and lynksys 10bt ether. Nothing paticularly unusual. The install went > picture perfect aside from a few probs making bsd recognize the ether card > (win95 and 98 both had even harder time finding that darn card, so no > surprise). It is a test machine for a new web server we plan to setup. I am > using Zeus as a web server. I have basically secured the machine. shut off > inetd, use ssh only (1.2.26), and applied the nestea patch to ip_input.c, thats > about it. I've run it over 8 to 10 hour periods with occasional reboots as I > setup the machine for a week. I put it up for the weekend for the first time, > starting it friday evening around 4 and leaving a number of pearl scripts setup > to pound away on the web server non stop from other machines in the office. It > was taking about 16k hits per hour and didnt seem to notice it. > > So, sunday evening at 22:52 it crashed with the following: > > Nov 15 22:52:37 <0.2> somnus /kernel: Fatal trap 12: page fault while in kernel > mode What version of FreeBSD is this? Ideally if you could get a crashdump and stack backtrace with a -g kernel .. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05813 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:39:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05805 for ; Mon, 16 Nov 1998 15:39:21 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA06498; Tue, 17 Nov 1998 10:08:54 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA02978; Tue, 17 Nov 1998 10:08:53 +1030 (CST) Message-ID: <19981117100853.V717@freebie.lemis.com> Date: Tue, 17 Nov 1998 10:08:53 +1030 From: Greg Lehey To: "Steven G. Kargl" Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel panics with SMP References: <19981117092941.N717@freebie.lemis.com> <199811162317.PAA12153@hotrats.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811162317.PAA12153@hotrats.apl.washington.edu>; from Steven G. Kargl on Mon, Nov 16, 1998 at 03:17:03PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 16 November 1998 at 15:17:03 -0800, Steven G. Kargl wrote: > According to Greg Lehey: >> On Monday, 16 November 1998 at 13:37:49 -0800, Steven G. Kargl wrote: >>> FreeBSD-current, cvsup'd on Saturday 14 Nov 98. >>> >>> SMP system, Micron Millenium Pro2 (dual Pentium Pro) with >>> 256 MB memory, Adaptec 2940 controller, 1 $.3 GB seagate drive. >>> >>> DDB message: >>> > > [trace deleted] > >> >> It would be nice to see the panic string, but it's pretty sure to be >> "ffs_blkfree: bad size". It looks as if it's fixed; wait a day or >> so. In the meantime, you can work around it with >> >> # sysctl -w vfs.ffs.doreallocblks=0 >> > > Thanks. > > My problem may be a combination of a broken BIOS and a out-of-date > config(8). Looking at that backtrace, it looks like your problem is due to a kernel bug. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:42:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06358 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:42:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06275 for ; Mon, 16 Nov 1998 15:42:20 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id PAA00512; Mon, 16 Nov 1998 15:41:45 -0800 (PST) Date: Mon, 16 Nov 1998 15:43:00 -0800 (PST) From: Tom Bartol To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: <4.1.19981116174945.00a5fa00@206.25.93.69> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Forrest Aldrich wrote: [snip] > I am beginning to suspect a filesystem bug. When this happens, something > doesn't > get handled correctly with the standard fsck. I end up having to bring my > machine > into single-user mode to perform the fsck manually. > > Anyone else? > I'm getting the crashes but fsck is able to repair my system just fine. I haven't been able to get a dump. The crashes occur during heavy local file I/O (such as a buildworld or cvsup of ports-all). This is on a system current as of 8:OOAM PST this morning. 400MHz PII SMP 512MB RAM, / and /usr on SEAGATE ST34502LW with adaptec 7890, /usr/scratch is RAID 0 on two IBM 9ZX's with DPT PM3334UW FW Rev. 07M0, 2 channels. I'm running a current kernel from Oct 29 at the moment as a work-around -- Trying to buildworld cvsupped moments ago to see if the problem has in fact been fixed as has been mentioned. If not, I'll get more hard-nosed about capturing a useful dump... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 15:59:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08550 for freebsd-current-outgoing; Mon, 16 Nov 1998 15:59:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hotrats.apl.washington.edu (hotrats.apl.washington.edu [128.95.76.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08542 for ; Mon, 16 Nov 1998 15:59:31 -0800 (PST) (envelope-from kargl@hotrats.apl.washington.edu) Received: (from kargl@localhost) by hotrats.apl.washington.edu (8.9.1/8.8.8) id QAA12246; Mon, 16 Nov 1998 16:03:15 -0800 (PST) (envelope-from kargl) From: "Steven G. Kargl" Message-Id: <199811170003.QAA12246@hotrats.apl.washington.edu> Subject: Re: kernel panics with SMP In-Reply-To: <19981117100853.V717@freebie.lemis.com> from Greg Lehey at "Nov 17, 1998 10: 8:53 am" To: grog@lemis.com (Greg Lehey) Date: Mon, 16 Nov 1998 16:03:14 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG me: > > > > Thanks. > > > > My problem may be a combination of a broken BIOS and a out-of-date > > config(8). Greg: > Looking at that backtrace, it looks like your problem is due to a > kernel bug. I not claiming that a bug does not exists, but with an out-of-date config(8) I may have (or have not) properly defined an option during kernel builds. A simple "make -j 4" in sys/compile/TROUTMASK would hang my machine in minutes. I've turned off a broken BIOS feature and set /usr to be mounted with sync. Several kernel builds have gone off without incidence, and I've built tex and friends from scratch without incidence. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 16:00:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08883 for freebsd-current-outgoing; Mon, 16 Nov 1998 16:00:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feeding.frenzy.com (feeding.frenzy.com [209.198.128.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08854 for ; Mon, 16 Nov 1998 16:00:18 -0800 (PST) (envelope-from bhauber@feeding.frenzy.com) Received: (from bhauber@localhost) by feeding.frenzy.com (8.8.8/8.8.7) id RAA15482 for current@freebsd.org; Mon, 16 Nov 1998 17:59:50 -0600 (CST) Message-ID: <19981116175950.A15393@frenzy.com> Date: Mon, 16 Nov 1998 17:59:50 -0600 From: Brian Hauber To: current@FreeBSD.ORG Subject: 3.0 problems Reply-To: bhauber@pobox.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I downloaded boot.flp from ftp.freebsd.org, wrote it out to a floppy using 'fdimage', and booted off of it. When all of the kernel debug information scrolls by, I noted, that wdc1 is not being found. Every other boot floppy I've used (2.2.0 thru 2.2.7) had no problems finding wdc1. It's looking at the same 'port' 0x170 and the same interrupt INT 15. If you need any further information regarding my system configuration, let me know. Please direct all responses to me, as I am not a member of this list. Thanks Brian -- Brian Hauber | http://www.pobox.com/~bhauber | bhauber@pobox.com PGP fingerprint = 0C 9B 2B 4F F8 68 12 81 DC 0A 13 43 FF 50 D0 1F To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 18:37:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28241 for freebsd-current-outgoing; Mon, 16 Nov 1998 18:37:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28235 for ; Mon, 16 Nov 1998 18:37:10 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id TAA12858; Mon, 16 Nov 1998 19:36:46 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd012847; Mon Nov 16 19:36:41 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id TAA05399; Mon, 16 Nov 1998 19:36:40 -0700 (MST) From: Terry Lambert Message-Id: <199811170236.TAA05399@usr05.primenet.com> Subject: Re: linux bugs To: bde@zeta.org.au (Bruce Evans) Date: Tue, 17 Nov 1998 02:36:40 +0000 (GMT) Cc: bde@zeta.org.au, jkh@zippy.cdrom.com, current@FreeBSD.ORG In-Reply-To: <199811110812.TAA32188@godzilla.zeta.org.au> from "Bruce Evans" at Nov 11, 98 07:12:24 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Installing linux from sys/modules/linux/ clobbers the version installed > >> from lkm/linux/, and vice versa. Breakage is limited by bugs in > > > >Given that modules are meant to replace lkms, I don't find that > >particularly odd. > > It's odd when the lkm one wins. Peter just fixed this. It's pure darwinism. I had just finished winning "core wars" when I went to code up the LKM subsystem... ;-) Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 19:17:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02524 for freebsd-current-outgoing; Mon, 16 Nov 1998 19:17:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02517 for ; Mon, 16 Nov 1998 19:17:14 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id TAA14245; Mon, 16 Nov 1998 19:16:49 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id TAA19874; Mon, 16 Nov 1998 19:16:49 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 16 Nov 1998 19:16:49 -0800 (PST) Message-Id: <199811170316.TAA19874@vashon.polstra.com> To: forrie@forrie.com Subject: Re: Nasty rebooting in 3.0 current Newsgroups: polstra.freebsd.current In-Reply-To: <4.1.19981116174945.00a5fa00@206.25.93.69> References: <4.1.19981116111511.00b92100@206.25.93.69> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.1.19981116174945.00a5fa00@206.25.93.69>, Forrest Aldrich wrote: > (cvsup.freebsd.org seems to be overloaded with cvs connections, I can't get in > right now) Then I suggest you use cvsup2.freebsd.org or cvsup3.freebsd.org. Both are generally underutilized compared to cvsup.freebsd.org. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 20:50:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13403 for freebsd-current-outgoing; Mon, 16 Nov 1998 20:50:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (tex-30.camalott.com [208.229.74.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA13398 for ; Mon, 16 Nov 1998 20:50:10 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA01425; Mon, 16 Nov 1998 22:49:38 -0600 (CST) (envelope-from joelh) To: Open Systems Networking Cc: Bryan Fullerton , freebsd-current@FreeBSD.ORG Subject: Re: proc changes References: From: Joel Ray Holveck Date: 16 Nov 1998 22:49:37 -0600 In-Reply-To: Open Systems Networking's message of "Sun, 15 Nov 1998 16:02:28 -0500 (EST)" Message-ID: <86pvamzzxa.fsf@detlev.UUCP> Lines: 21 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > *grumble* *grumble* > Ok for the Nth time :-) > You need to rebuild libkvm and associated utils and build a new kernel. > Im wondering if anyone reads current. :) > Actually ive been guilty of that myself in the past you dont read the > HEADS-UP or the repeated threads till your bitten. then its too late cause > they threads have died. Oh well maybe one day well get that real-time > trouble ticket system on the web :-) Okay, what do you think of having lists with *only* heads-up info for -current and -stable, with easily accessible archives? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 21:09:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15393 for freebsd-current-outgoing; Mon, 16 Nov 1998 21:09:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15385 for ; Mon, 16 Nov 1998 21:09:06 -0800 (PST) (envelope-from furuta@sra.co.jp) Received: from sramhc.sra.co.jp (sramhc [133.137.20.31]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id OAA01624; Tue, 17 Nov 1998 14:08:24 +0900 (JST) Received: from sramhc.sra.co.jp (furuta@localhost [127.0.0.1]) by sramhc.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id OAA28556; Tue, 17 Nov 1998 14:08:38 +0900 (JST) Message-Id: <199811170508.OAA28556@sramhc.sra.co.jp> To: freebsd-current@FreeBSD.ORG Cc: newconfig@jp.freebsd.org Subject: newconfig patch released Mime-Version: 1.0 X-Mailer: Mew version 1.70 on Emacs 19.28.7 / Mule 2.2 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 17 Nov 1998 14:08:38 +0900 From: Atsushi Furuta Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [1] Call for Testers. We, newconfig project, are porting the new device driver configuration system used in NetBSD and BSD/OS. Our work is based on FreeBSD-current. It is nowhere near finished, but is working to some extent. We decided to publish a patch to 3.0-RELEASE and call for testers and developers, especially people who can port device drivers. You can find the patch at: http://www.jp.freebsd.org/~furuta/newconf_30_981026.diff.gz Any comments and questions on this patch should be addressed to: newconfig@jp.FreeBSD.ORG (in English) newconfig-jp@jp.FreeBSD.ORG (in Japanese) Newconfig testers and device driver developers are requested to subscribe to one of the mailing lists. (Subscribers of newconfig-jp will also receive mails on the newconfig mailing list.) To subscribe to newconfig mailing list, please send an E-mail to majordomo@jp.freebsd.org including the line, subscribe newconfig in the body part. Information about newconfig project can be found at: http://www.jp.freebsd.org/newconfig/index.html (in English) http://www.jp.freebsd.org/newconfig/index-j.html (in Japanese) [2] about this patch This patch is intended for testing only. The kernel with this patch can be compiled and booted in the 3.0-RELEASE system, but has some limitations: * SCSI devices are not supported. SCSI devices are not recognized, so you need IDE system drives for testing. * ATAPI devices are not supported. * Device supported are still very limited. Tested and working devices are: + ISA syscons, psm, wd + ISA-PnP ed + PCI ed, bktr + others npx, apm * Not tested but the devices expected to work are: + ISA sio, ed, ep + PCI cy, de, en, fpa, fxp, lnc, sr, tl, tx, vx, xl, meteor * NEC PC98 (Japanese domestic model) architecture is supported, but not tested. * Alpha is not supported. * You cannot use UserConfig. * Some commands cannot be used (e.g. dset), and some works with limited functionality (e.g. vmstat). * There are probably many more undiscovered problems. [2.1] How to make newconfig kernel 1. Have a working FreeBSD-3.0-RELEASE system. We strongly suggest you to backup your data. 2. Extract source codes into /usr/src. You need /usr/src/sys as a minimum. Don't forget to make backups if you have any local changes. # cd /usr/src/ # mkdir sys.ORG # cd sys.ORG # (cd ../sys; tar cf - .) | tar xpf - 3. Apply the newconfig patch # cd /usr/src # zcat somewhere/newconf_30_981026.diff.gz | patch -p1 Check if the patch has been applied correctly. # find . -name '*.rej' -print 4. Make config.new # cd /usr/src/usr.sbin/config.new # make # make install Do not forget to rehash if you use csh and friends. 5. Edit your kernel configuration file for config.new. Sample configuration files are: /usr/src/sys/i386/conf/NEWCONF (for PC) /usr/src/sys/pc98/conf/NEWCONF98 (for NEC PC98) The syntax is different from that of conventional config, so please refer to the supplied samples. Note: You cannot use UserConfig with newconfig yet. # cd /usr/src/i386/conf # cp NEWCONF MYCONF # vi MYCONF 6. Invoke config.new # config.new MYCONF You will get some warning messages like these, but they are harmless and can be safely ignored. ../../i386/conf/Makefile.newconf.i386:114: unknown % construct ignored: %BEFORE_DEPEND ../../i386/conf/Makefile.newconf.i386:122: unknown % construct ignored: %MFILES ../../i386/conf/Makefile.newconf.i386:126: unknown % construct ignored: %CLEAN 7. Make kernel # cd ../../compile/MYCONF # make depend # make We recommend you do not do 'make install', as it is dangerous to have newconfig kernel as /kernel. Copy the kernel into root directory with another name. For example: # cp kernel /kernel.newconf When first time you boot with newconfig kernel, booting in single user mode is recommended. [3] Getting source codes via CVSup You can CVSup newconfig source from cvsup.jp.FreeBSD.ORG or its mirrors (cvsup[4-5].jp.FreeBSD.ORG). Example of CVSup file is: # Defaults that apply to all the collections *default host=cvsup.jp.freebsd.org *default base=/some/where/you/want *default prefix=/some/where/you/want/prefix *default release=cvs *default delete use-rel-suffix jp-newconfig [4] TODO These projects are listed as the highest priority by the newconfig project. If you are interested in helping this effort please subscribe to the mailing list and participate in the project. necessity difficulty A+ C * Support for PCI/ISA/ISA-PnP devices. A+ B+ * PC Card Support (PAO merge) A A+ * CAM Support B B * USB Support (porting?) A- A * CardBus Support A A- * Support for UserConfig, dset -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 16 23:42:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03909 for freebsd-current-outgoing; Mon, 16 Nov 1998 23:42:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp4.nwnexus.com (smtp4.nwnexus.com [206.63.63.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03903 for ; Mon, 16 Nov 1998 23:42:47 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx100-ip2.nwnexus.net [204.57.235.2]) by smtp4.nwnexus.com (8.8.8/8.8.8) with ESMTP id XAA32463 for ; Mon, 16 Nov 1998 23:42:01 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.1/8.8.8) id RAA04993 for current@FreeBSD.ORG; Sun, 15 Nov 1998 17:35:17 -0800 (PST) (envelope-from wrsomsky) Message-ID: <19981115173516.A4986@halcyon.com> Date: Sun, 15 Nov 1998 17:35:16 -0800 From: "William R. Somsky" To: current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, now that we've got the new 3-stage bootloader, and it looks like it's near to becoming the standard, I've got two questions: 1) Where is there documentation on it? 2) Will we have a DOS/WIN program to install a copy of the new boot0 when it gets trashed by a Windows install or other "disaster" ;-) ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 00:27:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08881 for freebsd-current-outgoing; Tue, 17 Nov 1998 00:27:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw1.pl.cp (ppp-pw16.nttca.com [204.160.176.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08871; Tue, 17 Nov 1998 00:27:49 -0800 (PST) (envelope-from astralblue@usa.net) Received: from localhost (gene@localhost) by gw1.pl.cp (8.9.1/8.9.1) with SMTP id AAA09075; Tue, 17 Nov 1998 00:27:01 -0800 (PST) (envelope-from astralblue@usa.net) X-Authentication-Warning: gw1.pl.cp: gene owned process doing -bs Date: Tue, 17 Nov 1998 00:27:01 -0800 (PST) From: "Eugene M. Kim" X-Sender: gene@gw1.pl.cp To: Garrett Wollman cc: FreeBSD-current Mailing List Subject: Re: cvs commit: src/sys/sys bus.h bus_private.h conf.h devicestat.h module.h src/sys/kern bus_if.m device_if.m kern_conf.c subr_bus.c subr_devstat.c In-Reply-To: <199811142158.NAA22480@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I'm afraid this commit broke a couple of bus devices such as smbus and iicbus that use bus_generic_create_intr; the routine was deleted from sys/kern/subr_bus.c. Is there a workaround, or must smbus.c and iicbus.c be rewritten per the new interface? These busses are necessary for bktr0; I really miss it :-p. Thank you, Eugene Kim On Sat, 14 Nov 1998, Garrett Wollman wrote: | wollman 1998/11/14 13:58:52 PST | | Modified files: | sys/sys bus.h bus_private.h conf.h devicestat.h | module.h | sys/kern bus_if.m device_if.m kern_conf.c | subr_bus.c subr_devstat.c | Log: | My changes to the new device interface: | | - Interface wth the new resource manager. | - Allow for multiple drivers implementing a single devclass. | - Remove ordering dependencies between header files. | - Style cleanup. | - Add DEVICE_SUSPEND and DEVICE_RESUME methods. | - Move to a single-phase interrupt setup scheme. | | Kernel builds on the Alpha are brken until Doug gets a chance to incorporate | these changes on that side. | | Agreed to in principle by: dfr | | Revision Changes Path | 1.7 +140 -71 src/sys/sys/bus.h | 1.4 +3 -3 src/sys/sys/bus_private.h | 1.48 +13 -18 src/sys/sys/conf.h | 1.3 +2 -2 src/sys/sys/devicestat.h | 1.5 +9 -9 src/sys/sys/module.h | 1.5 +67 -19 src/sys/kern/bus_if.m | 1.3 +15 -1 src/sys/kern/device_if.m | 1.29 +3 -3 src/sys/kern/kern_conf.c | 1.10 +199 -66 src/sys/kern/subr_bus.c | 1.5 +2 -2 src/sys/kern/subr_devstat.c | | To Unsubscribe: send mail to majordomo@FreeBSD.org | with "unsubscribe cvs-all" in the body of the message | Eugene M. Kim "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 00:48:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA10523 for freebsd-current-outgoing; Tue, 17 Nov 1998 00:48:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-41-dbn.dial-up.net [196.34.155.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA10465 for ; Tue, 17 Nov 1998 00:47:54 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id KAA08338; Tue, 17 Nov 1998 10:46:15 +0200 (SAT) From: Robert Nordier Message-Id: <199811170846.KAA08338@ceia.nordier.com> Subject: Re: [3-stage bootstrap] In-Reply-To: <19981115173516.A4986@halcyon.com> from "William R. Somsky" at "Nov 15, 98 05:35:16 pm" To: wrsomsky@halcyon.com (William R. Somsky) Date: Tue, 17 Nov 1998 10:46:12 +0200 (SAT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG William R. Somsky wrote: > Ok, now that we've got the new 3-stage bootloader, and it looks like > it's near to becoming the standard, I've got two questions: > > 1) Where is there documentation on it? There is currently no boot0 documentation. However, there are a few obscure configuration options, etc., so something is probably required. For boot1/boot2, most of the present boot(8) man page applies, though some information needs to be updated, and additional capabilities documented. Someone has also submitted a boot.config(8) man page (PR 8610), though this hasn't been committed. For the boot loader, there is some brief online-style documentation in src/sys/boot/common/help.common and src/sys/boot/i386/loader/help.i386. This will most likely be considerably expanded as the loader assumes its final form. > 2) Will we have a DOS/WIN program to install a copy of the new boot0 > when it gets trashed by a Windows install or other "disaster" ;-) I hadn't really thought about this, but given Windows' predilection for silently "taking out" the master boot record, I guess this does need doing. Unfortunately maintaining DOS programs that support FreeBSD tends to be a major headache; but it may be possible to cross-compile something using bcc (Bruce Evans' 16-bit C compiler in the ports collection). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 00:54:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11257 for freebsd-current-outgoing; Tue, 17 Nov 1998 00:54:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11251 for ; Tue, 17 Nov 1998 00:54:41 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id JAA26038; Tue, 17 Nov 1998 09:52:42 +0100 (CET) To: Kevin Day cc: current@FreeBSD.ORG Subject: Re: MediaGX and calcru: negative time In-reply-to: Your message of "Mon, 16 Nov 1998 17:11:54 CST." <199811162311.RAA09337@home.dragondata.com> Date: Tue, 17 Nov 1998 09:52:42 +0100 Message-ID: <26036.911292762@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> FreeBSD 2.2.7-RELEASE #0: Wed Oct 21 16:22:35 CDT 1998 >> devel@kevin1.touchmaster:/usr/src/sys/compile/DEVEL >> CPU: Cyrix GXm (0.00-MHz 586-class CPU) >> Origin = "CyrixInstead" Id = 0x540 DIR=0x3346 Stepping=3 Revision=3 >> real memory = 63963136 (62464K bytes) >> avail memory = 60252160 (58840K bytes) > >FreeBSD 3.0-RELEASE #0: Mon Nov 16 16:10:02 CST 1998 > root@kevin1.touchmaster:/usr/src/sys/compile/DEVEL >Timecounter "i8254" frequency 1193182 Hz cost 40336 ns >Timecounter "TSC" frequency 20172892 Hz cost 180 ns >CPU: Cyrix GXm (20.17-MHz 586-class CPU) > Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 > Features=0x808131 >real memory = 63963136 (62464K bytes) >avail memory = 60243968 (58832K bytes) >According to date, i'm running about 15-30x the speed I should be. > >Has anyone else reported this for a GXm? This is because the speed of your TSC counter is WAY wrong. If you know what frequency it should be, sysctl -w kern.timecounter.frequency=XXXXXX where XXXXXX is that frequency in Hz. Even better yet, try to find out why the frequency is so wrong in sys/isa/clock.c -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 02:03:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17954 for freebsd-current-outgoing; Tue, 17 Nov 1998 02:03:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17920 for ; Tue, 17 Nov 1998 02:02:52 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru (8.9.1a.NOMIME/8.9.1) with ESMTP id NAA03779 for ; Tue, 17 Nov 1998 13:02:13 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Tue, 17 Nov 1998 13:02:12 +0300 (MSK) From: "Roman V. Palagin" To: current@FreeBSD.ORG Subject: Inconsistency in udp_var.h and ip_var.h Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello! just found this kind of error in -current (cvsup'd about hour ago): in udp_var.h: struct udpiphdr { struct ipovly ui_i; /* overlaid ip structure */ struct udphdr ui_u; /* udp header */ }; #define ui_next ui_i.ih_next #define ui_prev ui_i.ih_prev in ip_var.h: struct ipovly { u_char ih_x1[9]; /* (unused) */ u_char ih_pr; /* protocol */ u_short ih_len; /* protocol length */ struct in_addr ih_src; /* source internet address */ struct in_addr ih_dst; /* destination internet address */ }; as you can see, there is no ih_next and ih_prev members in ipovly. should ui_next and ui_prev go away? ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 02:20:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA19649 for freebsd-current-outgoing; Tue, 17 Nov 1998 02:20:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zappa.demon.nl (zappa.demon.nl [195.173.232.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA19642 for ; Tue, 17 Nov 1998 02:20:20 -0800 (PST) (envelope-from root@zappa.demon.nl) Received: (from root@localhost) by zappa.demon.nl (8.9.1/8.8.8) id LAA00266; Tue, 17 Nov 1998 11:21:18 +0100 (CET) (envelope-from root) Message-ID: <19981117112118.A252@zappa.demon.nl> Date: Tue, 17 Nov 1998 11:21:18 +0100 From: Ron Klinkien To: Doug White Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adaptec SCSI messages References: <19981114144915.A244@zappa.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug White on Mon, Nov 16, 1998 at 04:03:13PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 16, 1998 at 04:03:13PM -0800, Doug White wrote: > On Sat, 14 Nov 1998, Ron Klinkien wrote: > > > I have my FreeBSD system running for a few weeks now, > > but during bootup there is a long timeout and a message > > displayed from the adaptec scsi adapter when > > there is a probe on my scsi disc. > > Check your termination, it looks like your SCSI hard disk isn't responding > immediately. Perhaps it needs to be spun up first? After some investigation about the fact that the drive didn't report 80Mb/s, and someone pointing out that it should do that with my config, after a while i figured out the drive wasn't correctly jumpered. ;-() Factory default is LVD mode, but mine was jumpered Single Ended. So I had a SE drive on a Ultra2 LVD cable, work ok , but I guessed the drive complained ones in a while with the msgs as result. After jumpering it right the facts at bootup are correct for the first time in 3 months ;-) Strange though that after doubling the data transfer rate from 40 -> 80Mb/s iozone 100 doesn't reports any increase of speed. Thanks for your response. Ron. > > > --- > > ahc0: rev 0x00 int a irq 10 on pci0.6.0 > > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > > --- > > Waiting 4 seconds for SCSI devices to settle > > (probe6:ahc0:0:6:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xf4 > > SEQADDR == 0x15b > > SSTAT1 == 0x2 > > (probe6:ahc0:0:6:0): Queuing a BDR SCB > > (probe6:ahc0:0:6:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xf4 > > SEQADDR == 0x15b > > SSTAT1 == 0x2 > > (probe6:ahc0:0:6:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 8 SCBs aborted > > changing root device to da0s1a > > da0 at ahc0 bus 0 target 6 lun 0 > > da0: Fixed Direct Access SCSI2 device > > da0: 40.0MB/s transfers (20.0MHz, offset 31, 16bit), Tagged Queueing Enabled > > da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) > > --- > > cd0 at ahc0 bus 0 target 1 lun 0 > > cd0: Removable CD-ROM SCSI2 device > > cd0: 20.0MB/s transfers (20.0MHz, offset 15) > > cd0: Attempt to query device size failed: NOT READY, Medium not present > > (da0:ahc0:0:6:0): tagged openings now 63 > > --- > > zappa# uname -a > > FreeBSD zappa.demon.nl 3.0-CURRENT FreeBSD 3.0-CURRENT #6: Thu Nov 12 21:04:50 > > CET 1998 root@zappa.demon.nl:/usr/src/sys/compile/UMRK5 i386 > > Er, current questions should go to current@freebsd.org. > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- --- "You could jam in Joe's garage..." -FZ Ron Klinkien System Engineer ron@zappa.demon.nl http://www.zappa.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 02:40:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA21512 for freebsd-current-outgoing; Tue, 17 Nov 1998 02:40:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21443 for ; Tue, 17 Nov 1998 02:39:59 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA05148; Tue, 17 Nov 1998 10:38:40 GMT Date: Tue, 17 Nov 1998 10:38:40 +0000 (GMT) From: Doug Rabson To: Julian Elischer cc: Terry Lambert , jkh@zippy.cdrom.com, green@unixhelp.org, peter@netplex.com.au, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: Is it soup yet? :-) In-Reply-To: <36509430.2781E494@whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Julian Elischer wrote: > Terry Lambert wrote: > > > > > > > > > Call be crazy, but I think I'd almost like to move the "real" kernel to > > > > > > > /boot/kernel, providing the search paths were ok. > > > > > > > > > > > > You're absolutely nuts. > > > > > > > > > > Can we get postings in -current back on track? I'm seeing enough > > > > > Brian Feldman posts to justify a filter. > > > > > > > > The "mini FFS" used by the boot blocks doesn't know how to traverse > > > > subdirectories. > > > > > > Actually it does. > > > > Then someone added it more recently than the original version > > from CSRG. > > > > Terry Lambert > > terry@lambert.org > > --- > > Any opinions in this posting are my own and not those of my present > > or previous employers. > > I think you're confusing two bits of code.. > > the miniFFS came via me, from the MACH bootblocks > > the stuff from CSRG (via Bill Jolitz) was junked in 92. In the alpha loader, I use Julian's FFS code to locate /boot/loader (because that bit has to fit into the 8k bootarea) and then the one from libstand for loading everything else. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 02:59:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23843 for freebsd-current-outgoing; Tue, 17 Nov 1998 02:59:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23838 for ; Tue, 17 Nov 1998 02:59:32 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA05238; Tue, 17 Nov 1998 10:52:44 GMT Date: Tue, 17 Nov 1998 10:52:44 +0000 (GMT) From: Doug Rabson To: "Roman V. Palagin" cc: current@FreeBSD.ORG Subject: Re: Inconsistency in udp_var.h and ip_var.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Roman V. Palagin wrote: > hello! > > just found this kind of error in -current (cvsup'd about hour ago): > > in udp_var.h: > > struct udpiphdr { > struct ipovly ui_i; /* overlaid ip structure */ > struct udphdr ui_u; /* udp header */ > }; > #define ui_next ui_i.ih_next > #define ui_prev ui_i.ih_prev > > in ip_var.h: > > struct ipovly { > u_char ih_x1[9]; /* (unused) */ > u_char ih_pr; /* protocol */ > u_short ih_len; /* protocol length */ > struct in_addr ih_src; /* source internet address */ > struct in_addr ih_dst; /* destination internet address */ > }; > > as you can see, there is no ih_next and ih_prev members in ipovly. should > ui_next and ui_prev go away? Yes they should. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 03:23:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25912 for freebsd-current-outgoing; Tue, 17 Nov 1998 03:23:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA25907 for ; Tue, 17 Nov 1998 03:22:56 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.sanpei.org (u4168.seaple.icc.ne.jp [203.140.32.168]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id UAA21560; Tue, 17 Nov 1998 20:22:12 +0900 (JST) Received: (from sanpei@localhost) by lavender.sanpei.org (8.8.8/3.6W) id UAA01911; Tue, 17 Nov 1998 20:22:10 +0900 (JST) Date: Tue, 17 Nov 1998 20:22:10 +0900 (JST) Message-Id: <199811171122.UAA01911@lavender.sanpei.org> To: toasty@home.dragondata.com Cc: current@FreeBSD.ORG, sanpei@sanpei.org, cjohnson@netgsi.com Subject: Re: MediaGX and calcru: negative time In-Reply-To: Your message of "Tue, 17 Nov 1998 03:30:32 JST". <199811161830.MAA16210@home.dragondata.com> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Ok... I'm using a Media GXm in an embedded product with FreeBSD... I'm >> getting the annoying 'calcru' messages, and processes dying. >> >> Copyright (c) 1992-1998 FreeBSD Inc. >> Copyright (c) 1982, 1986, 1989, 1991, 1993 >> The Regents of the University of California. All rights reserved. >> >> FreeBSD 2.2.7-RELEASE #0: Wed Oct 21 16:22:35 CDT 1998 >> devel@kevin1.touchmaster:/usr/src/sys/compile/DEVEL >> CPU: Cyrix GXm (0.00-MHz 586-class CPU) >> Origin = "CyrixInstead" Id = 0x540 DIR=0x3346 Stepping=3 Revision=3 >> real memory = 63963136 (62464K bytes) >> avail memory = 60252160 (58840K bytes) >> >> >> Now, since Cyrix is supporting us with this product, are there any questions >> I can ask them that may shed some light? >> >> It appears that the problem is brought out by lots of IDE access. The IDE >> interface is done internaly, in the CPU. Could timeouts/delays in the IDE >> side be slowing the clock somehow? >> >> Tell me what to ask, and I will. :) I have MediaGX box. I install 2.2.6R. I also have this problem..... But my problem is only calcru, and can't detect psm0(PS/2) port. Sometimes can't detect Ethernet Card(occasionally automatically rebooted...). This problem (I think) already reported to GNATS Problem repository, kern/6630[1] which is included experimental patch. Please apply this patch. This Patch is ``check timer twice, and use larger one at getit:clock.c''. Another person who has also MediaGX box, reported me that his MediaGX box is needed 4 times to detect correct one. I had planning to report this problem to GNATS Database and Mr Christopher T. Johnson. [1] kern/6630: Fix for Cyrix I8254 bug http://www.freebsd.org/cgi/query-pr.cgi?pr=6630 Thank you MIHIRA Yoshiro ----- 4times patch --- /sys/i386/isa/clock.c Sun Apr 27 22:44:19 1997 +++ ./clock.c Mon Nov 2 17:01:55 1998 @@ -345,7 +345,9 @@ { u_long ef; int high, low; - +#ifdef CPU_CYRIX_NO_I8254_LATCH + int ret1, ret2, ret3, ret4; +#endif ef = read_eflags(); disable_intr(); @@ -354,9 +356,32 @@ low = inb(TIMER_CNTR0); high = inb(TIMER_CNTR0); +#ifdef CPU_CYRIX_NO_I8254_LATCH + ret1 = (high << 8) | low; + outb(TIMER_MODE, TIMER_SEL0 | TIMER_LATCH); + low = inb(TIMER_CNTR0); + high= inb(TIMER_CNTR0); + ret2 = (high << 8) | low; + + outb(TIMER_MODE, TIMER_SEL0 | TIMER_LATCH); + low = inb(TIMER_CNTR0); + high= inb(TIMER_CNTR0); + ret3 = (high << 8) | low; + + outb(TIMER_MODE, TIMER_SEL0 | TIMER_LATCH); + low = inb(TIMER_CNTR0); + high= inb(TIMER_CNTR0); + ret4 = (high << 8) | low; +#endif write_eflags(ef); +#ifdef CPU_CYRIX_NO_I8254_LATCH + ret1 = (ret1 > ret2 ? ret1 : ret2); + ret3 = (ret3 > ret4 ? ret3 : ret4); + return (ret1 > ret3 ? ret1 : ret3); +#else return ((high << 8) | low); +#endif } /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 04:04:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01862 for freebsd-current-outgoing; Tue, 17 Nov 1998 04:04:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01733 for ; Tue, 17 Nov 1998 04:04:25 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru (8.9.1a.NOMIME/8.9.1) with ESMTP id PAA04097; Tue, 17 Nov 1998 15:02:13 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Tue, 17 Nov 1998 15:02:12 +0300 (MSK) From: "Roman V. Palagin" To: Phil Regnauld cc: Doug White , current@FreeBSD.ORG Subject: Re: IPv6 and -current In-Reply-To: <19981116224929.52241@stimpy.prosa.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Phil Regnauld wrote: > Doug White writes: > > > > There's a couple at least, see http://www.freebsd.org/projects. AFAIK > > both projects are against -STABLE code. > > Actually the INRIA stuff (from Francis Dupont/INRIA in fact) > was ported to -current twice by Pierre Beyssac. Yes, it was, but it's outdated now. (this is from frmug.org) ftp> ls pub/ipv6 ipv6-19980326.tar.gz ipv6-19980402.tar.gz ipv6-19980517.tar.gz ipv6-19980519.tar.gz ipv6-19980527.tar.gz 226 Transfer complete. ftp> ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 04:50:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06861 for freebsd-current-outgoing; Tue, 17 Nov 1998 04:50:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06855 for ; Tue, 17 Nov 1998 04:50:43 -0800 (PST) (envelope-from opsys@mail.webspan.net) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970608) with SMTP id HAA26137; Tue, 17 Nov 1998 07:50:14 -0500 (EST) Date: Tue, 17 Nov 1998 07:50:10 -0500 (EST) From: Open Systems Networking X-Sender: opsys@orion.webspan.net To: Joel Ray Holveck cc: Bryan Fullerton , freebsd-current@FreeBSD.ORG Subject: Re: proc changes In-Reply-To: <86pvamzzxa.fsf@detlev.UUCP> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16 Nov 1998, Joel Ray Holveck wrote: > Okay, what do you think of having lists with *only* heads-up info for > -current and -stable, with easily accessible archives? Personally I dont think anyone will read them. They dont seem to read the *HEADS-UP* messages on current and another list that isnt read is just a waste of time IMO.Well just have to keep chuggin with what we have and answer the occasional storm of repeated *me too* problems. Chris -- "You both seem to be ignoring the fact that the networking market is driven by so-called 'IT professionals' these days, most of whom can't tell the difference between an ARP and a carp." --Wes Peters ===================================| Open Systems FreeBSD Consulting. FreeBSD 3.0 is available now! | Phone: (402)573-9124 / ICQ # 20016186 -----------------------------------| 3335 N. 103 Plaza, Omaha, NE 68134 FreeBSD: The power to serve! | E-Mail: opsys@open-systems.net http://www.freebsd.org | Consulting, Network Engineering, Security ===================================| http://open-systems.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 05:09:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09043 for freebsd-current-outgoing; Tue, 17 Nov 1998 05:09:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09038 for ; Tue, 17 Nov 1998 05:09:02 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.47]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA42A6; Tue, 17 Nov 1998 14:08:34 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981112232834.48551@breizh.prism.uvsq.fr> Date: Tue, 17 Nov 1998 14:13:06 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Nicolas Souchu Subject: Re: ZIP+ and NatSemi parallel port chipst (was Re: ZIP, again) Cc: FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12-Nov-98 Nicolas Souchu wrote: > On Mon, Nov 09, 1998 at 11:13:27PM +0100, Jeroen Ruigrok/Asmodai wrote: >>> In fact, we have some problems with NSC chips here. >>> >>> Anybody could report successfull ZIP+ detection with NatSemi chips? >> >>So I guess it's detected alright... Now to know how to use it *G* > > You can't use it? Well it gets probed as da2... Except all my devices in fstab are still sd instead of their da counterparts. I wanted to convert them, but found the man-pages to be sketchy at best, and since I don't want to disable my system again ;) regards, --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 05:29:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA11064 for freebsd-current-outgoing; Tue, 17 Nov 1998 05:29:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA11057 for ; Tue, 17 Nov 1998 05:29:03 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id IAA19605; Tue, 17 Nov 1998 08:26:54 -0500 (EST) Date: Tue, 17 Nov 1998 08:26:54 -0500 (EST) From: Chuck Robey To: Jeroen Ruigrok/Asmodai cc: Nicolas Souchu , FreeBSD Current Subject: Re: ZIP+ and NatSemi parallel port chipst (was Re: ZIP, again) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > On 12-Nov-98 Nicolas Souchu wrote: > > On Mon, Nov 09, 1998 at 11:13:27PM +0100, Jeroen Ruigrok/Asmodai wrote: > >>> In fact, we have some problems with NSC chips here. > >>> > >>> Anybody could report successfull ZIP+ detection with NatSemi chips? > >> > >>So I guess it's detected alright... Now to know how to use it *G* > > > > You can't use it? > > Well it gets probed as da2... Except all my devices in fstab are still sd > instead of their da counterparts. I wanted to convert them, but found the > man-pages to be sketchy at best, and since I don't want to disable my system > again ;) The sd* and da* devices have the same major/minor numbers. Cam is color-blind at that range, you haven't anything to worry about. It's probably a good idea to update your devices and fstab, against some future change, but right now, it doesn't matter. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 05:44:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13290 for freebsd-current-outgoing; Tue, 17 Nov 1998 05:44:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13285 for ; Tue, 17 Nov 1998 05:44:42 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:uiCdh5QQ/EI9Y+2FtLbnt2J14Wj2m37f@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id WAA06109; Tue, 17 Nov 1998 22:37:11 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA01137; Tue, 17 Nov 1998 22:38:36 +0900 (JST) Message-Id: <199811171338.WAA01137@zodiac.mech.utsunomiya-u.ac.jp> To: Poul-Henning Kamp cc: Kevin Day , current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: MediaGX and calcru: negative time In-reply-to: Your message of "Tue, 17 Nov 1998 09:52:42 +0100." <26036.911292762@critter.freebsd.dk> References: <26036.911292762@critter.freebsd.dk> Date: Tue, 17 Nov 1998 22:38:35 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> FreeBSD 2.2.7-RELEASE #0: Wed Oct 21 16:22:35 CDT 1998 >>> devel@kevin1.touchmaster:/usr/src/sys/compile/DEVEL >>> CPU: Cyrix GXm (0.00-MHz 586-class CPU) >>> Origin = "CyrixInstead" Id = 0x540 DIR=0x3346 Stepping=3 Revision=3 >>> real memory = 63963136 (62464K bytes) >>> avail memory = 60252160 (58840K bytes) >> >>FreeBSD 3.0-RELEASE #0: Mon Nov 16 16:10:02 CST 1998 >> root@kevin1.touchmaster:/usr/src/sys/compile/DEVEL >>Timecounter "i8254" frequency 1193182 Hz cost 40336 ns >>Timecounter "TSC" frequency 20172892 Hz cost 180 ns >>CPU: Cyrix GXm (20.17-MHz 586-class CPU) >> Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 >> Features=0x808131 >>real memory = 63963136 (62464K bytes) >>avail memory = 60243968 (58832K bytes) > >>According to date, i'm running about 15-30x the speed I should be. >> >>Has anyone else reported this for a GXm? > >This is because the speed of your TSC counter is WAY wrong. > >If you know what frequency it should be, > sysctl -w kern.timecounter.frequency=XXXXXX >where XXXXXX is that frequency in Hz. > >Even better yet, try to find out why the frequency is so wrong >in sys/isa/clock.c The probelem report kern/6630 "[PATCH] Fix for Cyrix I8254 bug" has a possible explanation and a patch. I have heard from a couple of users that while the patch does not completely eradicate the problem, it makes things much better. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 06:51:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21232 for freebsd-current-outgoing; Tue, 17 Nov 1998 06:51:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21215 for ; Tue, 17 Nov 1998 06:51:28 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem17.masternet.it [194.184.65.27]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id PAA27092; Tue, 17 Nov 1998 15:50:30 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <199811171450.PAA27092@scotty.masternet.it> From: "Gianmarco Giovannelli" To: Tom Bartol Date: Tue, 17 Nov 1998 15:58:17 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Nasty rebooting in 3.0 current Reply-to: gmarco@giovannelli.it CC: freebsd-current@FreeBSD.ORG References: <4.1.19981116174945.00a5fa00@206.25.93.69> In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am beginning to suspect a filesystem bug. When this happens, something > > doesn't > > get handled correctly with the standard fsck. I end up having to bring my > > machine > > into single-user mode to perform the fsck manually. > > > > Anyone else? > > > > I'm getting the crashes but fsck is able to repair my system just fine. I > haven't been able to get a dump. The crashes occur during heavy local > file I/O (such as a buildworld or cvsup of ports-all). This is on a > system current as of 8:OOAM PST this morning. 400MHz PII SMP 512MB RAM, / > and /usr on SEAGATE ST34502LW with adaptec 7890, /usr/scratch is RAID 0 on > two IBM 9ZX's with DPT PM3334UW FW Rev. 07M0, 2 channels. I'm running a > current kernel from Oct 29 at the moment as a work-around -- Trying to > buildworld cvsupped moments ago to see if the problem has in fact been > fixed as has been mentioned. If not, I'll get more hard-nosed about > capturing a useful dump... Wonderfull, I think to be the only one to suffers from suddendly reboot ... Now I am not alone anymore... :) Sorry for the joke, but here the crashes happens usually when I am testing some cgi perl script with Netscape and Apache web server. The script involved an heavy disk activity... At the first I thought was the Pentium II overclocked 333 --> 500, but the problem continue even if I put the bus back to 83,75,66 ... Also I have an adaptec 7890 scsi controller (onboard) with two 9gb wide quantum... Is perhaps an hd controller related problem ? Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 07:41:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA26324 for freebsd-current-outgoing; Tue, 17 Nov 1998 07:41:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA26297; Tue, 17 Nov 1998 07:40:44 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA25708; Tue, 17 Nov 1998 10:40:02 -0500 (EST) (envelope-from wollman) Date: Tue, 17 Nov 1998 10:40:02 -0500 (EST) From: Garrett Wollman Message-Id: <199811171540.KAA25708@khavrinen.lcs.mit.edu> To: "Eugene M. Kim" Cc: Garrett Wollman , FreeBSD-current Mailing List Subject: Re: cvs commit: src/sys/sys bus.h bus_private.h conf.h devicestat.h module.h src/sys/kern bus_if.m device_if.m kern_conf.c subr_bus.c subr_devstat.c In-Reply-To: References: <199811142158.NAA22480@freefall.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Is there a workaround, or must smbus.c and iicbus.c be rewritten per the > new interface? Yes. -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, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 07:54:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27499 for freebsd-current-outgoing; Tue, 17 Nov 1998 07:54:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27466 for ; Tue, 17 Nov 1998 07:54:15 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA11120; Tue, 17 Nov 1998 10:53:42 -0500 (EST) Date: Tue, 17 Nov 1998 10:53:42 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kyle Mestery cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: Nasty rebooting in 3.0 current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Kyle Mestery wrote: > > As of this weekend's CVS update (current to the timestamp of this message) > > there appears to be a problem with rebooting on FreeBSD-3.0-CURRENT. > > > I noticed this over the weekend also. I am running a current kernel from > Saturday night around 5PM CST, on a dual PPro machine. On both Sunday > morning and this morning I awoke to find the machine in a hung state, no > video output, nohting. Required a hard reset. I havent had time to > investivate, but will tonite. Very strange. Mine appears to be caused by > a lot of network traffic also, asa CVSup this morning caused the same thing to > happen. > After exiting XFree86, my machine had a frozen console. I tried switching, got that infamous "never-ending high beep from the old pc speaker", tried pressing Ctrl+Alt+Del, Ctrl+Esc, to no avail. I was about to give up but I said "what the hell" and typed "cont\n". Lo, my system was rebooting from the ctrl-alt-del, and it seemed for some reaason that it got stuck inside ddb. > -- > Kyle Mestery > StorageTek's Storage Networking Group Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 08:19:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00566 for freebsd-current-outgoing; Tue, 17 Nov 1998 08:19:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00555 for ; Tue, 17 Nov 1998 08:19:26 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id RAA10676; Tue, 17 Nov 1998 17:22:48 +0100 (CET) Message-Id: <199811171622.RAA10676@rt2.synx.com> Date: Tue, 17 Nov 1998 17:17:46 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: Is it soup yet? FreeBSD NFS To: cejkar@dcse.fee.vutbr.cz cc: freebsd-current@FreeBSD.ORG In-Reply-To: <199811131604.RAA08265@kazi.dcse.fee.vutbr.cz> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 13 Nov, Cejka Rudolf wrote: > >> > Everyone seems to be talking about using FreeBSD as an NFS client, >> > how does FreeBSD do as a NFS server? >> > >> > -J >> > >> >> I'm going to be using NFS extensively at home for a while, I'll let you >> know. >> >> Last time I used it, it wasn't the most stable thing. A NFS mounted >> buildworld crashed the server once, but then worked fine after that. >> >> - -Alfred > > We have long-time problems (not critical) with NFS server running > on FreeBSD 2.2.6/2.2.7/3.0 against Solaris 2.5/2.6 clients there. > > Our problem: > > FreeBSD: NFS server without any special parameters. > Solaris: NFS client without any special parameters. > > Example - working on Solaris above mounted filesystem from FreeBSD: > > $ gzcat less-332.tar.gz | tar xvf - # This creates 74 files in > # directory less-332 > $ rm -r less-332 # This _leaves_ 43 files! > rm: Unable to remove directory less-332: File exists > $ rm -r less-332 # This _still leaves_ 15 files! > rm: Unable to remove directory less-332: File exists > $ rm -r less-332 # Uff, directory is removed now... > > I think, problem is in different versions (NFSv2 vs. NFSv3) - but it > looks very trivial (?). If I mount NFS exported filesystem (exports > FreeBSD) on Solaris with option "vers=2" (it says "use NFSv2"), > problems disappear. But we are using cachefs (cached filesystem) over > NFS with automounting feature and we have no change to say "cachefs, > mount NFS filesystem with 'vers=2' option". There isn't any parameter > for this on Solaris... > > I have tried to use "mountd -2" on FreeBSD server part, but it > caused Solaris hangs... > > --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- > Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) > Technical University of Brno, Faculty of El. Engineering and Comp. Science > Bozetechova 2, 612 66 Brno, Czech Republic > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message I have an open problem on this (pr5890). Look at it and try the suggested fix. The machine where it is applied runs NFS serving for now 7 month and no problems appeared (clients: Solaris, aix, sco, hpux). No need to say that this needs a competent blessing....(re-read the BSD license before trying it :). RN. IhM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 08:41:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03208 for freebsd-current-outgoing; Tue, 17 Nov 1998 08:41:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03203 for ; Tue, 17 Nov 1998 08:41:34 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id LAA20517; Tue, 17 Nov 1998 11:41:08 -0500 (EST) Date: Tue, 17 Nov 1998 11:41:08 -0500 (EST) Message-Id: <199811171641.LAA20517@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: aio_read() / aio_write() don't work Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I reported PR kern/8669 about aio_read() and aio_write() not working. Anybody have any ideas about it. It seems to me that the aio_* routines: - don't work at all - don't have a man page - have a broken header (doesn't do an "extern "C" {") Where is the code for this stuff? I can't find it, so, I can't even consider fixing it. -Rob ps. We really need a thread-safe way of offset-read's and offset-write's. pread() and pwrite() would be ideal. Regardless, this aio_* stuff should be fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 08:44:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03748 for freebsd-current-outgoing; Tue, 17 Nov 1998 08:44:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA03737 for ; Tue, 17 Nov 1998 08:44:34 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id IAA09403; Tue, 17 Nov 1998 08:44:06 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 17 Nov 1998 08:44:06 -0800 (PST) From: Doug White To: "William R. Somsky" cc: current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <19981115173516.A4986@halcyon.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 15 Nov 1998, William R. Somsky wrote: > Ok, now that we've got the new 3-stage bootloader, and it looks like > it's near to becoming the standard, I've got two questions: > > 1) Where is there documentation on it? Um, the source? :-) I'm looking for this as well. The curent mail archives may have some info too. > 2) Will we have a DOS/WIN program to install a copy of the new boot0 > when it gets trashed by a Windows install or other "disaster" ;-) Robert Nordier is hoarding a boot0inst program somewhere, maybe www.freebsd.org/~nordier/. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 09:47:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13548 for freebsd-current-outgoing; Tue, 17 Nov 1998 09:47:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alive.znep.com (207-178-54-226.go2net.com [207.178.54.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13538 for ; Tue, 17 Nov 1998 09:47:51 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id JAA11675; Tue, 17 Nov 1998 09:43:21 -0800 (PST) (envelope-from marcs@znep.com) Date: Tue, 17 Nov 1998 09:43:20 -0800 (PST) From: Marc Slemko To: HighWind Software Information cc: current@FreeBSD.ORG Subject: Re: aio_read() / aio_write() don't work In-Reply-To: <199811171641.LAA20517@highwind.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, HighWind Software Information wrote: > > I reported PR kern/8669 about aio_read() and aio_write() not working. > Anybody have any ideas about it. > > It seems to me that the aio_* routines: > > - don't work at all As I already told you, it is NOT correct to say that they don't work at all and, in fact, just hides the real thing that needs fixing. That isn't good; if you said that "oh, offsets don't work" then someone would be a lot more likely to look at it than if you say "oh, they just don't work period". And, at this point, the only thing that I would see wrong that didn't work in your test program is the offsets. > - don't have a man page > - have a broken header (doesn't do an "extern "C" {") > > Where is the code for this stuff? I can't find it, so, I can't even > consider fixing it. /sys/kern/vfs_aio.c has the aio_* stuff, but I think the problem is actually down lower in things like vn_write in vfs_vops.c. It doesn't look too hard to fix, but I haven't had a chance to try it yet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 09:49:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13809 for freebsd-current-outgoing; Tue, 17 Nov 1998 09:49:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA13798 for ; Tue, 17 Nov 1998 09:49:41 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id LAA28243; Tue, 17 Nov 1998 11:39:24 -0600 (CST) From: Kevin Day Message-Id: <199811171739.LAA28243@home.dragondata.com> Subject: Re: MediaGX and calcru: negative time In-Reply-To: <199811171122.UAA01911@lavender.sanpei.org> from MIHIRA Yoshiro at "Nov 17, 98 08:22:10 pm" To: sanpei@sanpei.org (MIHIRA Yoshiro) Date: Tue, 17 Nov 1998 11:39:23 -0600 (CST) Cc: current@FreeBSD.ORG, sanpei@sanpei.org, cjohnson@netgsi.com X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can confirm that this patch works: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #3: Tue Nov 24 17:38:30 CST 1998 devel@kevin1.touchmaster:/usr/src/sys/compile/DEVEL Calibrating clock(s) ... TSC clock: 233902340 Hz, i8254 clock: 1217245 Hz 1217245 Hz differs from default of 1193182 Hz by more than 1% Timecounter "i8254" frequency 1193182 Hz cost 1302 ns Timecounter "TSC" frequency 233864996 Hz cost 180 ns CPU: Cyrix GXm (233.86-MHz 586-class CPU) Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 Features=0x808131 I'm going to file a errata report with Cyrix.... Kevin > > I have MediaGX box. I install 2.2.6R. I also have this problem..... > But my problem is only calcru, and can't detect psm0(PS/2) port. > Sometimes can't detect Ethernet Card(occasionally automatically rebooted...). > > This problem (I think) already reported to GNATS Problem repository, > kern/6630[1] which is included experimental patch. Please apply this patch. > This Patch is ``check timer twice, and use larger one at getit:clock.c''. > > Another person who has also MediaGX box, reported me that > his MediaGX box is needed 4 times to detect correct one. > > I had planning to report this problem to GNATS Database and Mr Christopher > T. Johnson. > > [1] kern/6630: Fix for Cyrix I8254 bug > http://www.freebsd.org/cgi/query-pr.cgi?pr=6630 > > Thank you > MIHIRA Yoshiro > > ----- > 4times patch > --- /sys/i386/isa/clock.c Sun Apr 27 22:44:19 1997 > +++ ./clock.c Mon Nov 2 17:01:55 1998 > @@ -345,7 +345,9 @@ > { > u_long ef; > int high, low; > - > +#ifdef CPU_CYRIX_NO_I8254_LATCH > + int ret1, ret2, ret3, ret4; > +#endif > ef = read_eflags(); > disable_intr(); > > @@ -354,9 +356,32 @@ > > low = inb(TIMER_CNTR0); > high = inb(TIMER_CNTR0); > +#ifdef CPU_CYRIX_NO_I8254_LATCH > + ret1 = (high << 8) | low; > > + outb(TIMER_MODE, TIMER_SEL0 | TIMER_LATCH); > + low = inb(TIMER_CNTR0); > + high= inb(TIMER_CNTR0); > + ret2 = (high << 8) | low; > + > + outb(TIMER_MODE, TIMER_SEL0 | TIMER_LATCH); > + low = inb(TIMER_CNTR0); > + high= inb(TIMER_CNTR0); > + ret3 = (high << 8) | low; > + > + outb(TIMER_MODE, TIMER_SEL0 | TIMER_LATCH); > + low = inb(TIMER_CNTR0); > + high= inb(TIMER_CNTR0); > + ret4 = (high << 8) | low; > +#endif > write_eflags(ef); > +#ifdef CPU_CYRIX_NO_I8254_LATCH > + ret1 = (ret1 > ret2 ? ret1 : ret2); > + ret3 = (ret3 > ret4 ? ret3 : ret4); > + return (ret1 > ret3 ? ret1 : ret3); > +#else > return ((high << 8) | low); > +#endif > } > > /* > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:02:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15554 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:02:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15549 for ; Tue, 17 Nov 1998 10:02:53 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id NAA25473; Tue, 17 Nov 1998 13:01:54 -0500 (EST) Date: Tue, 17 Nov 1998 13:01:54 -0500 (EST) Message-Id: <199811171801.NAA25473@highwind.com> From: HighWind Software Information To: marcs@znep.com CC: current@FreeBSD.ORG In-reply-to: (message from Marc Slemko on Tue, 17 Nov 1998 09:43:20 -0800 (PST)) Subject: Re: aio_read() / aio_write() don't work Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I already told you, it is NOT correct to say that they don't work at > all and, in fact, just hides the real thing that needs fixing. Sorry about that. You are right. The offset doesn't work. Unfortunately, that is the main reason I wanted to use these routines. I wonder how well they will work in conjunction with libc_r. I guess we'll find out. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:05:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15767 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:05:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from premierproductions.com (pm4-205.hp.infi.net [208.142.82.205]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA15729; Tue, 17 Nov 1998 10:05:28 -0800 (PST) (envelope-from webmaster@premierproductions.com) Date: Tue, 17 Nov 1998 10:05:28 -0800 (PST) From: webmaster@premierproductions.com Message-Id: <199811171805.KAA15729@hub.freebsd.org> To: webmaster@premierproductions.com Subject: Community Christmas Announcement Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG GREAT HOLIDAY MUSIC The Holidays are quickly approaching and what better way to begin the season than with a great Christmas show. Premier Productions is proud to announce that we will be bringing The Ray Boltz Christmas Show to the Charleston Municipal Auditorium on Saturday, November 28 at 7:00pm. Join us for a great evening of Christmas music that will put you in the Christmas spirit for the rest of the season. All seating is reserved but great seats still remain at the Civic Center Box Office, and Tickets Master Outlets. www.ticketmaster.com You can charge tickets by phone by calling: 304-342-5757 For more information visit our web site at www.PremierProductions.com Hope to see you there! Thanks Premier Productions This is a one time community announcement. This is a one time community announcement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:11:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16846 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:11:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16838 for ; Tue, 17 Nov 1998 10:11:29 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id KAA25089 for ; Tue, 17 Nov 1998 10:10:33 -0800 (PST) Date: Tue, 17 Nov 1998 10:11:48 -0800 (PST) From: Tom Bartol To: freebsd-current@FreeBSD.ORG Subject: NFS problems in -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've been seeing the following problem for a while now (since 3.0-19981006-BETA) but was too busy at the time to report it or help diagnose it further. Now I've got some time on my hands... I can fairly consistently wedge NFS writes to our server with the following: dd if=/dev/zero of=ick bs=8192 count=1000 which tries to write an 8MB file to our file server which is an Auspex. I have mounted Auspex from my 3.0-current machine (cvsupped and built this morning) in NFSv3 mode. This command will wedge one or more of the nfsiod processes. "ps -auwx | grep nfsiod" reports the following: root 137 0.0 0.0 216 64 ?? I 9:12AM 0:02.31 nfsiod -n 4 root 138 0.0 0.0 216 64 ?? I 9:12AM 0:01.74 nfsiod -n 4 root 139 0.0 0.0 216 64 ?? D 9:12AM 0:00.27 nfsiod -n 4 root 140 0.0 0.0 216 64 ?? D 9:12AM 0:00.24 nfsiod -n 4 The two processes in state "D" are the wedged ones. A separate machine running -current from July 11 works fine. Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS reads work fine. Is anyone else seeing similar behaviour? What can I do to try to fine tune a diagnosis and help solve the problem? Thanks for your help, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:14:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17573 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:14:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-8-dbn.dial-up.net [196.34.155.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17534 for ; Tue, 17 Nov 1998 10:13:56 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id UAA11618; Tue, 17 Nov 1998 20:11:35 +0200 (SAT) From: Robert Nordier Message-Id: <199811171811.UAA11618@ceia.nordier.com> Subject: Re: your mail In-Reply-To: from Doug White at "Nov 17, 98 08:44:06 am" To: dwhite@resnet.uoregon.edu (Doug White) Date: Tue, 17 Nov 1998 20:11:31 +0200 (SAT) Cc: wrsomsky@halcyon.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > On Sun, 15 Nov 1998, William R. Somsky wrote: > > > 2) Will we have a DOS/WIN program to install a copy of the new boot0 > > when it gets trashed by a Windows install or other "disaster" ;-) > > Robert Nordier is hoarding a boot0inst program somewhere, maybe > www.freebsd.org/~nordier/. It's http://www.freebsd.org/~rnordier/boot0inst-1.0.tar.gz except that this runs on FreeBSD rather than DOS. However, see my earlier reply to William's message, also somewhere on the -current list. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:15:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17842 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:15:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megadeth.rtci.com (megadeth.noc.rtci.com [216.27.37.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17831 for ; Tue, 17 Nov 1998 10:15:22 -0800 (PST) (envelope-from dhopkins@rtci.com) Received: from rtci.com (oxygen.schizo.com [216.27.37.251]) by megadeth.rtci.com (8.8.8/8.8.8) with ESMTP id NAA17535; Tue, 17 Nov 1998 13:19:22 -0500 (EST) (envelope-from dhopkins@rtci.com) Message-ID: <3651BF9B.A7D93857@rtci.com> Date: Tue, 17 Nov 1998 13:25:31 -0500 From: Damon Hopkins Organization: Research Triangle Consultants, Inc. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Current Mailing list Subject: Re: Random rebooting References: <36505A1E.8876B72@rtci.com> <19981117092446.M717@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I did not see a panic in any of the logs -- [-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=-] [ Damon Hopkins mailto: dhopkins@rtci.com ] [ Software Developer http://totally.schizo.com ] [ Research Triangle Consultants, Inc. http://www.rtci.com ] [ -- In search of the elusive 50 sided triangle. -- ] [-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=-] Greg Lehey wrote: > Not really. Your machine probably rebooted because of something like > a panic, but you don't mention that. If you're running -CURRENT, you > should at least have dumps enabled, and preferably a debug kernel so > you can do something with the dumps. The only thing I can see from > the messages you added was that you didn't have dumps enabled. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:16:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17958 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:16:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA17933 for ; Tue, 17 Nov 1998 10:16:14 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.169]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA18D2; Tue, 17 Nov 1998 19:15:47 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 17 Nov 1998 19:20:22 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Chuck Robey Subject: Re: ZIP+ and NatSemi parallel port chipst (was Re: ZIP, again) Cc: FreeBSD Current , Nicolas Souchu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Nov-98 Chuck Robey wrote: > On Tue, 17 Nov 1998, Jeroen Ruigrok/Asmodai wrote: >> Well it gets probed as da2... Except all my devices in fstab are still sd >> instead of their da counterparts. I wanted to convert them, but found the >> man-pages to be sketchy at best, and since I don't want to disable my system >> again ;) > > The sd* and da* devices have the same major/minor numbers. Cam is > color-blind at that range, you haven't anything to worry about. It's > probably a good idea to update your devices and fstab, against some > future change, but right now, it doesn't matter. Well, let's put it like this: I have tried every ./MAKEDEV I knew to get the equivalents of my current used sd* entries. Or am I supposed to disklabel them to da counterparts first and then MAKEDEV and update /etc/fstab? I really couldn't find any good pointers on this. With most of the da manpages still in the fingers ;) (the 9 section). --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:26:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20149 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:26:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20144 for ; Tue, 17 Nov 1998 10:26:41 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id NAA05067; Tue, 17 Nov 1998 13:29:22 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 17 Nov 1998 13:29:22 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Damon Hopkins cc: Current Mailing list Subject: Re: Random rebooting In-Reply-To: <3651BF9B.A7D93857@rtci.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Damon Hopkins wrote: > Greg Lehey wrote: > > Not really. Your machine probably rebooted because of something like > > a panic, but you don't mention that. If you're running -CURRENT, you > > should at least have dumps enabled, and preferably a debug kernel so > > you can do something with the dumps. The only thing I can see from > > the messages you added was that you didn't have dumps enabled. > > I did not see a panic in any of the logs how do you expect the kernel to log a panic unless it's via a logged serial consol? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:27:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20288 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:27:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20275 for ; Tue, 17 Nov 1998 10:27:16 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.169]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA37D; Tue, 17 Nov 1998 19:26:31 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 17 Nov 1998 19:31:06 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Tom Bartol Subject: RE: NFS problems in -current Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Nov-98 Tom Bartol wrote: > > Hi all, > > I've been seeing the following problem for a while now (since > 3.0-19981006-BETA) but was too busy at the time to report it or help > diagnose it further. Now I've got some time on my hands... > > I can fairly consistently wedge NFS writes to our server with the > following: Ye also applied Mike Smith's NFS patches? Just curious... --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 10:37:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA21542 for freebsd-current-outgoing; Tue, 17 Nov 1998 10:37:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21502; Tue, 17 Nov 1998 10:36:57 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id KAA19506; Tue, 17 Nov 1998 10:35:10 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019499; Tue, 17 Nov 98 10:34:50 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id KAA14701; Tue, 17 Nov 1998 10:34:49 -0800 (PST) From: Archie Cobbs Message-Id: <199811171834.KAA14701@bubba.whistle.com> Subject: Re: hosts before bind in /etc/host.conf? In-Reply-To: from Licia at "Nov 15, 98 11:33:58 am" To: licia@o-o.org (Licia) Date: Tue, 17 Nov 1998 10:34:49 -0800 (PST) Cc: jkh@zippy.cdrom.com, current@FreeBSD.ORG, peter@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Licia writes: > On a fairly unrelated note, I would also suggest if possible, > to add a default of -s to the syslogd flags in /etc/rc.conf for people > who are not aware of the possibility of syslog bombing. I agree with adding '-s' to syslogd.. seems the more conservative approach. This is the common case anyway. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 11:16:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25935 for freebsd-current-outgoing; Tue, 17 Nov 1998 11:10:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25929 for ; Tue, 17 Nov 1998 11:10:15 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA13971; Tue, 17 Nov 1998 13:09:48 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id NAA04727; Tue, 17 Nov 1998 13:09:17 -0600 Message-ID: <19981117130916.47217@right.PCS> Date: Tue, 17 Nov 1998 13:09:16 -0600 From: Jonathan Lemon To: HighWind Software Information Cc: current@FreeBSD.ORG Subject: Re: aio_read() / aio_write() don't work References: <199811171641.LAA20517@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199811171641.LAA20517@highwind.com>; from HighWind Software Information on Nov 11, 1998 at 11:41:08AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Nov 11, 1998 at 11:41:08AM -0500, HighWind Software Information wrote: > > I reported PR kern/8669 about aio_read() and aio_write() not working. > Anybody have any ideas about it. So, did you have time to try out the possible patch to aio_write that I sent you? I don't have a scratch box right now, otherwise I'd try testing it out myself. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 11:18:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27200 for freebsd-current-outgoing; Tue, 17 Nov 1998 11:18:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27189 for ; Tue, 17 Nov 1998 11:18:04 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id LAA26946; Tue, 17 Nov 1998 11:12:38 -0800 (PST) Date: Tue, 17 Nov 1998 11:13:53 -0800 (PST) From: Tom Bartol To: Jeroen Ruigrok/Asmodai cc: freebsd-current@FreeBSD.ORG Subject: RE: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > On 17-Nov-98 Tom Bartol wrote: > > > > Hi all, > > > > I've been seeing the following problem for a while now (since > > 3.0-19981006-BETA) but was too busy at the time to report it or help > > diagnose it further. Now I've got some time on my hands... > > > > I can fairly consistently wedge NFS writes to our server with the > > following: > > Ye also applied Mike Smith's NFS patches? Just curious... > > --- No, I'm running stock -current. I must have missed the mail that mentioned the patches you speak of. I'd like to try them. Where can I find them? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 11:18:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27218 for freebsd-current-outgoing; Tue, 17 Nov 1998 11:18:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27193 for ; Tue, 17 Nov 1998 11:18:05 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA07170 for ; Tue, 17 Nov 1998 14:17:39 -0500 (EST) Date: Tue, 17 Nov 1998 14:17:39 -0500 (EST) From: "Matthew N. Dodd" To: current@FreeBSD.ORG Subject: /dev/ioport[bwl] Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whats the story on the #ifdef notyet ... #endif Bits around the code implementing /dev/ioport[bwl] in src/sys/i386/i386/mem.c? I'd like to use /dev/io and friends (/dev/ioport[bwl] if they exist) to do some PIO routine prototyping for a device driver. That the code in question is commented out leads me to believe that this will not be possible. Thanks. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 12:05:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04754 for freebsd-current-outgoing; Tue, 17 Nov 1998 12:05:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from paris.dppl.com (paris.dppl.com [205.230.74.150]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA04748 for ; Tue, 17 Nov 1998 12:05:24 -0800 (PST) (envelope-from yds@ingress.net) Received: (qmail 29147 invoked from network); 17 Nov 1998 20:04:57 -0000 Received: from ichiban.ingress.com (HELO ichiban) (205.230.64.31) by paris.dppl.com with SMTP; 17 Nov 1998 20:04:57 -0000 Message-ID: <018001be1265$8cf95560$1f40e6cd@ichiban.ingress.com> From: "Yarema" To: "Tom Bartol" , Subject: Re: NFS problems in -current Date: Tue, 17 Nov 1998 15:04:57 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The two processes in state "D" are the wedged ones. A separate machine >running -current from July 11 works fine. > >Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS >reads work fine. > >Is anyone else seeing similar behaviour? What can I do to try to fine >tune a diagnosis and help solve the problem? I remember having this problem very consistently when 2.2.7 came out. Doesn't happen to me anymore. Most likely cuz the network here got rearranged rather than there being any fix in FreeBSD's NFS code. I'm also curious how to diagnose and report something useful should this happen again. -- Yarema To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 12:58:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12127 for freebsd-current-outgoing; Tue, 17 Nov 1998 12:58:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (50.camalott.com [208.203.140.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12113 for ; Tue, 17 Nov 1998 12:58:04 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id OAA04580; Tue, 17 Nov 1998 14:57:31 -0600 (CST) (envelope-from joelh) To: Open Systems Networking Cc: Bryan Fullerton , freebsd-current@FreeBSD.ORG Subject: Re: proc changes References: From: Joel Ray Holveck Date: 17 Nov 1998 14:57:30 -0600 In-Reply-To: Open Systems Networking's message of "Tue, 17 Nov 1998 07:50:10 -0500 (EST)" Message-ID: <86ogq6yr45.fsf@detlev.UUCP> Lines: 19 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Okay, what do you think of having lists with *only* heads-up info for >> -current and -stable, with easily accessible archives? > Personally I dont think anyone will read them. They dont seem to read the > *HEADS-UP* messages on current and another list that isnt read is just a > waste of time IMO.Well just have to keep chuggin with what we have and > answer the occasional storm of repeated *me too* problems. I am much more likely to read more of a low-bandwidth list with only messages I know are relevant than a high-bandwidth list with lots of discussion which may or may not apply to what I'm doing. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 13:16:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16353 for freebsd-current-outgoing; Tue, 17 Nov 1998 13:16:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (50.camalott.com [208.203.140.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16344 for ; Tue, 17 Nov 1998 13:16:20 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id PAA04672; Tue, 17 Nov 1998 15:15:17 -0600 (CST) (envelope-from joelh) To: Jeroen Ruigrok/Asmodai Cc: Chuck Robey , FreeBSD Current , Nicolas Souchu Subject: Re: ZIP+ and NatSemi parallel port chipst (was Re: ZIP, again) References: From: Joel Ray Holveck Date: 17 Nov 1998 15:15:15 -0600 In-Reply-To: Jeroen Ruigrok/Asmodai's message of "Tue, 17 Nov 1998 19:20:22 +0100 (CET)" Message-ID: <86n25qyqak.fsf@detlev.UUCP> Lines: 23 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The sd* and da* devices have the same major/minor numbers. Cam is >> color-blind at that range, you haven't anything to worry about. It's >> probably a good idea to update your devices and fstab, against some >> future change, but right now, it doesn't matter. > I have tried every ./MAKEDEV I knew to get the equivalents of my > current used sd* entries. Or am I supposed to disklabel them to da > counterparts first and then MAKEDEV and update /etc/fstab? disklabel doesn't enter ento it. sd vs. da is a driver issue and a naming issue. Have you updated your /dev/MAKEDEV from /usr/src/etc/etc.i386/MAKEDEV lately? (Running MAKEDEV from the src tree doesn't cut it; see pr i386/8598). MAKEDEV da# (where # is the number of SCSI disks you want to make nodes for, not the highest-numbered device) will make the nodes. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 13:22:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16977 for freebsd-current-outgoing; Tue, 17 Nov 1998 13:22:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16924 for ; Tue, 17 Nov 1998 13:22:00 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id QAA27441; Tue, 17 Nov 1998 16:21:01 -0500 (EST) Date: Tue, 17 Nov 1998 16:21:01 -0500 (EST) Message-Id: <199811172121.QAA27441@highwind.com> From: HighWind Software Information To: jlemon@americantv.com CC: current@FreeBSD.ORG In-reply-to: <19981117130916.47217@right.PCS> (message from Jonathan Lemon on Tue, 17 Nov 1998 13:09:16 -0600) Subject: Re: aio_read() / aio_write() don't work Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So, did you have time to try out the possible patch to aio_write that I sent you? I don't have a scratch box right now, otherwise I'd try testing it out myself. I never got that patch. I'll try it if you send it. -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 13:32:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18721 for freebsd-current-outgoing; Tue, 17 Nov 1998 13:32:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18669 for ; Tue, 17 Nov 1998 13:32:26 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.21]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA26C2; Tue, 17 Nov 1998 21:31:38 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 17 Nov 1998 22:36:13 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Tom Bartol Subject: RE: NFS problems in -current Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Nov-98 Tom Bartol wrote: > > On Tue, 17 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > > No, I'm running stock -current. I must have missed the mail that > mentioned the patches you speak of. I'd like to try them. Where can I > find them? Do a search on the CURRENT list for NFS and date about a week ago --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 13:36:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19391 for freebsd-current-outgoing; Tue, 17 Nov 1998 13:36:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from heaven.gigo.com (ppp.gigo.com [207.173.132.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19385 for ; Tue, 17 Nov 1998 13:36:39 -0800 (PST) (envelope-from jfesler@gigo.com) Received: by heaven.gigo.com (8.8.8/8.8.8) with SMTP id NAA07157 for ; Tue, 17 Nov 1998 13:36:03 -0800 (PST) X-SMTP: helo heaven.gigo.com from jfesler@gigo.com server jfesler@heaven.gigo.com ip 207.173.133.57 Date: Tue, 17 Nov 1998 13:36:01 -0800 (PST) From: Jason Fesler To: current@FreeBSD.ORG Subject: Heads up file Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, this may seem a bit strange for you, but here's a stab at a possible solution for people who can't keep up with the sheer bulk of -current. Maintain a README type file, perhaps called HEADSUP, with warnings and announcements in reverse cronological order, and dated. I did this for a couple of the software projects I've done in the past, and it was extremely helpful. People only had to read down to the point where they last upgrade, and nothing had to be left out for fear of being overly redudant. Every one in a while the file would be trimmed (roughly yearly) to keep the file size sane, but it overall worked out well. Am I on drugs for suggesting it here? Or just on drugs? :-). Jason Fesler |".. and ten thousand noblemen squated and Price, Speed, Quality - | strained, for the King's word, was law." Pick any two. | - SCA Folklore To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 13:42:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20204 for freebsd-current-outgoing; Tue, 17 Nov 1998 13:42:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vss.sci-nnov.ru (vss.sci-nnov.ru [193.125.71.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20182 for ; Tue, 17 Nov 1998 13:42:25 -0800 (PST) (envelope-from dmiter@sci-nnov.ru) Received: from winhome (home.sci-nnov.ru [194.190.176.102]) by vss.sci-nnov.ru (8.8.8/Dmiter-4.2vss) with SMTP id AAA24852; Wed, 18 Nov 1998 00:41:43 +0300 (MSK) Message-ID: <00b401be1272$e4336de0$0200000a@winhome.sci-nnov.ru> Reply-To: "Dmitry Eremin" From: "Dmitry Eremin" To: Cc: "Bill Fenner" Subject: ARP problem with two same Ethernet cards. Date: Wed, 18 Nov 1998 00:40:21 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have problem after install two same Ethernet cards in the computer. I have following configuration: FreeBSD 3.0-CURRENT #2: Tue Nov 17 16:15:40 MSK 1998 2 3C5x9 board(s) on ISA found at 0x320 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: utp[*UTP*] address 00:c0:4f:da:36:f5 ep1 at 0x320-0x32f irq 5 on isa ep1: aui/utp[*UTP*] address 00:20:af:aa:fc:19 root@FreeBSD# ifconfig -a ep0: flags=8843 mtu 1500 inet 192.168.1.230 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:c0:4f:da:36:f5 ep1: flags=8843 mtu 1500 inet 192.168.201.230 netmask 0xffffff00 broadcast 192.168.201.255 ether 00:20:af:aa:fc:19 I have the following error messages on console and log files: arp: 192.168.1.202 is on ep0 but got reply from 00:00:c0:8a:9e:d0 on ep1 arp: 192.168.1.202 is on ep0 but got reply from 00:00:c0:8a:9e:d0 on ep1 arp: 192.168.1.192 is on ep0 but got reply from 00:c0:4f:a9:9b:a4 on ep1 root@FreeBSD# arp -a xxx.xxx.xx (192.168.1.192) at 0:c0:4f:a9:9b:a4 ? (192.168.1.202) at 0:0:c0:8a:9e:d0 ? (192.168.1.204) at 0:0:c0:99:d1:c5 I point to fact that I don't have broken switch between two nets. These nets are physically independent. I don't have any hardware between these nets exclude my computer. This problem reiterates on computer with two same Ethernet cards. I'm already having this problem with two SMC (de0 and de1) cards. My experiment with two 3COM (ep0 and ep1) cards give the same result. This problem didn't have in 3.0-SNAP-981004. Best regards. \|/ _________________________________________________________oOO_(o_o)_OOo___ Dmitry Eremin : dmiter@sci-nnov.ru : Fido: 2:5015/23 : N.Novgorod, Russia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 13:47:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20553 for freebsd-current-outgoing; Tue, 17 Nov 1998 13:47:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20548 for ; Tue, 17 Nov 1998 13:47:07 -0800 (PST) (envelope-from bhilton@vpop.net) Received: from vpop.net ([209.181.248.193]) by boromir.vpop.net (8.9.1/8.8.5) with ESMTP id NAA23781 for ; Tue, 17 Nov 1998 13:46:39 -0800 (PST) Message-ID: <3651EEBE.BECF445D@vpop.net> Date: Tue, 17 Nov 1998 15:46:38 -0600 From: Brad Hilton X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: skip on elf kernel? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I was curious if anyone has had any success loading the skip module onto an ELF kernel. It seems that the port builds the module as an lkm, not a kld, so the elf kernel won't load it. Also, if running a -current ELF system with an aout kernel, I have found it necessary to build the skip port with OBJFORMAT set to 'aout', or modload chokes on the ELF file format. Is there a solution to this problem I'm not seeing, or are we just in the "transition" phase still? More importantly, is it possible to run skip with an ELF kernel? If anyone has any suggestions/thoughts on this I would appreciate the feedback. Regards, Brad Hilton VPOP Technologies bhilton@vpop.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 14:08:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24542 for freebsd-current-outgoing; Tue, 17 Nov 1998 14:08:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24314 for ; Tue, 17 Nov 1998 14:07:11 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.21]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA6B42; Tue, 17 Nov 1998 23:06:29 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 17 Nov 1998 23:11:05 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Jason Fesler Subject: RE: Heads up file Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Nov-98 Jason Fesler wrote: > Okay, this may seem a bit strange for you, but here's a stab at a possible > solution for people who can't keep up with the sheer bulk of -current. > Maintain a README type file, perhaps called HEADSUP, with warnings and > announcements in reverse cronological order, and dated. Sounds fine to me... > I did this for a couple of the software projects I've done in the past, > and it was extremely helpful. People only had to read down to the point > where they last upgrade, and nothing had to be left out for fear of being > overly redudant. Every one in a while the file would be trimmed (roughly > yearly) to keep the file size sane, but it overall worked out well. As far as I am concerned I think it's a good idea, especially with all the hooks and crannies one tends to forget. For example my last few posts about sd/da stuff... Then again, I am lame =p But seriously, there are lots of caveats one can quickly overlook, and as I try to maintain all lists necessary for myself. Just my opinion... > Am I on drugs for suggesting it here? Or just on drugs? :-). I won't speculate ;) Mayhaps a doc-project? --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 14:21:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27704 for freebsd-current-outgoing; Tue, 17 Nov 1998 14:21:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27693 for ; Tue, 17 Nov 1998 14:21:32 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id PAA27996; Tue, 17 Nov 1998 15:21:03 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd027939; Tue Nov 17 15:20:54 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id PAA14095; Tue, 17 Nov 1998 15:20:50 -0700 (MST) From: Terry Lambert Message-Id: <199811172220.PAA14095@usr09.primenet.com> Subject: Re: Random rebooting To: grog@lemis.com (Greg Lehey) Date: Tue, 17 Nov 1998 22:20:50 +0000 (GMT) Cc: dhopkins@rtci.com, current@FreeBSD.ORG In-Reply-To: <19981117092446.M717@freebie.lemis.com> from "Greg Lehey" at Nov 17, 98 09:24:46 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not really. Your machine probably rebooted because of something like > a panic, but you don't mention that. If you're running -CURRENT, you > should at least have dumps enabled, and preferably a debug kernel so > you can do something with the dumps. The only thing I can see from > the messages you added was that you didn't have dumps enabled. > > Also, you appear not to be following this list, or you would have seen > a number of messages on panics in the last few days. We appear to > have fixed one, but there's no way of knowing whether it had anything > to do with your problem. Actually, I have been able to demonstrate silent reboots since late 2.2.6, and subsequently. I didn't speak up because I assumed it was a local driver problem with a custom driver. The reboots are infrequent, but appear to occur most commonly with high network load, and more commonly with RIP being the source of the load. The reboot is completely silent; no console logs, no panic message, nothing -- except "/ was not unmounted cleanly" in the dmesg after the event. FWIW. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 14:53:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03089 for freebsd-current-outgoing; Tue, 17 Nov 1998 14:53:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.training.iafrica.com (axl.training.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03081 for ; Tue, 17 Nov 1998 14:53:12 -0800 (PST) (envelope-from sheldonh@axl.training.iafrica.com) Received: from sheldonh (helo=axl.training.iafrica.com) by axl.training.iafrica.com with local-esmtp (Exim 2.053 #1) id 0zftyW-0000Cf-00; Wed, 18 Nov 1998 00:51:56 +0200 From: Sheldon Hearn To: Jeroen Ruigrok/Asmodai cc: Jason Fesler , current@FreeBSD.ORG Subject: Re: Heads up file In-reply-to: Your message of "Tue, 17 Nov 1998 23:11:05 +0100." Date: Wed, 18 Nov 1998 00:51:56 +0200 Message-ID: <784.911343116@axl.training.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998 23:11:05 +0100, Jeroen Ruigrok/Asmodai wrote: > As far as I am concerned I think it's a good idea, especially with all > the hooks and crannies one tends to forget. For example my last few > posts about sd/da stuff... Then again, I am lame =p Hi Jeroen, I think you've hit the nail on the head. Read the following excerpt from the FreeBSD handbook. In fact, the whole of section 18.1 is well worth reading, not unlike most of the handbook. :-) | 18.1.4. Using FreeBSD-current | | Join the FreeBSD-current mailing list | and the FreeBSD CVS commit message mailing list | . This is not just a good idea, it | is essential. | | If you are not on the FreeBSD-current mailing list you will | not see the comments that people are making about the | current state of the system and thus will probably end up | stumbling over a lot of problems that others have already | found and solved. Even more importantly, you will miss out | on potentially critical information (e.g. ``Yo, Everybody! | Before you rebuild /usr/src, you must rebuild the kernel | or your system will crash horribly!"). | | The cvs-all mailing list will allow you to see the commit | log entry for each change as it is made along with any | pertinent information on possible side-effects. Now, it is obvious that people are _not_ reading this. Do you think the people who are not reading this are any more likely to read a HEADSUP file? If not, then it's requires work that doesn't have a meaningful payoff. I'm pretty sure that the only people who would benefit from the kind of file you're asking for are people who don't need it. :-) But there's no harm in your suggestion. So why am I "shooting it down"? It will require work from "someone". For "someone" to volunteer for such work, he or she will need to be convinced that it'll pay off. I'm just trying to give you insight into why "someone" might not jump forward and say "YES, I will take on this responsibility". Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 15:07:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05206 for freebsd-current-outgoing; Tue, 17 Nov 1998 15:07:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05200 for ; Tue, 17 Nov 1998 15:07:29 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id PAA04390; Tue, 17 Nov 1998 15:06:59 -0800 (PST) Date: Tue, 17 Nov 1998 15:08:15 -0800 (PST) From: Tom Bartol To: Jeroen Ruigrok/Asmodai cc: freebsd-current@FreeBSD.ORG Subject: RE: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > On 17-Nov-98 Tom Bartol wrote: > > > > On Tue, 17 Nov 1998, Jeroen Ruigrok/Asmodai wrote: > > > > No, I'm running stock -current. I must have missed the mail that > > mentioned the patches you speak of. I'd like to try them. Where can I > > find them? > > Do a search on the CURRENT list for NFS and date about a week ago > > --- O.K. I've just looked -- If you're referring to the NFS ACCESS patches, then these have already been committed and so I'm already running with those. If you're not referring to these patches then I can't find what you're trying to point me at -- an exact pointer to what you're talking about would really help in that case. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 15:07:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05426 for freebsd-current-outgoing; Tue, 17 Nov 1998 15:07:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from heaven.gigo.com (ppp.gigo.com [207.173.132.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05275 for ; Tue, 17 Nov 1998 15:07:38 -0800 (PST) (envelope-from jfesler@gigo.com) Received: by heaven.gigo.com (8.8.8/8.8.8) with SMTP id PAA08070; Tue, 17 Nov 1998 15:06:19 -0800 (PST) X-SMTP: helo heaven.gigo.com from jfesler@gigo.com server jfesler@heaven.gigo.com ip 207.173.133.57 Date: Tue, 17 Nov 1998 15:06:16 -0800 (PST) From: Jason Fesler To: Sheldon Hearn cc: Jeroen Ruigrok/Asmodai , current@FreeBSD.ORG Subject: Re: Heads up file In-Reply-To: <784.911343116@axl.training.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > | If you are not on the FreeBSD-current mailing list you will > | not see the comments that people are making about the .. .. Which is noisy beyond believe at times - signal to noise ratio is pretty bad pretty often. We seem to be trying to get more exposure to the 3.0 branch - checkouts of "." are now spitting out 3.0. With the people now using 3.0 it's somethings a bit much to ask they stay current with current (no pun intended). > | The cvs-all mailing list will allow you to see the commit Oh, those are easy to read quicky ;-). Definately invaluable but not the quickest to get through. > Now, it is obvious that people are _not_ reading this. Do you think the > people who are not reading this are any more likely to read a HEADSUP > file? If not, then it's requires work that doesn't have a meaningful > payoff. I think this mainly depends on where it's placed. If it were prominantly placed, it might take a few sticks of clue (Hey! Either read "current" or at least read the heads up file!), but catch on quickly enough. > work, he or she will need to be convinced that it'll pay off. I'm just > trying to give you insight into why "someone" might not jump forward and > say "YES, I will take on this responsibility". I'd certainly be willing to offer this help but I'm only able to commit to once or twice a day 6 days a week. I secondly don't have CVS access in order to maintain it. If I were to work on it, the notes would be brief - and if they required detailed instructions a url to the post in -current would be provided, or the url to a document in the local source tree (whatever is appropriate). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 16:00:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14321 for freebsd-current-outgoing; Tue, 17 Nov 1998 16:00:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14272 for ; Tue, 17 Nov 1998 16:00:06 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id XAA09059; Tue, 17 Nov 1998 23:57:09 GMT (envelope-from nik) Message-ID: <19981117235709.20735@nothing-going-on.org> Date: Tue, 17 Nov 1998 23:57:09 +0000 From: Nik Clayton To: current@FreeBSD.ORG Subject: /etc/rc.d, and changes to /etc/rc? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, [ Originally posted to -hackers. Forwarded to -current at Robert Nordier's request, apparently fewer developers than I thought read -hackers. Reply-to *not* set, I can read replies in either -hackers or -current, and this is probably -current material as much as it is -hackers ] During the day job, I use Solaris. This is not, in and of itself, a bad thing. Solaris uses run levels. I don't particularly like them, but I tolerate them. I *don't* want to bring run levels (or even, if Terry's reading, run states) to FreeBSD. The one useful feature I've found with run [levels|states] as implemented on Solaris is the /etc/init.d directory. For those that don't know, this contains 'n' scripts, one per 'service', that take 'start' and 'stop' parameters. If you want to stop Sendmail, it's sh /etc/init.d/sendmail stop No need to poke around with ps, grep, and friends to determine the PID to kill, no wondering about whether or not there's a lock file you might need to clean up afterwards, and so on. It helps save a little time, and is probably easier for newcomers to understand as well. We already have the beginning of a system like this for ported software, with the ${PREFIX}/etc/rc.d directory. What are people's thoughts on doing the same thing to the base system? In essence, this would involve (on a case by case basis) going through the daemons started in /etc/rc*, building a script to start/stop the daemon, and changing the code in /etc/rc* to call these scripts instead. NOTE: The order in which scripts would be called by /etc/rc* would not be determined by the script name, there would be none of this silliness with S20foo and K50bar, ordering is still determined by /etc/rc* All I want to do is abstract out the daemon start/stop process a little more. Down the road, this could bring other benefits as well; - For those that like run levels/states, it becomes easier for them to create a port with a new version of init that implemented them. People that want run levels install the port, people that don't, don't. - It makes it easier to install replacements for programs that are in the base system. If sendmail was started from /etc/rc.d/smtp.sh, the first thing smtp.sh could check for is the existence of /usr/local/etc/rc.d/smtp.sh, and call that instead if it existed. Replacing sendmail with qmail or vmailer then becomes a little easier. - Simplifies documentation. When explaining how to stop a system process, you don't need to explain ps, grep, kill, awk/cut, backticks, and pipelines. You just say "Do it like this", and explain the magic behind it at a later point. I realise this is a religious issue, and one of those things people like to get all excited about. However, I've just seen a message from Jordan suggesting the ordering be changed in host.conf, and *no one* objected. I figured I'd jump in quickly, before they stop putting Prozac in the water. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 16:17:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19593 for freebsd-current-outgoing; Tue, 17 Nov 1998 16:17:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19562 for ; Tue, 17 Nov 1998 16:17:32 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id TAA01034; Tue, 17 Nov 1998 19:16:56 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Tue, 17 Nov 1998 19:16:55 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Nik Clayton cc: current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? In-Reply-To: <19981117235709.20735@nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Nik Clayton wrote: > Folks, > > [ Originally posted to -hackers. Forwarded to -current at Robert Nordier's > request, apparently fewer developers than I thought read -hackers. > > Reply-to *not* set, I can read replies in either -hackers or -current, > and this is probably -current material as much as it is -hackers ] > > During the day job, I use Solaris. This is not, in and of itself, a bad > thing. > > Solaris uses run levels. I don't particularly like them, but I tolerate > them. I *don't* want to bring run levels (or even, if Terry's reading, > run states) to FreeBSD. I'd recommend searching the mail archives for this issue. It has com e up many times and been shot down every time so far. IMHO, the start/stop scripts don't really add much. The granularity is usually too large for my tastes. e.g. the NFS start/stop scripts on most systems kill/start all of the daemons, when I typically just want to HUP or kill/restart one. Then you also slow booting somewhat. Look at the PID for your first login shell on FreeBSD and solaris and compare. I think you'll be surprised with about the number of exec's. Don't evendare to suggest sourcing the start/stop scripts. That is one of my biggest beefs with solaris' sysv init files is that some are sourced, some are exec'ed and all of them are run with the same shell regardless of the #!. I say leave well enough alone. It's wasted effort. The start/stop directory under /usr/local is enough to satisfy the thrid party software that wants to install without editing the rc-files. All the core services are in existing rc-files and it is just reinventing the wheel to rewite them as a bunch of separate files instead of a few. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 16:25:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20675 for freebsd-current-outgoing; Tue, 17 Nov 1998 16:25:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20668 for ; Tue, 17 Nov 1998 16:25:04 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id TAA13293; Tue, 17 Nov 1998 19:24:22 -0500 (EST) Date: Tue, 17 Nov 1998 19:24:22 -0500 (EST) From: John Fieber To: ADRIAN Filipi-Martin cc: Nik Clayton , current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, ADRIAN Filipi-Martin wrote: > I say leave well enough alone. It's wasted effort. The start/stop > directory under /usr/local is enough to satisfy the thrid party software > that wants to install without editing the rc-files. But I sure wish they would consistently take 'start', 'stop' and 'restart' arguments...most that come with ports are only good for launching. -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 16:45:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23088 for freebsd-current-outgoing; Tue, 17 Nov 1998 16:45:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA23078 for ; Tue, 17 Nov 1998 16:44:59 -0800 (PST) (envelope-from terbart@aye.net) Received: (qmail 8743 invoked by uid 3185); 18 Nov 1998 00:42:56 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 18 Nov 1998 00:42:56 -0000 Date: Tue, 17 Nov 1998 19:42:56 -0500 (EST) From: Barrett Richardson Reply-To: Barrett Richardson To: Terry Lambert cc: Greg Lehey , dhopkins@rtci.com, current@FreeBSD.ORG Subject: Re: Random rebooting In-Reply-To: <199811172220.PAA14095@usr09.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Terry Lambert wrote: > > Actually, I have been able to demonstrate silent reboots since > late 2.2.6, and subsequently. > > I didn't speak up because I assumed it was a local driver problem > with a custom driver. > > The reboots are infrequent, but appear to occur most commonly > with high network load, and more commonly with RIP being the > source of the load. > > The reboot is completely silent; no console logs, no panic message, > nothing -- except "/ was not unmounted cleanly" in the dmesg after > the event. > > FWIW. Me too. My monitor would go >blink<, then .. memory test. Sometimes when I would get home, I would find that it had rebooted a couple times during the day. Sometimes it would run flawlessly for 10 days. Replaced memory, controllers, video cards, even disks. Loaded Virus NT a couple of weeks back and saw the darndest thing. You could wiggle the mouse pointer over an icon and it would smudge as if it were wet paint while Xwindows was unaffected. Found out that it would go away if I turned off the internal cache on the CPU. The reboots ceased -- defective CPU. My MB is a Tyan 1570. - Barrett > > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 16:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24160 for freebsd-current-outgoing; Tue, 17 Nov 1998 16:53:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24154 for ; Tue, 17 Nov 1998 16:53:02 -0800 (PST) (envelope-from marc@netcologne.de) Received: from oranje.my.domain (dial5-74.netcologne.de [194.8.195.74]) by mail2.netcologne.de (8.8.8/8.8.8) with ESMTP id BAA20633 for ; Wed, 18 Nov 1998 01:52:30 +0100 (MET) X-Ncc-Regid: de.netcologne Received: (from marc@localhost) by oranje.my.domain (8.9.1/8.9.1) id BAA03207; Wed, 18 Nov 1998 01:53:41 +0100 (CET) (envelope-from marc) Date: Wed, 18 Nov 1998 01:53:41 +0100 (CET) Message-Id: <199811180053.BAA03207@oranje.my.domain> From: Marc van Woerkom To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! What does this message ===> netscape-communicator-4.5 is marked as broken: PLIST. mean, exactly? Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 17:13:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26324 for freebsd-current-outgoing; Tue, 17 Nov 1998 17:13:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-31-dbn.dial-up.net [196.34.155.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26314 for ; Tue, 17 Nov 1998 17:13:18 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id DAA14132 for current@FreeBSD.ORG; Wed, 18 Nov 1998 03:12:29 +0200 (SAT) From: Robert Nordier Message-Id: <199811180112.DAA14132@ceia.nordier.com> Subject: Re: Heads up file In-Reply-To: from Jason Fesler at "Nov 17, 98 03:06:16 pm" To: current@FreeBSD.ORG Date: Wed, 18 Nov 1998 03:12:26 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA26320 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jason Fesler wrote: > > | If you are not on the FreeBSD-current mailing list you will > > | not see the comments that people are making about the > .. .. Which is noisy beyond believe at times - signal to noise ratio is > pretty bad pretty often. We seem to be trying to get more exposure to the > 3.0 branch - checkouts of "." are now spitting out 3.0. With the people > now using 3.0 it's somethings a bit much to ask they stay current with > current (no pun intended). > > > | The cvs-all mailing list will allow you to see the commit > > Oh, those are easy to read quicky ;-). Definately invaluable but not the > quickest to get through. > > > Now, it is obvious that people are _not_ reading this. Do you think the > > people who are not reading this are any more likely to read a HEADSUP > > file? If not, then it's requires work that doesn't have a meaningful > > payoff. > > I think this mainly depends on where it's placed. If it were prominantly > placed, it might take a few sticks of clue (Hey! Either read "current" or > at least read the heads up file!), but catch on quickly enough. Many folks are presently treating FreeBSD-current as though it is just a rather more sexy and desirable version of FreeBSD-stable. This is understandable, given the extremely long gestation period of 3.0-RELEASE. But it is also completely at odds with the intended purpose of the -current branch. The handbook delimits just two categories of people who were intended to *run* FreeBSD-current: o FreeBSD developers o FreeBSD testers These developers and testers are folks who, in a commercial enterprise, would actually have to be *paid* to work on an in-house, alpha-quality version of the product. The current branch was intended to be treated somewhat like a "restricted area", on the same basis that a factory floor is a restricted area. Because hard, and sometimes dangerous, work is going on there, and bystanders are likely to get their fingers chopped off if they lose concentration. FreeBSD-current was never meant to be "comfortable", it was meant to be "endured" by developers/testers as a necessary part of advancing FreeBSD. Making -current more accessible and user-friendly to folks who are not actively engaged in development or testing is likely to be ultimately counter-productive. And it has the potential to severely limit what can be done by developers, if false expectations (that FreeBSD-current is really just a cool, safe, fun place to be) are encouraged. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 17:23:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27689 for freebsd-current-outgoing; Tue, 17 Nov 1998 17:23:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27684 for ; Tue, 17 Nov 1998 17:23:30 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id UAA28352; Tue, 17 Nov 1998 20:23:01 -0500 (EST) (envelope-from wollman) Date: Tue, 17 Nov 1998 20:23:01 -0500 (EST) From: Garrett Wollman Message-Id: <199811180123.UAA28352@khavrinen.lcs.mit.edu> To: John Fieber Cc: ADRIAN Filipi-Martin , Nik Clayton , current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > But I sure wish they would consistently take 'start', 'stop' and > 'restart' arguments...most that come with ports are only good for > launching. Yes, the ports are almost all broken -- that's one of my biggest beefs. When you consider how trivial it usually is: #!/bin/sh case "$1" in stop) killall postmaster;; *) rm -f /tmp/.s.PGSQL.* su -l postgres -c 'exec postmaster -S -o -F >$HOME/errlog' & echo -n ' pgsql';; esac ...there's really no excuse for not doing it right. -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, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 17:45:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29684 for freebsd-current-outgoing; Tue, 17 Nov 1998 17:45:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lonegunman.xfiles.org.uk (lonegunman.xfiles.org.uk [194.200.230.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29673 for ; Tue, 17 Nov 1998 17:45:25 -0800 (PST) (envelope-from benhutch@lonegunman.xfiles.org.uk) Received: (from benhutch@localhost) by lonegunman.xfiles.org.uk (8.9.1/8.9.1) id BAA16434; Wed, 18 Nov 1998 01:44:46 GMT (envelope-from benhutch) Message-ID: <19981118014446.C15587@xfiles.org.uk> Date: Wed, 18 Nov 1998 01:44:46 +0000 From: Ben Hutchinson To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? References: <199811180123.UAA28352@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811180123.UAA28352@khavrinen.lcs.mit.edu>; from Garrett Wollman on Tue, Nov 17, 1998 at 08:23:01PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In which case how about implementing something a little more sysv-ish for only ports? Ie, a rough idea: /usr/local/etc/rcS.d for startup scripts /usr/local/etc/rcK.d for shutdown scripts With a "compatibilty" /usr/local/etc/rc.d directory for old style ports. New ports which wish to use sysv-ish startup and shutdown can. Those which don't, don't. Would this provide sufficient granularity? - Ben On Tue, Nov 17, 1998 at 08:23:01PM -0500, Garrett Wollman wrote: > Yes, the ports are almost all broken -- that's one of my biggest > beefs. > > When you consider how trivial it usually is: > > #!/bin/sh > case "$1" in > stop) killall postmaster;; > *) > rm -f /tmp/.s.PGSQL.* > su -l postgres -c 'exec postmaster -S -o -F >$HOME/errlog' & > echo -n ' pgsql';; > esac > > ...there's really no excuse for not doing it right. -- "I Want To Believe" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 18:11:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02801 for freebsd-current-outgoing; Tue, 17 Nov 1998 18:11:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02795 for ; Tue, 17 Nov 1998 18:11:32 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA13245; Tue, 17 Nov 1998 19:11:04 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd013129; Tue Nov 17 19:10:55 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA21262; Tue, 17 Nov 1998 19:10:10 -0700 (MST) From: Terry Lambert Message-Id: <199811180210.TAA21262@usr01.primenet.com> Subject: Re: Random rebooting To: terbart@aye.net Date: Wed, 18 Nov 1998 02:10:09 +0000 (GMT) Cc: tlambert@primenet.com, grog@lemis.com, dhopkins@rtci.com, current@FreeBSD.ORG In-Reply-To: from "Barrett Richardson" at Nov 17, 98 07:42:56 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Me too. My monitor would go >blink<, then .. memory test. Sometimes > when I would get home, I would find that it had rebooted a couple > times during the day. Sometimes it would run flawlessly for 10 days. > Replaced memory, controllers, video cards, even disks. Loaded > Virus NT a couple of weeks back and saw the darndest thing. You > could wiggle the mouse pointer over an icon and it would smudge > as if it were wet paint while Xwindows was unaffected. Found out that it > would go away if I turned off the internal cache on the CPU. The reboots > ceased -- defective CPU. My MB is a Tyan 1570. This is on a 486DX/4-100, no L2 cache, sufficient stepping that the L1 cache should be OK, but I have tried it with the L1 cache disabled (had to hack a control register in locore.s to do it), with the same effect. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 18:50:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05951 for freebsd-current-outgoing; Tue, 17 Nov 1998 18:50:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05868 for ; Tue, 17 Nov 1998 18:49:58 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id VAA03471; Tue, 17 Nov 1998 21:49:31 -0500 (EST) Date: Tue, 17 Nov 1998 21:49:31 -0500 (EST) Message-Id: <199811180249.VAA03471@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Killed Myself Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After installing the recent libc_r and libc, I'm getting: ld.so failed: Undefined symbol "SYS_kldsym" in make:/usr/lib/aout/libc.so.3.1 I also get it sometimes when I link against libc_r. "SYS_kldsym" is always the thing I don't seem to have a definition for. This just started happening. UGH! -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 19:56:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11816 for freebsd-current-outgoing; Tue, 17 Nov 1998 19:56:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11807 for ; Tue, 17 Nov 1998 19:56:04 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from william.cybcon.com (william@usr1-0.cybcon.com [205.147.76.1]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id TAA23671 for ; Tue, 17 Nov 1998 19:55:18 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 17 Nov 1998 19:53:22 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: FreeBsd-Current Subject: StarOffice 5.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Tue, 17 Nov 1998 17:08:33 -0800 (PST) From: William Woods To: FreeBsd-Questions Subject: StarOffice 5.0 Rumor has it that there are people who have gotten StarOffice 5.0 to run on an aout system. Please let me know how.... ---------------------------------- E-Mail: William Woods Date: 17-Nov-98 Time: 19:52:54 -->> FreeBSD 3.0 <<-- AIM bsdman1 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 21:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20827 for freebsd-current-outgoing; Tue, 17 Nov 1998 21:46:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20822 for ; Tue, 17 Nov 1998 21:46:01 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id XAA29327; Tue, 17 Nov 1998 23:45:27 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id XAA04652; Tue, 17 Nov 1998 23:43:07 -0600 (CST) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13906.24128.702398.773664@zuhause.zuhause.mn.org> Date: Tue, 17 Nov 1998 23:42:24 -0600 (CST) To: Marc van Woerkom Cc: freebsd-current@FreeBSD.ORG Subject: Re: [netscape communicator-4.5] In-Reply-To: <199811180053.BAA03207@oranje.my.domain> References: <199811180053.BAA03207@oranje.my.domain> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marc van Woerkom writes: > Hi! > > What does this message > > ===> netscape-communicator-4.5 is marked as broken: PLIST. It means that if you want to run it, you'll need to install it manually, it's still aout so you'll need to have aout compatibility libraries, and if you want real encryption, you'll have to do the fortify yourself. I think that if you want to hack the Makefile to install it for you, it's pretty easy. It took me about 10 minutes. Since aout libraries are deprecated, I'm guessing that the porter are waiting for Netscape to build an elf version. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 17 22:10:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22814 for freebsd-current-outgoing; Tue, 17 Nov 1998 22:10:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from badlans.lanminds.com (badlans.lanminds.com [208.25.91.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22809 for ; Tue, 17 Nov 1998 22:10:03 -0800 (PST) (envelope-from rrs@badlans.lanminds.com) Received: (from rrs@localhost) by badlans.lanminds.com (8.8.6/8.8.6) id WAA11059; Tue, 17 Nov 1998 22:11:01 -0800 (PST) Date: Tue, 17 Nov 1998 22:11:01 -0800 (PST) From: Robert Schulhof Message-Id: <199811180611.WAA11059@badlans.lanminds.com> To: current@FreeBSD.ORG, info@highwind.com Subject: Re: Killed Myself Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had a similar problem when I recompiled in the libc_r directory rather than doing a buildworld. Copying /usr/src/sys/sys/syscall.h to /usr/include/sys solved the problem. I guess kldsym() was the last system call added. Hope that helps Robert Schulhof UNIX System Administrator LanMinds Internet. (LMI Net) rrs@lmi.net http://www.lmi.net (510) 843-6389 VOX (510) 843-6390 FAX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 00:08:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00163 for freebsd-current-outgoing; Wed, 18 Nov 1998 00:08:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skunkworks.specialty.ab.ca (skunkworks.specialty.ab.ca [207.167.8.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00158 for ; Wed, 18 Nov 1998 00:08:39 -0800 (PST) (envelope-from j.b.george@ieee.org) Received: (from uucp@localhost) by skunkworks.specialty.ab.ca (8.8.8/8.8.8) with UUCP id BAA19608 for freebsd-current@freebsd.org; Wed, 18 Nov 1998 01:08:14 -0700 (MST) (envelope-from j.b.george@ieee.org) Received: from infomat (infomat [192.168.4.2]) by gongshow.masterplan.org (8.8.8/8.8.8) with SMTP id BAA19619 for ; Wed, 18 Nov 1998 01:07:08 -0700 (MST) (envelope-from j.b.george@ieee.org) Received: by infomat with Microsoft Mail id <01BE128F.CD600D40@infomat>; Wed, 18 Nov 1998 01:07:24 -0700 Message-ID: <01BE128F.CD600D40@infomat> From: Jason George To: "'freebsd-current@freebsd.org'" Subject: Issue with Bad Block scan on fresh disk Date: Wed, 18 Nov 1998 01:07:23 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA00159 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was building two new 3.0 boxes when I stumbled upon a little nuance with the bad block scan within the initial sysinstall. I was wondering if anyone else had noticed this or had any suggestions. Here's the scenario: I took a new 5.2G Quantum IDE drive out of the sealed static bag, configured the BIOS to detect it, and booted the 3.0-RELEASE boot floppy. I chose a Custom Install, and Dangerously Dedicated the entire disk, set it bootable, and flagged a Bad Block Scan. I then sliced the disk. When it finally came time to do the bad block scan and subsequent filesystem generation, the bad block scan DID NOT proceed, yet the filesystem generation and system install did continue to completion. A little perplexed, I rebooted and followed my normal installation procedure (Custom Install, Dangerously Dedicated, etc, as above). This time, the bad block scan ran before the filesystem generation. The system install continued to completion. I thought this was a freak occurence, but when I built a second box with another farm-fresh virgin drive using the same procedure, the bad block scan was ignored again. I reinstalled a second time on the second box. The bad block scan ran fine. I'd dig more into this, but the cost of iteration makes the work a little difficult. ;-) --Jason j.b.georgeieee.org jbgmasterplan.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 00:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00620 for freebsd-current-outgoing; Wed, 18 Nov 1998 00:13:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00615; Wed, 18 Nov 1998 00:13:33 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.1/8.9.1) with ESMTP id JAA00871; Wed, 18 Nov 1998 09:12:44 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id JAA25327; Wed, 18 Nov 1998 09:12:43 +0100 (CET) From: Cejka Rudolf Message-Id: <199811180812.JAA25327@kazi.dcse.fee.vutbr.cz> Subject: Re: Is it soup yet? FreeBSD NFS In-Reply-To: <199811171622.RAA10676@rt2.synx.com> from Remy Nonnenmacher at "Nov 17, 98 05:17:46 pm" To: remy@synx.com Date: Wed, 18 Nov 1998 09:12:42 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (CC: hackers) > On 13 Nov, Cejka Rudolf wrote: > > > > We have long-time problems (not critical) with NFS server running > > on FreeBSD 2.2.6/2.2.7/3.0 against Solaris 2.5/2.6 clients there. > > > > Our problem: > > > > FreeBSD: NFS server without any special parameters. > > Solaris: NFS client without any special parameters. > > > > Example - working on Solaris above mounted filesystem from FreeBSD: > > > > $ gzcat less-332.tar.gz | tar xvf - # This creates 74 files in > > # directory less-332 > > $ rm -r less-332 # This _leaves_ 43 files! > > rm: Unable to remove directory less-332: File exists > > $ rm -r less-332 # This _still leaves_ 15 files! > > rm: Unable to remove directory less-332: File exists > > $ rm -r less-332 # Uff, directory is removed now... > > > > I think, problem is in different versions (NFSv2 vs. NFSv3) - but it > > looks very trivial (?). If I mount NFS exported filesystem (exports > > FreeBSD) on Solaris with option "vers=2" (it says "use NFSv2"), > > problems disappear. But we are using cachefs (cached filesystem) over > > NFS with automounting feature and we have no change to say "cachefs, > > mount NFS filesystem with 'vers=2' option". There isn't any parameter > > for this on Solaris... > > I have an open problem on this (pr5890). Look at it and try the > suggested fix. The machine where it is applied runs NFS serving for now > 7 month and no problems appeared (clients: Solaris, aix, sco, hpux). > > No need to say that this needs a competent blessing....(re-read the BSD > license before trying it :). > > RN. Yes. It looks it is the problem. Thanks. I have tried to debug mentioned code. Source code is: if (!error && toff && verf && verf != at.va_filerev) error = NFSERR_BAD_COOKIE; And in case of "rm -r less-332" values for example are: error: 0 toff: 5c:02:00:00:00:00:00:00 (memory dump) verf: c7:a4:7c:5a:5b:00:00:00 (memory dump) at.va_filerev: e6:a4:7c:5a:5b:00:00:00 (memory dump) In every next "rm -r less-332" try value in at.va_filerev goes into verf and at.va_filerev contains new unknown value. So is this bug on Solaris side? (Or FreeBSD?) Is there any possible workaround without disabling COOKIE tests? Thanks. --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 00:43:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA04018 for freebsd-current-outgoing; Wed, 18 Nov 1998 00:43:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rt2.synx.com (tech.boostworks.com [194.167.81.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03980; Wed, 18 Nov 1998 00:43:45 -0800 (PST) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id JAA12651; Wed, 18 Nov 1998 09:47:53 +0100 (CET) Message-Id: <199811180847.JAA12651@rt2.synx.com> Date: Wed, 18 Nov 1998 09:42:51 +0100 (CET) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: Re: Is it soup yet? FreeBSD NFS To: cejkar@dcse.fee.vutbr.cz cc: freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG In-Reply-To: <199811180812.JAA25327@kazi.dcse.fee.vutbr.cz> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Nov, Cejka Rudolf wrote: > > (CC: hackers) > >> On 13 Nov, Cejka Rudolf wrote: >> > >> > We have long-time problems (not critical) with NFS server running >> > on FreeBSD 2.2.6/2.2.7/3.0 against Solaris 2.5/2.6 clients there. >> > >> > Our problem: >> > >> > FreeBSD: NFS server without any special parameters. >> > Solaris: NFS client without any special parameters. >> > >> > Example - working on Solaris above mounted filesystem from FreeBSD: >> > >> > $ gzcat less-332.tar.gz | tar xvf - # This creates 74 files in >> > # directory less-332 >> > $ rm -r less-332 # This _leaves_ 43 files! >> > rm: Unable to remove directory less-332: File exists >> > $ rm -r less-332 # This _still leaves_ 15 files! >> > rm: Unable to remove directory less-332: File exists >> > $ rm -r less-332 # Uff, directory is removed now... >> > >> > I think, problem is in different versions (NFSv2 vs. NFSv3) - but it >> > looks very trivial (?). If I mount NFS exported filesystem (exports >> > FreeBSD) on Solaris with option "vers=2" (it says "use NFSv2"), >> > problems disappear. But we are using cachefs (cached filesystem) over >> > NFS with automounting feature and we have no change to say "cachefs, >> > mount NFS filesystem with 'vers=2' option". There isn't any parameter >> > for this on Solaris... >> >> I have an open problem on this (pr5890). Look at it and try the >> suggested fix. The machine where it is applied runs NFS serving for now >> 7 month and no problems appeared (clients: Solaris, aix, sco, hpux). >> >> No need to say that this needs a competent blessing....(re-read the BSD >> license before trying it :). >> >> RN. > > Yes. It looks it is the problem. Thanks. > > I have tried to debug mentioned code. Source code is: > > if (!error && toff && verf && verf != at.va_filerev) > error = NFSERR_BAD_COOKIE; > > And in case of "rm -r less-332" values for example are: > error: 0 > toff: 5c:02:00:00:00:00:00:00 (memory dump) > verf: c7:a4:7c:5a:5b:00:00:00 (memory dump) > at.va_filerev: e6:a4:7c:5a:5b:00:00:00 (memory dump) > In every next "rm -r less-332" try value in at.va_filerev goes into verf > and at.va_filerev contains new unknown value. So is this bug on > Solaris side? (Or FreeBSD?) Is there any possible workaround without > disabling COOKIE tests? > > Thanks. > > --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- > Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) > Technical University of Brno, Faculty of El. Engineering and Comp. Science > Bozetechova 2, 612 66 Brno, Czech Republic It clearly requires a NFS' god blessing. My view of it is that the cookie identifying a directory changes after a few operations (maybe after releasing a block of free entries. May be checked by removing files in reverse scanning order ?) but client continue to use the old cookie. Reading NFS specs would say if server is wrong in changing the cookie or is the client is wrong to use an old one. I'm not competent enought to go further. "peter" at -bugs is in charge of it and, considering the NFS complexity, I assume the problem is not simple. RN. ItM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 01:45:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08858 for freebsd-current-outgoing; Wed, 18 Nov 1998 01:45:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08852 for ; Wed, 18 Nov 1998 01:45:38 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA09352; Wed, 18 Nov 1998 10:46:16 +0100 (BST) Date: Wed, 18 Nov 1998 09:46:16 +0000 (GMT) From: Doug Rabson To: HighWind Software Information cc: current@FreeBSD.ORG Subject: Re: Killed Myself In-Reply-To: <199811180249.VAA03471@highwind.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, HighWind Software Information wrote: > > After installing the recent libc_r and libc, I'm getting: > > ld.so failed: Undefined symbol "SYS_kldsym" in make:/usr/lib/aout/libc.so.3.1 > > I also get it sometimes when I link against libc_r. > > "SYS_kldsym" is always the thing I don't seem to have a definition for. > > This just started happening. UGH! This is a new syscall. Re-install the includes and rebuild libc. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 01:54:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10114 for freebsd-current-outgoing; Wed, 18 Nov 1998 01:54:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10101 for ; Wed, 18 Nov 1998 01:54:45 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA24723; Wed, 18 Nov 1998 20:54:15 +1100 Date: Wed, 18 Nov 1998 20:54:15 +1100 From: Bruce Evans Message-Id: <199811180954.UAA24723@godzilla.zeta.org.au> To: current@FreeBSD.ORG, winter@jurai.net Subject: Re: /dev/ioport[bwl] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Whats the story on the > >#ifdef notyet >... >#endif > >Bits around the code implementing /dev/ioport[bwl] in >src/sys/i386/i386/mem.c? It should have gone away 6 years ago. >I'd like to use /dev/io and friends (/dev/ioport[bwl] if they exist) to do >some PIO routine prototyping for a device driver. Opening /dev/io gives direct access to i/o instructions. This is much easier and just as (in)secure as /dev/ioport would be. Drivers should probably be prototyped using modules. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 01:59:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA10817 for freebsd-current-outgoing; Wed, 18 Nov 1998 01:59:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA10778 for ; Wed, 18 Nov 1998 01:59:24 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id TAA01090; Tue, 17 Nov 1998 19:39:19 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp02.primenet.com, id smtpd000979; Tue Nov 17 19:39:11 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id TAA22932; Tue, 17 Nov 1998 19:38:57 -0700 (MST) From: Terry Lambert Message-Id: <199811180238.TAA22932@usr01.primenet.com> Subject: Re: Is it soup yet? :-) To: jb@cimlogic.com.au (John Birrell) Date: Wed, 18 Nov 1998 02:38:57 +0000 (GMT) Cc: julian@whistle.com, dag-erli@ifi.uio.no, green@unixhelp.org, jkh@zippy.cdrom.com, peter@netplex.com.au, mike@smith.net.au, current@FreeBSD.ORG In-Reply-To: <199811120415.PAA08645@cimlogic.com.au> from "John Birrell" at Nov 12, 98 03:15:00 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > they fetch updates overr the net. > > but they don't have code to replace the bootblocks > > to do that would mean 2 upgrades, one to get the new software that CAN do > > so, and one to replace them. > > So why can't you do that?! > Do you have dependencies between your upgrade versions (or whatever you > call them)? Yes. You have to be able to downgrade automatically if the upgrade doesn't work. No matter what happens, it has to work. Period. If you have questions as to what this has to do with a.out on post upgrade hardware, you can ask Julian for more detail. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 02:14:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12509 for freebsd-current-outgoing; Wed, 18 Nov 1998 02:14:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12489 for ; Wed, 18 Nov 1998 02:14:10 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA09307; Wed, 18 Nov 1998 10:42:51 +0100 (BST) Date: Wed, 18 Nov 1998 09:42:51 +0000 (GMT) From: Doug Rabson To: Tom Bartol cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, Tom Bartol wrote: > > Hi all, > > I've been seeing the following problem for a while now (since > 3.0-19981006-BETA) but was too busy at the time to report it or help > diagnose it further. Now I've got some time on my hands... > > I can fairly consistently wedge NFS writes to our server with the > following: > > dd if=/dev/zero of=ick bs=8192 count=1000 > > which tries to write an 8MB file to our file server which is an Auspex. I > have mounted Auspex from my 3.0-current machine (cvsupped and built this > morning) in NFSv3 mode. This command will wedge one or more of the nfsiod > processes. "ps -auwx | grep nfsiod" reports the following: > > root 137 0.0 0.0 216 64 ?? I 9:12AM 0:02.31 nfsiod -n 4 > root 138 0.0 0.0 216 64 ?? I 9:12AM 0:01.74 nfsiod -n 4 > root 139 0.0 0.0 216 64 ?? D 9:12AM 0:00.27 nfsiod -n 4 > root 140 0.0 0.0 216 64 ?? D 9:12AM 0:00.24 nfsiod -n 4 > > The two processes in state "D" are the wedged ones. A separate machine > running -current from July 11 works fine. > > Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS > reads work fine. > > Is anyone else seeing similar behaviour? What can I do to try to fine > tune a diagnosis and help solve the problem? > > Thanks for your help, The best place to start is to get a tcpdump of the set of transactions which wedged the iod. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 02:39:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15193 for freebsd-current-outgoing; Wed, 18 Nov 1998 02:39:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15185 for ; Wed, 18 Nov 1998 02:39:02 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id LAA05550 for freebsd-current@FreeBSD.ORG; Wed, 18 Nov 1998 11:38:05 +0100 (CET) Message-ID: <19981118113805.A5521@foobar.franken.de> Date: Wed, 18 Nov 1998 11:38:05 +0100 From: Harold Gutch To: freebsd-current@FreeBSD.ORG Subject: page fault when rm'ing on ccd-partition Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm experiencing problems on a (non-local) 3.0-19980916-SNAP non-SMP System. When rm'ing certain files from a ccd'd disk the machine panics. I can't really localize the problem any further as: - I don't know which files exactly cause the problem, or what they have in common, find -mtime 7 | xargs rm over one of the ccd-partitions reproducebly panics the machine though. - A person local to the machine wrote down the following panic-output: Fatal Trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xf01152c7 stack pointer = 0x10:0xf0211f7c frame pointer = 0x10:0xf0211f94 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL0, pres 1, def32 1, gran 1 processor flags = interrupt enabled, resume, IOPL=0 current process = Idle interrupt mask = cam trap number = 12 panic: page fault $ nm -aout /kernel | grep f01152 f0115288 t _ahc_handle_target_cmd from /etc/ccd.conf: ccd1 65536 0 /dev/sd4g /dev/sd5g /dev/sd6g /dev/sd7g So if it's the SCSI-driver which causes the panics, trying to dump to a SCSI-disk isn't very likely to succeed :). - The kernel even refuses to dump to a newly plugged in IDE-disk, a partition of which is configured as swap- and dumpdevice, but after booting the output "savecore: no core dump" can be seen. As the machine is about an hour's ride away from me, I'd rather be able to debug the problem remotely. I asked for a serial cable to a linux-box standing next to the FreeBSD-machine, I guess I then could use it as console, get it to fall to ddb when panicing and then get a stacktrace - or am I missing something that wouldn't work ? If i got the kernel do dump to the IDE-disk, that too would of course help... any ideas why this is failing ? -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. ed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 03:38:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21190 for freebsd-current-outgoing; Wed, 18 Nov 1998 03:38:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21173 for ; Wed, 18 Nov 1998 03:38:22 -0800 (PST) (envelope-from grg@philol.msu.ru) Received: from localhost (grg@localhost) by isabase.philol.msu.ru (8.9.1/8.9.1) with ESMTP id OAA03202; Wed, 18 Nov 1998 14:35:03 +0300 (MSK) (envelope-from grg@philol.msu.ru) X-Authentication-Warning: isabase.philol.msu.ru: grg owned process doing -bs Date: Wed, 18 Nov 1998 14:35:03 +0300 (MSK) From: Grigoriy Strokin To: Nik Clayton cc: current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? In-Reply-To: <19981117235709.20735@nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know that Solaris /etc/inittab provides a very robust mechanism for rerunning a process with a given pid if it dies. The analogue in FreeBSD is /etc/ttys: if mgetty/xdm exits/dies another instance is started. inittab is more flexible, because the processes have not to be connected to terminals... For example, I'd like to restart inetd in my FreeBSD current every time it dies 1-4 times per week :) Grigoriy. On Tue, 17 Nov 1998, Nik Clayton wrote: > Folks, > > [ Originally posted to -hackers. Forwarded to -current at Robert Nordier's > request, apparently fewer developers than I thought read -hackers. > > Reply-to *not* set, I can read replies in either -hackers or -current, > and this is probably -current material as much as it is -hackers ] > > During the day job, I use Solaris. This is not, in and of itself, a bad > thing. > > Solaris uses run levels. I don't particularly like them, but I tolerate > them. I *don't* want to bring run levels (or even, if Terry's reading, > run states) to FreeBSD. > > The one useful feature I've found with run [levels|states] as implemented > on Solaris is the /etc/init.d directory. For those that don't know, this > contains 'n' scripts, one per 'service', that take 'start' and 'stop' > parameters. If you want to stop Sendmail, it's > > sh /etc/init.d/sendmail stop > > No need to poke around with ps, grep, and friends to determine the PID to > kill, no wondering about whether or not there's a lock file you might > need to clean up afterwards, and so on. It helps save a little time, and > is probably easier for newcomers to understand as well. > > We already have the beginning of a system like this for ported software, > with the ${PREFIX}/etc/rc.d directory. > > What are people's thoughts on doing the same thing to the base system? > > In essence, this would involve (on a case by case basis) going through > the daemons started in /etc/rc*, building a script to start/stop the > daemon, and changing the code in /etc/rc* to call these scripts instead. > > NOTE: The order in which scripts would be called by /etc/rc* would not > be determined by the script name, there would be none of this silliness > with S20foo and K50bar, ordering is still determined by /etc/rc* > > All I want to do is abstract out the daemon start/stop process a little > more. > > Down the road, this could bring other benefits as well; > > - For those that like run levels/states, it becomes easier for them to > create a port with a new version of init that implemented them. > People that want run levels install the port, people that don't, don't. > > - It makes it easier to install replacements for programs that are in > the base system. If sendmail was started from /etc/rc.d/smtp.sh, > the first thing smtp.sh could check for is the existence of > /usr/local/etc/rc.d/smtp.sh, and call that instead if it existed. > Replacing sendmail with qmail or vmailer then becomes a little easier. > > - Simplifies documentation. When explaining how to stop a system process, > you don't need to explain ps, grep, kill, awk/cut, backticks, and > pipelines. You just say "Do it like this", and explain the magic > behind it at a later point. > > I realise this is a religious issue, and one of those things people like > to get all excited about. However, I've just seen a message from Jordan > suggesting the ordering be changed in host.conf, and *no one* objected. > I figured I'd jump in quickly, before they stop putting Prozac in the > water. > > N > -- > C.R.F. Consulting -- we're run to make me richer. . . > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > === Grigoriy Strokin, Lomonosov University (MGU), Moscow === === contact info: http://isabase.philol.msu.ru/~grg/ === To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 04:01:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23647 for freebsd-current-outgoing; Wed, 18 Nov 1998 04:01:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23629; Wed, 18 Nov 1998 04:01:20 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from cybcon.com (wwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id EAA11106; Wed, 18 Nov 1998 04:00:53 -0800 (PST) Date: Wed, 18 Nov 1998 04:00:53 -0800 (PST) From: Bill Woods To: questions@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: StatrOffice 5.0 In-Reply-To: <615CAC0140CED111AF1500805FEDDB8A0D3AAA@ns.new-mediacom.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I remember reading somewhere on this list(s) there there was work on getting StarOffice 5.0 to run on FreeBSD. I am currently running FreeBSD 3.0 -current, cvsupped and compiled last night. What is the status of getting this working/ Someone mentioned on irc last night that it has been successfull? Someone fill me in here, as I have herd good things about this program William To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 04:23:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28084 for freebsd-current-outgoing; Wed, 18 Nov 1998 04:23:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nomad.dataplex.net (nomad.dataplex.net [208.2.87.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28076; Wed, 18 Nov 1998 04:23:28 -0800 (PST) (envelope-from rkw@nomad.dataplex.net) Received: from localhost (rkw@localhost) by nomad.dataplex.net (8.9.1/8.9.1) with ESMTP id GAA15688; Wed, 18 Nov 1998 06:22:27 -0600 (CST) (envelope-from rkw@nomad.dataplex.net) Date: Wed, 18 Nov 1998 06:22:27 -0600 (CST) From: Richard Wackerbarth To: Mark Murray cc: Eivind Eklund , Satoshi Asami , current@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? In-Reply-To: <199811161752.TAA01647@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 16 Nov 1998, Mark Murray wrote: > Eivind Eklund wrote: > > I think the first one also is nice to have. Some of us want to update perl > > and the rest of the system independently of each other (e.g, due to local > > hacks to the perl code, for people doing development of Perl itself). > > OK - I'll buy that. I'd prefer it to be undocumented, so people won't find > the switch, frob it, and get burnt. BUZZ ... WRONG ANSWER. Please document it properly so that people won't get burned. It's better to tell someone why they shouldn't play with matches rather than just hiding them on the top shelf. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 04:42:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29518 for freebsd-current-outgoing; Wed, 18 Nov 1998 04:42:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29512 for ; Wed, 18 Nov 1998 04:42:33 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from mercury (mercury [129.127.36.44]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id XAA29115; Wed, 18 Nov 1998 23:12:05 +1030 (CST) Received: from localhost by mercury; (5.65v3.2/1.1.8.2/27Nov97-0404PM) id AA00202; Wed, 18 Nov 1998 23:12:03 +1030 Date: Wed, 18 Nov 1998 23:12:01 +1030 (CST) From: Kris Kennaway To: Richard Wackerbarth Cc: current@FreeBSD.ORG Subject: Re: perl5 is needed to build kernel, why the a make.conf option NOPERL5 ? In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Richard Wackerbarth wrote: > > Eivind Eklund wrote: > > > I think the first one also is nice to have. Some of us want to update perl > > > and the rest of the system independently of each other (e.g, due to local > > > hacks to the perl code, for people doing development of Perl itself). > > > > OK - I'll buy that. I'd prefer it to be undocumented, so people won't find > > the switch, frob it, and get burnt. > > BUZZ ... WRONG ANSWER. > > Please document it properly so that people won't get burned. It's better > to tell someone why they shouldn't play with matches rather than just > hiding them on the top shelf. :-) Setting NOPERL=true is useful to me because it takes a fair mount of time to rebuild, even if the source hasn't changed. I recompile my world using 'make depend;make all', which while it's not the recommended or supported way to recompile things, does save lots of compilation time (I haven't needed to do a make world since E-day). Leaving PERL building turned on causes lots of 'null' recompilation of things which haven't changed (formatting manpages, etc)..so I only bother to recompile it when I see a commit message stating something important has been changed. As long as the effects of setting the flag are documented, I don't see a problem with keeping it visible to casual inspection (as opposed to burying it somewhere where it will never be noticed :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 04:54:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA00336 for freebsd-current-outgoing; Wed, 18 Nov 1998 04:54:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gw-nl1.philips.com (gw-nl1.philips.com [192.68.44.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA00331 for ; Wed, 18 Nov 1998 04:54:21 -0800 (PST) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-nl1.philips.com (localhost.philips.com [127.0.0.1]) by gw-nl1.philips.com with ESMTP id NAA29979 for ; Wed, 18 Nov 1998 13:53:53 +0100 (MET) (envelope-from Jos.Backus@nl.origin-it.com) Received: from smtprelay-eur1.philips.com(130.139.36.3) by gw-nl1.philips.com via mwrap (4.0a) id xma029977; Wed, 18 Nov 98 13:53:53 +0100 Received: from hal.mpn.cp.philips.com (hal.mpn.cp.philips.com [130.139.64.195]) by smtprelay-nl1.philips.com (8.8.5/8.6.10-1.2.2m-970826) with SMTP id NAA26036 for ; Wed, 18 Nov 1998 13:53:52 +0100 (MET) Received: (qmail 6041 invoked by uid 666); 18 Nov 1998 12:54:13 -0000 Date: Wed, 18 Nov 1998 13:54:13 +0100 From: Jos Backus To: current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? Message-ID: <19981118135413.C3308@hal.mpn.cp.philips.com> References: <19981117235709.20735@nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.10i In-Reply-To: ; from Grigoriy Strokin on Wed, Nov 18, 1998 at 02:35:03PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 18, 1998 at 02:35:03PM +0300, Grigoriy Strokin wrote: > For example, I'd like to restart inetd in my FreeBSD current every time it > dies 1-4 times per week :) In that case, you may find http://pobox.com/~djb/daemontools.html to be of interest. -- Jos Backus _/ _/_/_/ "Reliability means never _/ _/ _/ having to say you're sorry." _/ _/_/_/ -- D. J. Bernstein _/ _/ _/ _/ Jos.Backus@nl.origin-it.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 06:29:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11802 for freebsd-current-outgoing; Wed, 18 Nov 1998 06:29:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megadeth.rtci.com (megadeth.noc.rtci.com [216.27.37.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11793 for ; Wed, 18 Nov 1998 06:29:21 -0800 (PST) (envelope-from dhopkins@rtci.com) Received: from rtci.com (oxygen.schizo.com [216.27.37.251]) by megadeth.rtci.com (8.8.8/8.8.8) with ESMTP id JAA26631; Wed, 18 Nov 1998 09:33:41 -0500 (EST) (envelope-from dhopkins@rtci.com) Message-ID: <3652DC31.9A1754FE@rtci.com> Date: Wed, 18 Nov 1998 09:39:45 -0500 From: Damon Hopkins Organization: Research Triangle Consultants, Inc. X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: Current Mailing list Subject: Re: Random rebooting References: <199811180210.TAA21262@usr01.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This sounds like what is happening to me. This machine is a AMD 486-133 w/ 24 MB RAM no funky drivers or anything.. it has NEVER rebooted like this before.. I don't know about the heavy network load I did some huge file transfers yesterday on our lan and had no ill effects. Well, well, well, what to do. -- [-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=-] [ Damon Hopkins mailto: dhopkins@rtci.com ] [ Software Developer http://totally.schizo.com ] [ Research Triangle Consultants, Inc. http://www.rtci.com ] [ -- In search of the elusive 50 sided triangle. -- ] [-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=-] Terry Lambert wrote: > > > Me too. My monitor would go >blink<, then .. memory test. Sometimes > > when I would get home, I would find that it had rebooted a couple > > times during the day. Sometimes it would run flawlessly for 10 days. > > Replaced memory, controllers, video cards, even disks. Loaded > > Virus NT a couple of weeks back and saw the darndest thing. You > > could wiggle the mouse pointer over an icon and it would smudge > > as if it were wet paint while Xwindows was unaffected. Found out that it > > would go away if I turned off the internal cache on the CPU. The reboots > > ceased -- defective CPU. My MB is a Tyan 1570. > > This is on a 486DX/4-100, no L2 cache, sufficient stepping that the > L1 cache should be OK, but I have tried it with the L1 cache > disabled (had to hack a control register in locore.s to do it), > with the same effect. > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 06:35:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12719 for freebsd-current-outgoing; Wed, 18 Nov 1998 06:35:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bashful.realminfo.com (bashful.realminfo.com [208.205.6.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12713 for ; Wed, 18 Nov 1998 06:35:30 -0800 (PST) (envelope-from smyth@bashful.realminfo.com) Received: from localhost (smyth@localhost) by bashful.realminfo.com (8.8.7/8.8.7) with SMTP id KAA16821 for ; Wed, 18 Nov 1998 10:50:12 -0500 Date: Wed, 18 Nov 1998 10:50:12 -0500 (EST) From: Scott Smyth To: FreeBSD Current Mailing List Subject: can't find libnet.so.0.93 for perl stuff Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a couple occasions I have had the error: "can't find libnet.so.0.92" for doing any perl stuff, which is part of kernel build too. It goes away depending on what day I download and build the FreeBSD-3.0 sources. The last day I downloaded was 11/15 and rebuilt the system only to have this error again. Has anybody else seen this or is this a very isolated error that I can fix. Thanks, Scott -- Scott Smyth, Senior Developer R&D (770) 446-1332 ssmyth@realminfo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 07:03:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16160 for freebsd-current-outgoing; Wed, 18 Nov 1998 07:03:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16088 for ; Wed, 18 Nov 1998 07:02:45 -0800 (PST) (envelope-from grg@philol.msu.ru) Received: from localhost (grg@localhost) by isabase.philol.msu.ru (8.9.1/8.9.1) with ESMTP id SAA11519; Wed, 18 Nov 1998 18:00:30 +0300 (MSK) (envelope-from grg@philol.msu.ru) X-Authentication-Warning: isabase.philol.msu.ru: grg owned process doing -bs Date: Wed, 18 Nov 1998 18:00:30 +0300 (MSK) From: Grigoriy Strokin To: Jos Backus cc: current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? In-Reply-To: <19981118135413.C3308@hal.mpn.cp.philips.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Jos Backus wrote: > On Wed, Nov 18, 1998 at 02:35:03PM +0300, Grigoriy Strokin wrote: > > For example, I'd like to restart inetd in my FreeBSD current every time it > > dies 1-4 times per week :) > > In that case, you may find http://pobox.com/~djb/daemontools.html to be of > interest. Thanks, I'll check it out! Grigoriy. === Grigoriy Strokin, Lomonosov University (MGU), Moscow === === contact info: http://isabase.philol.msu.ru/~grg/ === To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 08:10:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24459 for freebsd-current-outgoing; Wed, 18 Nov 1998 08:10:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24454 for ; Wed, 18 Nov 1998 08:10:35 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA28319; Wed, 18 Nov 1998 11:09:52 -0500 (EST) Date: Wed, 18 Nov 1998 11:09:52 -0500 (EST) From: "Matthew N. Dodd" To: Bruce Evans cc: current@FreeBSD.ORG Subject: Re: /dev/ioport[bwl] In-Reply-To: <199811180954.UAA24723@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Bruce Evans wrote: > Opening /dev/io gives direct access to i/o instructions. As I discovered. It appears to work rather well. > This is much easier and just as (in)secure as /dev/ioport would be. > Drivers should probably be prototyped using modules. Well, I"m just prototyping the PIO routines which don't need to be tested in-kernel. (Stuff like reading status registers and MAC addresses and such.) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 08:22:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25570 for freebsd-current-outgoing; Wed, 18 Nov 1998 08:22:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25508 for ; Wed, 18 Nov 1998 08:22:20 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:LMIUXfD7db+d80yaSSuuzREKCinuy+7D@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id SAA17463; Wed, 18 Nov 1998 18:21:37 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:KNuG3llqnylcXrq9jALMjZchTuCo9gIj@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id SAA27118; Wed, 18 Nov 1998 18:21:36 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811181621.SAA27118@greenpeace.grondar.za> To: Scott Smyth cc: FreeBSD Current Mailing List Subject: Re: can't find libnet.so.0.93 for perl stuff In-Reply-To: Your message of " Wed, 18 Nov 1998 10:50:12 EST." References: Date: Wed, 18 Nov 1998 18:21:34 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Smyth wrote: > On a couple occasions I have had the error: > "can't find libnet.so.0.92" for doing any perl stuff, which is > part of kernel build too. It goes away depending on what day I > download and build the FreeBSD-3.0 sources. The last day I > downloaded was 11/15 and rebuilt the system only to have this > error again. Sounds like you have an (old, broken) perl port. Delete the perl port and let 3.0's _system_ perl do the job. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 09:01:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01040 for freebsd-current-outgoing; Wed, 18 Nov 1998 09:01:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01034 for ; Wed, 18 Nov 1998 09:01:38 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id JAA29034; Wed, 18 Nov 1998 09:00:49 -0800 (PST) Date: Wed, 18 Nov 1998 09:02:12 -0800 (PST) From: Tom Bartol To: Doug Rabson cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Doug Rabson wrote: > On Tue, 17 Nov 1998, Tom Bartol wrote: > > > > > Hi all, > > > > I've been seeing the following problem for a while now (since > > 3.0-19981006-BETA) but was too busy at the time to report it or help > > diagnose it further. Now I've got some time on my hands... > > > > I can fairly consistently wedge NFS writes to our server with the > > following: > > > > dd if=/dev/zero of=ick bs=8192 count=1000 > > > > which tries to write an 8MB file to our file server which is an Auspex. I > > have mounted Auspex from my 3.0-current machine (cvsupped and built this > > morning) in NFSv3 mode. This command will wedge one or more of the nfsiod > > processes. "ps -auwx | grep nfsiod" reports the following: > > > > root 137 0.0 0.0 216 64 ?? I 9:12AM 0:02.31 nfsiod -n 4 > > root 138 0.0 0.0 216 64 ?? I 9:12AM 0:01.74 nfsiod -n 4 > > root 139 0.0 0.0 216 64 ?? D 9:12AM 0:00.27 nfsiod -n 4 > > root 140 0.0 0.0 216 64 ?? D 9:12AM 0:00.24 nfsiod -n 4 > > > > The two processes in state "D" are the wedged ones. A separate machine > > running -current from July 11 works fine. > > > > Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS > > reads work fine. > > > > Is anyone else seeing similar behaviour? What can I do to try to fine > > tune a diagnosis and help solve the problem? > > > > Thanks for your help, > > The best place to start is to get a tcpdump of the set of transactions > which wedged the iod. > > -- Thanks for the tip. I'll start there and report back when I've got something interesting... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 10:04:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11525 for freebsd-current-outgoing; Wed, 18 Nov 1998 10:04:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (tex-107.camalott.com [208.229.74.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11511 for ; Wed, 18 Nov 1998 10:04:45 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id MAA00465; Wed, 18 Nov 1998 12:03:41 -0600 (CST) (envelope-from joelh@gnu.org) Date: Wed, 18 Nov 1998 12:03:41 -0600 (CST) Message-Id: <199811181803.MAA00465@detlev.UUCP> X-Authentication-Warning: detlev.UUCP: joelh set sender to joelh@gnu.org using -f To: freebsd-current@FreeBSD.ORG Subject: KGDB with aout From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do we have any way to do post-mortem kernel debugging of an a.out kernel, or do I need to bite the bullet and go to an ELF kernel? Are there any current caveats about an ELF kernel (or, since I haven't cvsup'd in two weeks, and we seem to be having some -current problems right now, any caveats from about 4 Nov)? Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 10:46:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18088 for freebsd-current-outgoing; Wed, 18 Nov 1998 10:46:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18075 for ; Wed, 18 Nov 1998 10:46:35 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA06273; Wed, 18 Nov 1998 10:45:16 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 18 Nov 1998 10:45:15 -0800 (PST) From: Doug White To: Ben Hutchinson cc: Garrett Wollman , freebsd-current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? In-Reply-To: <19981118014446.C15587@xfiles.org.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Ben Hutchinson wrote: > In which case how about implementing something a little more sysv-ish for > only ports? > > Ie, a rough idea: > > /usr/local/etc/rcS.d for startup scripts I strongly oppose this; rc.d already exists and is standardized in several releases. Such a change would be gratuitous. > /usr/local/etc/rcK.d for shutdown scripts rc.shutdown.d would be a self-documenting name. rcK.d doesn't mean anything to me. (K=kill?? I don't come from a Solaris background.) > Would this provide sufficient granularity? It would save people from hacking /etc/rc.shutdown (like rc.d saves hacking /etc/rc.local). Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 10:46:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18106 for freebsd-current-outgoing; Wed, 18 Nov 1998 10:46:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18089 for ; Wed, 18 Nov 1998 10:46:44 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA06302; Wed, 18 Nov 1998 10:46:04 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 18 Nov 1998 10:46:03 -0800 (PST) From: Doug White To: Marc van Woerkom cc: freebsd-current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <199811180053.BAA03207@oranje.my.domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Marc van Woerkom wrote: > What does this message > > ===> netscape-communicator-4.5 is marked as broken: PLIST. > > mean, exactly? The packing list for the port is out of date, and the port is marked BROKEN until the maintainer regenerates the packing list (PLIST). Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 10:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18257 for freebsd-current-outgoing; Wed, 18 Nov 1998 10:48:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18205 for ; Wed, 18 Nov 1998 10:48:01 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA06641; Wed, 18 Nov 1998 10:47:29 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 18 Nov 1998 10:47:29 -0800 (PST) From: Doug White To: William Woods cc: FreeBsd-Current Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 17 Nov 1998, William Woods wrote: > Date: Tue, 17 Nov 1998 17:08:33 -0800 (PST) > From: William Woods > To: FreeBsd-Questions > Subject: StarOffice 5.0 > > Rumor has it that there are people who have gotten StarOffice 5.0 to run on an > aout system. Please let me know how.... > Yeah, I'd like to steal their LinuxThreads library, which is what we're missing at the moment .. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 10:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18377 for freebsd-current-outgoing; Wed, 18 Nov 1998 10:49:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18359 for ; Wed, 18 Nov 1998 10:49:20 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA07314; Wed, 18 Nov 1998 10:48:41 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 18 Nov 1998 10:48:40 -0800 (PST) From: Doug White To: Jason George cc: "'freebsd-current@freebsd.org'" Subject: Re: Issue with Bad Block scan on fresh disk In-Reply-To: <01BE128F.CD600D40@infomat> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Jason George wrote: > I was building two new 3.0 boxes when I stumbled upon a little nuance > with the bad block scan within the initial sysinstall. I was > wondering if anyone else had noticed this or had any suggestions. The bad block scan is useless for IDE and SCSI drives. If it finds anything return the drive and get a replacement... Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 11:17:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA22354 for freebsd-current-outgoing; Wed, 18 Nov 1998 11:17:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lonegunman.xfiles.org.uk (lonegunman.xfiles.org.uk [194.200.230.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA22341 for ; Wed, 18 Nov 1998 11:17:16 -0800 (PST) (envelope-from benhutch@lonegunman.xfiles.org.uk) Received: (from benhutch@localhost) by lonegunman.xfiles.org.uk (8.9.1/8.9.1) id TAA18140; Wed, 18 Nov 1998 19:16:28 GMT (envelope-from benhutch) Message-ID: <19981118191628.A18022@xfiles.org.uk> Date: Wed, 18 Nov 1998 19:16:28 +0000 From: Ben Hutchinson To: Doug White Cc: freebsd-current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? References: <19981118014446.C15587@xfiles.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Doug White on Wed, Nov 18, 1998 at 10:45:15AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 18, 1998 at 10:45:15AM -0800, Doug White wrote: > I strongly oppose this; rc.d already exists and is standardized in several > releases. Such a change would be gratuitous. I wasn't suggesting that rc.d be ditched, merely that another option be provided if a port wished to make use of it. > > rc.shutdown.d would be a self-documenting name. rcK.d doesn't mean > anything to me. (K=kill?? I don't come from a Solaris background.) Yep, Knnscriptname generally means "this is a shutdown script, invoke me as scriptname stop". rc.shutdown.d would be fine, the examples I provided were merely a rough idea. > > It would save people from hacking /etc/rc.shutdown (like rc.d saves > hacking /etc/rc.local). Which is why it would (IMHO) be a good idea. - Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 11:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27598 for freebsd-current-outgoing; Wed, 18 Nov 1998 11:53:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27581 for ; Wed, 18 Nov 1998 11:53:13 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id UAA07496; Wed, 18 Nov 1998 20:52:29 +0100 (CET) Message-ID: <19981118205229.A7476@foobar.franken.de> Date: Wed, 18 Nov 1998 20:52:29 +0100 From: Harold Gutch To: joelh@gnu.org, freebsd-current@FreeBSD.ORG Subject: Re: KGDB with aout References: <199811181803.MAA00465@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811181803.MAA00465@detlev.UUCP>; from Joel Ray Holveck on Wed, Nov 18, 1998 at 12:03:41PM -0600 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 18, 1998 at 12:03:41PM -0600, Joel Ray Holveck wrote: > Do we have any way to do post-mortem kernel debugging of an a.out > kernel, or do I need to bite the bullet and go to an ELF kernel? You need an a.out gdb, for example from an a.out system you still have somewhere - or from ftp://ftp.lemis.com/pub/vinum/gdb-aout. -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 11:56:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27949 for freebsd-current-outgoing; Wed, 18 Nov 1998 11:56:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27929; Wed, 18 Nov 1998 11:56:49 -0800 (PST) (envelope-from mi@video-collage.com) X-Relay-IP:   Received: (from mi@localhost) by xxx.video-collage.com (8.9.1a/8.9.1) id OAA09226; Wed, 18 Nov 1998 14:56:17 -0500 (EST) Message-Id: <199811181956.OAA09226@xxx.video-collage.com> Subject: communicator-4.5 port (was: Re: your mail) In-Reply-To: from Doug White at "Nov 18, 1998 10:46: 3 am" To: current@FreeBSD.ORG Date: Wed, 18 Nov 1998 14:56:17 -0500 (EST) Cc: thepish@FreeBSD.ORG From: Mikhail Teterin X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" What does this message => => ===> netscape-communicator-4.5 is marked as broken: PLIST. => => mean, exactly? = =The packing list for the port is out of date, and the port is marked =BROKEN until the maintainer regenerates the packing list (PLIST). So, why is it not BROKEN= "packing list is out of date (pkg/PLIST)" then? Too long?! :-< -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 11:58:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28159 for freebsd-current-outgoing; Wed, 18 Nov 1998 11:58:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28153 for ; Wed, 18 Nov 1998 11:58:55 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from cybcon.com (wwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id LAA01434; Wed, 18 Nov 1998 11:58:26 -0800 (PST) Date: Wed, 18 Nov 1998 11:58:26 -0800 (PST) From: Bill Woods To: Doug White cc: FreeBsd-Current Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG any idea when this may be possible? Untill then, do you know where I could grab a copy of Star Office 4.0 that works on FreeBSD ? On Wed, 18 Nov 1998, Doug White wrote: > On Tue, 17 Nov 1998, William Woods wrote: > > > Date: Tue, 17 Nov 1998 17:08:33 -0800 (PST) > > From: William Woods > > To: FreeBsd-Questions > > Subject: StarOffice 5.0 > > > > Rumor has it that there are people who have gotten StarOffice 5.0 to run on an > > aout system. Please let me know how.... > > > > Yeah, I'd like to steal their LinuxThreads library, which is what we're > missing at the moment .. > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 12:29:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02148 for freebsd-current-outgoing; Wed, 18 Nov 1998 12:29:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02108; Wed, 18 Nov 1998 12:29:41 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id MAA27868; Wed, 18 Nov 1998 12:29:06 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Wed, 18 Nov 1998 12:29:05 -0800 (PST) From: Doug White To: Bill Woods cc: questions@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: StatrOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Bill Woods wrote: > I remember reading somewhere on this list(s) there there was work on > getting StarOffice 5.0 to run on FreeBSD. > > I am currently running FreeBSD 3.0 -current, cvsupped and compiled last > night. What is the status of getting this working/ Someone mentioned on > irc last night that it has been successfull? Someone fill me in here, as I > have herd good things about this program Still nothing yet, stay tuned. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 13:07:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06564 for freebsd-current-outgoing; Wed, 18 Nov 1998 13:07:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA06528 for ; Wed, 18 Nov 1998 13:07:26 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id PAA13507; Wed, 18 Nov 1998 15:06:42 -0600 (CST) Date: Wed, 18 Nov 1998 15:06:41 -0600 From: Dan Nelson To: Harold Gutch , joelh@gnu.org, freebsd-current@FreeBSD.ORG Subject: Re: KGDB with aout Message-ID: <19981118150641.A13349@emsphone.com> References: <199811181803.MAA00465@detlev.UUCP> <19981118205229.A7476@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <19981118205229.A7476@foobar.franken.de>; from "Harold Gutch" on Wed Nov 18 20:52:29 GMT 1998 X-OS: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 18), Harold Gutch said: > On Wed, Nov 18, 1998 at 12:03:41PM -0600, Joel Ray Holveck wrote: > > Do we have any way to do post-mortem kernel debugging of an a.out > > kernel, or do I need to bite the bullet and go to an ELF kernel? > > You need an a.out gdb, for example from an a.out system you still > have somewhere - or from ftp://ftp.lemis.com/pub/vinum/gdb-aout. revision 1.11 date: 1998/10/15 00:19:08; author: peter; state: Exp; lines: +3 -1 Add objformat links for gdb and (while we're at it) c++filt. This means we can (assuming an a.out gdb is present) debug a.out kernels and crashdumps with gdb -aout. Just running: gdb -aout -k kernel.0 vmcore.0 should work (works for me). And if you don't have an a.out gdb, you should be able to build one via "OBJFORMAT=aout ; make clean && make all install" in the gdb source dir. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 13:29:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10170 for freebsd-current-outgoing; Wed, 18 Nov 1998 13:29:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lonegunman.xfiles.org.uk (lonegunman.xfiles.org.uk [194.200.230.242]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10135; Wed, 18 Nov 1998 13:29:25 -0800 (PST) (envelope-from benhutch@lonegunman.xfiles.org.uk) Received: (from benhutch@localhost) by lonegunman.xfiles.org.uk (8.9.1/8.9.1) id VAA18477; Wed, 18 Nov 1998 21:28:48 GMT (envelope-from benhutch) Message-ID: <19981118212848.C18407@xfiles.org.uk> Date: Wed, 18 Nov 1998 21:28:48 +0000 From: Ben Hutchinson To: Mikhail Teterin , freebsd-current@FreeBSD.ORG Cc: thepish@FreeBSD.ORG Subject: Re: communicator-4.5 port (was: Re: your mail) References: <199811181956.OAA09226@xxx.video-collage.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811181956.OAA09226@xxx.video-collage.com>; from Mikhail Teterin on Wed, Nov 18, 1998 at 02:56:17PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Somebody was hacking late, and wanted to be brief so they could get to bed? It's an accurate, if somewhat brief description which means "The packaging list is broken". If it bothers you that much, fix it, and send-pr the changes. - Ben On Wed, Nov 18, 1998 at 02:56:17PM -0500, Mikhail Teterin wrote: > So, why is it not > > BROKEN= "packing list is out of date (pkg/PLIST)" > > then? Too long?! :-< > -- "You Can't Handle The Truth" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 13:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11215 for freebsd-current-outgoing; Wed, 18 Nov 1998 13:35:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11201 for ; Wed, 18 Nov 1998 13:35:23 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id PAA00503; Wed, 18 Nov 1998 15:34:50 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199811182134.PAA00503@ns.tar.com> From: "Richard Seaman, Jr." To: "Brian Feldman" Cc: "current@freebsd.org" Date: Wed, 18 Nov 98 15:34:50 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=_=_=IMA.BOUNDARY.F2MX61138764=_=_=_" Subject: Re: RFSIGSHARE ready? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --_=_=_=IMA.BOUNDARY.F2MX61138764=_=_=_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit On Thu, 12 Nov 1998 22:06:52 -0500 (EST), Brian Feldman wrote: >Would you mind actually trying moving the signal masks out of struct >procsig then? It would be easy, but I don't have time to be testing new >kernels, I've attached some patches, which represent changes to your patches, to implement shared signal handling. These seem to be sufficient to get LinuxThreads working in FreeBSD "native" with full signal handling. However, I've only tried a few test programs. I recognise that this is not the same as having LinuxThreads working in emulation, which is your goal. I have no idea if these patches will accomplish your goal, but they might move you closer. I've also modified your patches to the linux emulation to mirror what I have done in the FreeBSD native case. I haven't even tried these (in linux emulation) so I don't know if they help or hinder. I'll also renew my offer to send you the modifications I've made to LinuxThreads to get it running in FreeBSD "native", as these might be a guide to your work on getting the emulation mode working. --_=_=_=IMA.BOUNDARY.F2MX61138764=_=_=_ Content-Type: application/octet-stream; name="kern.diffs.gz" Content-Transfer-Encoding: base64 H4sICByqUTYAA2tlcm4uZGlmZnMAzRprc9pI8rP8KyabWi84MugFCBN7y2s7iWv9quBs9m5vi5Kl AbQGSSUJYl+S++3XPTOSRkJgJ6l1ljIPa3r63T3dLZ0GHr3bIzd+0I6S9i29/xDGXsvd2v/219bb oyEZ+zO6R9rTcE7bgbtM2knstqvU1OVWTNPYp0s/mJAYvhI/DIjeMrQtzx+PyW6Mv0nBnt7pO3pX 2zog7R3yO7xIQKmXALk7QLGld01Y7sDyTnvrlIuY3Cdt37S77ZkfLO74Z2v69wpaT3O9uJYkrkUy Fi1DcyxDB2mee3TsB5ScnV68+310fng1ev328v3w+PL9BcGXdqfpmrZJ4pG3mM/v/24Db6K8Vnq7 EN4mZWYNvaMahu4ZurX1Uqy5szCgjSSNF25Kojh0yU6kEvG/BDJy4klCdvCzCZs/whtfUewH6bjx wxlC7tL5Ytb40WvuEY62SYIwJckiisI4pd5/gh9UEu0eRKPI95oDgQLEWMQBObm4HP5riBc/wxv+ APFGE8z9xP0uFuCE1xrA6hQWsDqkxKxlOpaFHugH7mzhUfISKSwCP0m91vRgq9M1nE7XUru6Ifnp 0dnlxcnot3NFu0O/rC68GsKCUbdwenaCa1bN2vD09ZvDi2NYtWtWr06POTFcgj+0xcG3eMwBeMwB MzegIjSOw1gloKR98vbV1dvLI5WkYTQQIGXcxoDz8NwfA49keH4lwDLfk9lizueFNGGeB2nulnzw 0ynuqnrfgex9jZPLq4vL6+G7qyu29JzOEloQPT755d3rEdNNJsaYNFC03YPxzAE5twvNobTKWuZy MMbhPd0QH5spvRo+htCr4WPoPKcB+OwDBH87ZwTBap/QbOcn5w+xKJystA2uDd8cvj2R9z6rFxDd t1na/Or4tbyP+RH40BjsrDci9CgOL6zK1rMNkQGQETi512CyA8zSmf2h/VnSNELtE03GcjJ8e/Rm VdQkddzbJvNrxQ2jez+QF1SyDR6tEothVyIDSc691twDwgiVjkc0iYClBtivKe3cAO8jvBQokCrF Dw6f+JPIiSlE2D4paxSONPYajwebvHpVDvKCWGVZ1oTeHgFnSsiPngrvAXGn/swjwPH+j8/vVAKi 8h874hf6IBNUuKEqRJB+rkq/biWJGC5gctWbhRG10gLqbaurddSu1nW7Hfju2eI4ukk8lrlajueh b3ER8yuDKtiMBmUouDDY2t3d5VkLX1lxldI5BKAT35MpajYNSQq/4WtCReYk6TSmDqgRMxecKy1C 3tPMxoT8tUggqTn3JFzS2A3ncz8lSz9OF86MzOk85NjSKSXzuRNRD4Sf4KH0Yeq70wKNn5AbiqfW IgEYJyGOoEuYyYHo9RRg5kAIcwddgogslfpBgSSBg5K4TgKpNoHTjBJnNmNoKAnHyEMCy2EAGIM0 AcAAaBIXBAjnEhIQ3A8Yx+C4qe8uZk5cUYU/j2Z0Dk7tpCBLq1ArvA4BaZrSGLiZLXAZZWMnmZPS 2T0rZyk41M0ixcj9gBwHP6Wo8AJJreZVFB84hi2IBDfdhMBn3BIboSQuTs3h9eHRr5Du/n1CSMMg O0TXoPLkX00J7vTi9Pr08GxUgkfAq8PXJ+z/ppRnJKfK4rimZG3mR+sj3JfskoZEfLeGI56wSv69 4uAE0sLj8GS+7wRMezUxEMXoYCk4IxnH4Zy5boTeCSkmRBQgFXMQKAdokmQ+erbwJz45mgIzkNJ9 FwyeAJzwW7BcCDl4Gn4A5MxmCjOYUtEr08mLqnQH/HRczpPIcenuwXI+mjt3CQI3BUdF4XB68dvh WZ4ZPxOsHL7EJKvqXk0nAveW3TGcvoEdGfzswM++2jc7lTTDa+6YFh7PEszNPSuFQggFVOdo9J5l fhJGLHDgDF0TEnL4zKizBMQsaj84fmoBToj7iQ9XwYCOlCD44czVpIocgS5AMUaDEJJDHEPmDsF4 YOxXkDh+GR4LbmqDLOeY1azsJQVLOo9afDPGSQbblOxQgtgn/8tgBhvbDHC7NPweHW5GeW2joZtF o6GbpMxux+3gSbVDXLAh1HwstpRTj0npQq5OWnMngdSpLhGVTvR+325r3bbWJ5q5Z9h7ukVuoEM5 uYuIOM4ejc0Q2HptXSOGsWdqe5pN/rqdcmymZrnwVk0NeVTwkMK9o5SwTjU7PRVIAApLfAPFncK5 wH6P/rg6PB6xoulPFjrL0PfIjsJrJw7IfgtAvoywm6wsxPguds5pr7V0vzB0n1QZ/idb+gGVQ9r/ Lh18Rnp9aEkjJN0iFYb/yRrXzZ4Lb4yrj0RTSSO5HyESCK6dplSuk8+qgoezbmj5ecMXIOeK+PtI jK9EUG/3ijxPavgVXa6zvCFZ3qiaYEvvWS68Qb0gtzK8PlZYRQaqwrmG3INj3mkO4MzmynwIHP9n +U0lPGPx9hIRSMq8pXHQ9ucTx01HdDZ+iuBZIbl+8CWpzjJIiU2703PhjW4JgqWLpBXFI3cRQ8eK XbloXgEeOroowd/5KbAGXgCtKCfwUyjW/ODpdFNQXJ/A5QzeJzKTdsexuyAnium78uwLZRXf0L1a es+x9L5qGYaoq49YvshAWrxYUjJdgpq2i93SAtNdTMcuGxPw6ZrVtVSr23GtLhDoaWgmSEjvWQeX gpdSVqjPoBgGqZJwEbtY7jkTqOWCcQhlH7SO/iRwZmInGJKVWaK3gz4zziRLWIN6/1OMLd+EOjcz 2spM/SU0a1ELJH76UyJht7q2a/VMkAwDV5G9jWkJ/8dKfPdgkV2XOvh6+EyROXzVEfFjRO/8Jznh qhTXOmJXcsRun8hM6rbl6bYpawhMGoKdoFYGFzK1PlRtOCZhTRQf3ERpjN+YuaDqvhpdXB6dHb8/ PL3GrjQr46rQme7qd5mG7pqGppoGtxZ3rAKDSoanr4/enB03BysUigHY9jYp0Ywgpz7bJ7oY2GU9 QQ32MiLexUpd3aatBWO4ByTpOqbJRuiW3XesPgQZZALuVQrjene3NixxAsmpKTm9MXRIuZQqOR9d n5zzYTUAyWF/8e7srHpZ+K60tHquMGfAUerTeiynuNZjO9Kp0jGIzKRp9BzTsFXTMjMvyOYkxZw5 02M+IZUU/eLFinULOFDXHI7+0G0k/n9pOG6UU3MzMwF+o+9e/iqMUUcJkOl1q1GY+Hc4X+E5WrnB CWxjO9JloBtokAJcUCH5GPUr3KiNRYBeSb1mBQUNPAQjuw/A5QgzH17RKytgrt9cXVQjaWUCbWoF jnw1T6IlOfIsysg1JHLXb96eHB43MXY1DGpp6epyePo7mJkvNmuZkZTMLFDr83h6PqnLM4Lr6ygp R1siR3MWddOG4p6lYGYVtOFijulCZJ487ZVT6/D68qqZJcsHdtYnZ45BtzQX3l9Mn6X2b6LPMeh9 kL/P5VcKOp/2ZTbzU0FRVhFWQQ1Nc/HWaQUjjocei3IF1oCDEt4cZz1SFEdCuhkrBzZ03YX3CtZC ooeRVmEN3QSc5gbpKzgfwadp2y68v5uPikIPCz5ePjDIcOZBB3cr9Rr470CC4HkFNDQ8HI4uz47P D4e/5pJHG5H0TFPtmZbbMw345uoUWN3Qw/oJvwZiFo6TVhx+Upx2RW2P3iwmEyhioXyXNvIDiKsg 3wkF8ZLG/vieIZQ6dcHgl1Er9j2SWM823Z5t5KatlInbBNVRtuEaGPLpk9iem/D9ye8Q4s0tG9oQ u2txnyxQ1FeazOTihm3upKubNviL2KxrPcOFjyy+vorw11HWrZ4KH5DZdKuLv1iXzI4ybhFVtFNQ msquui17Kvk531Tx+L2Ss6pAsojnWhql3T/ncNGDWHW9h5L0+iBJDyXpFVlgPedN9iwRKI/fKcgC rCTEQGSoEhJIPHWhmntmvjuvpMsUygTy9CaHuYZC9TsgT9+qioIx8ywLGqnbkeivgAAeW9XxzIFf qKu+OCVE4EpJoyyyWNfKV3nYalJ+zvBIaCTBCizSxRyJbpggqWFySetGMkWOqOSd8ppUY+Eb6+Wn mKsXtNZ3v1Iv0TWI4MzqOx32CFTpoSze3S2dGJ/LsjXHNtS+weY02AUo2YDmo3SDSq6fCVcLT3ts jOVPEpqO0tICS7ZDRim7J88XvGycU9nmOqk7rdnlOovJlN3jw4GI2Jzf74dyXLSsLHgGfKzG5CBZ TV6uwiWRstYh72WyWzPFlcEaYqzwxsXPbMqkd7sOpAdVt40Mh9QxDNg4maudjX54HwGGwwFFjTqy 2OX7nCX12OHC7yLf0DGeNww7qERsZyT55FBh29acjnj+8R2L0SwMJkoWTo/YpONJwgogoUQUMnXi FLWo5DlThNBaGMBjOnpfU3XmdkrF73YiPv+UTCUds6XOKvfBEiTzpDIguwR0Oypkck/vs0qm0Pij 3XZl1xd47UtSzR9SID5NEpEIPvaRapnHju2JQfc3+GpXV7uG12HHwxc67cuvcdqKzrMnUp9G4Rm1 9TdletJNmR7JuYMwc3QbEkpffqy7mP0oDf3lS91qMqVPHa5jTC9TJ/BmNE7KDxgUIwWewdjuThMf rHh3cXp+dUb4JCF7WIrj8ujMh0L5voorH5QUuLoMlxeK5yv47TKW3USyC8LUH+OzLCh3jVkwSp7K KIzWepN0JZN0ieBM1zqerln8Ng/LV9nxUkzW0RjFKCgKfXw+jD0X0kDn99NnTZZGTUh9pg4VCdjX 1KR0+g43KznCFo+NEgC6fRkCr1RSbobnltUBt9GIfQtsB6vYVuAYTslEyzn8jSazBX2KcZJMba2Z elLk9HqkYM+AnhVqPVd8i/s27BRKE3ZDp7CRu4jRO2f33FrESYErOvPq7u8IRPjEED6HBKDbCxXg khRDxsEDAW+1tMgRqylyGowiHIAJCcfS7aCMoQoLyWYeDr6Ih4yqYdqgir5n8NvnKyPLRVS6QYR5 Vr4CIDv5MJWD/B84sOAsFzQAAA== --_=_=_=IMA.BOUNDARY.F2MX61138764=_=_=_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 13:47:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12950 for freebsd-current-outgoing; Wed, 18 Nov 1998 13:47:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12942 for ; Wed, 18 Nov 1998 13:47:50 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id NAA08246; Wed, 18 Nov 1998 13:47:22 -0800 (PST) Date: Wed, 18 Nov 1998 13:47:22 -0800 (PST) From: Tom Bartol To: Doug Rabson cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Doug Rabson wrote: > On Tue, 17 Nov 1998, Tom Bartol wrote: > > > > > Hi all, > > > > I've been seeing the following problem for a while now (since > > 3.0-19981006-BETA) but was too busy at the time to report it or help > > diagnose it further. Now I've got some time on my hands... > > > > I can fairly consistently wedge NFS writes to our server with the > > following: > > > > dd if=/dev/zero of=ick bs=8192 count=1000 > > > > which tries to write an 8MB file to our file server which is an Auspex. I > > have mounted Auspex from my 3.0-current machine (cvsupped and built this > > morning) in NFSv3 mode. This command will wedge one or more of the nfsiod > > processes. "ps -auwx | grep nfsiod" reports the following: > > > > root 137 0.0 0.0 216 64 ?? I 9:12AM 0:02.31 nfsiod -n 4 > > root 138 0.0 0.0 216 64 ?? I 9:12AM 0:01.74 nfsiod -n 4 > > root 139 0.0 0.0 216 64 ?? D 9:12AM 0:00.27 nfsiod -n 4 > > root 140 0.0 0.0 216 64 ?? D 9:12AM 0:00.24 nfsiod -n 4 > > > > The two processes in state "D" are the wedged ones. A separate machine > > running -current from July 11 works fine. > > > > Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS > > reads work fine. > > > > Is anyone else seeing similar behaviour? What can I do to try to fine > > tune a diagnosis and help solve the problem? > > > > Thanks for your help, > > The best place to start is to get a tcpdump of the set of transactions > which wedged the iod. > O.K. I've got a tcpdump of nfs traffic during a successful dd of 800KB and during a dd of 1600KB which resulted in a wedged nfsiod process. I'm not sure what to look for in the output. I don't see any obvious problems or major differences between the success and the failure, but then I'm not an expert at reading tcpdump output. Here is the command I used to capture the data: tcpdump -s 192 -vv >& nfs_traffic Which should see everything on my segment. We have switched 100BT to the desktop here and I have my own private port on the switch so my wire is pretty quite (except for the occasional broadcast). The traffic I captured contains only a few non-nfs tidbits. So, should I post my output for some helpful expert to take a look at? I'd sure like to see this problem fixed in -current... Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 14:06:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15204 for freebsd-current-outgoing; Wed, 18 Nov 1998 14:06:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15197 for ; Wed, 18 Nov 1998 14:06:25 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id NAA08322; Wed, 18 Nov 1998 13:50:26 -0800 (PST) Date: Wed, 18 Nov 1998 13:50:26 -0800 (PST) From: Tom Bartol To: Doug Rabson cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Doug Rabson wrote: > On Tue, 17 Nov 1998, Tom Bartol wrote: > > > > > Hi all, > > > > I've been seeing the following problem for a while now (since > > 3.0-19981006-BETA) but was too busy at the time to report it or help > > diagnose it further. Now I've got some time on my hands... > > > > I can fairly consistently wedge NFS writes to our server with the > > following: > > > > dd if=/dev/zero of=ick bs=8192 count=1000 > > > > which tries to write an 8MB file to our file server which is an Auspex. I > > have mounted Auspex from my 3.0-current machine (cvsupped and built this > > morning) in NFSv3 mode. This command will wedge one or more of the nfsiod > > processes. "ps -auwx | grep nfsiod" reports the following: > > > > root 137 0.0 0.0 216 64 ?? I 9:12AM 0:02.31 nfsiod -n 4 > > root 138 0.0 0.0 216 64 ?? I 9:12AM 0:01.74 nfsiod -n 4 > > root 139 0.0 0.0 216 64 ?? D 9:12AM 0:00.27 nfsiod -n 4 > > root 140 0.0 0.0 216 64 ?? D 9:12AM 0:00.24 nfsiod -n 4 > > > > The two processes in state "D" are the wedged ones. A separate machine > > running -current from July 11 works fine. > > > > Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS > > reads work fine. > > > > Is anyone else seeing similar behaviour? What can I do to try to fine > > tune a diagnosis and help solve the problem? > > > > Thanks for your help, > > The best place to start is to get a tcpdump of the set of transactions > which wedged the iod. > > -- Oh, I should add that top reports that the wedged nfsiod process is in state "sbwait" and never returns to state "nfsidl" Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 14:14:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16733 for freebsd-current-outgoing; Wed, 18 Nov 1998 14:14:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16723 for ; Wed, 18 Nov 1998 14:14:04 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id PAA04092; Wed, 18 Nov 1998 15:13:16 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id PAA00479; Wed, 18 Nov 1998 15:13:14 -0700 Date: Wed, 18 Nov 1998 15:13:14 -0700 Message-Id: <199811182213.PAA00479@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Richard Seaman, Jr." Cc: "Brian Feldman" , "current@freebsd.org" Subject: Re: RFSIGSHARE ready? In-Reply-To: <199811182134.PAA00503@ns.tar.com> References: <199811182134.PAA00503@ns.tar.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Would you mind actually trying moving the signal masks out of struct > >procsig then? It would be easy, but I don't have time to be testing new > >kernels, > > I've attached some patches, which represent changes to your patches, > to implement shared signal handling. > > These seem to be sufficient to get LinuxThreads working in FreeBSD > "native" with full signal handling. However, I've only tried a > few test programs. Cool. I haven't been able to help out, but I appreciate the work you and Brian have been doing to hash this out! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 14:48:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22571 for freebsd-current-outgoing; Wed, 18 Nov 1998 14:48:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22561 for ; Wed, 18 Nov 1998 14:48:05 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id OAA10154; Wed, 18 Nov 1998 14:47:35 -0800 (PST) Date: Wed, 18 Nov 1998 14:47:36 -0800 (PST) From: Tom Bartol To: Doug Rabson cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS problems in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Doug Rabson wrote: > On Tue, 17 Nov 1998, Tom Bartol wrote: > > > > > Hi all, > > > > I've been seeing the following problem for a while now (since > > 3.0-19981006-BETA) but was too busy at the time to report it or help > > diagnose it further. Now I've got some time on my hands... > > > > I can fairly consistently wedge NFS writes to our server with the > > following: > > > > dd if=/dev/zero of=ick bs=8192 count=1000 > > > > which tries to write an 8MB file to our file server which is an Auspex. I > > have mounted Auspex from my 3.0-current machine (cvsupped and built this > > morning) in NFSv3 mode. This command will wedge one or more of the nfsiod > > processes. "ps -auwx | grep nfsiod" reports the following: > > > > root 137 0.0 0.0 216 64 ?? I 9:12AM 0:02.31 nfsiod -n 4 > > root 138 0.0 0.0 216 64 ?? I 9:12AM 0:01.74 nfsiod -n 4 > > root 139 0.0 0.0 216 64 ?? D 9:12AM 0:00.27 nfsiod -n 4 > > root 140 0.0 0.0 216 64 ?? D 9:12AM 0:00.24 nfsiod -n 4 > > > > The two processes in state "D" are the wedged ones. A separate machine > > running -current from July 11 works fine. > > > > Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS > > reads work fine. > > > > Is anyone else seeing similar behaviour? What can I do to try to fine > > tune a diagnosis and help solve the problem? > > > > Thanks for your help, > > The best place to start is to get a tcpdump of the set of transactions > which wedged the iod. > > -- I just had another nfsiod wedge in state "nfsrcv" while using Netscape. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 14:53:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23534 for freebsd-current-outgoing; Wed, 18 Nov 1998 14:53:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23526 for ; Wed, 18 Nov 1998 14:53:22 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id RAA20619; Wed, 18 Nov 1998 17:52:17 -0500 (EST) Date: Wed, 18 Nov 1998 17:52:17 -0500 (EST) Message-Id: <199811182252.RAA20619@highwind.com> From: HighWind Software Information To: lists@tar.com CC: green@unixhelp.org, current@FreeBSD.ORG In-reply-to: <199811182134.PAA00503@ns.tar.com> (lists@tar.com) Subject: Re: RFSIGSHARE ready? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a question with regard to LinuxThreads on FreeBSD 3.0 Is this a substitute for libc_r?? How does this fit into the picture? -Rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 15:26:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28533 for freebsd-current-outgoing; Wed, 18 Nov 1998 15:26:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28505 for ; Wed, 18 Nov 1998 15:26:19 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id SAA11435; Wed, 18 Nov 1998 18:25:44 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id SAA15088; Wed, 18 Nov 1998 18:25:38 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 18 Nov 1998 18:25:36 -0500 (EST) To: Robert Nordier CC: freebsd-current@FreeBSD.ORG Subject: /boot/loader & comconsole X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13907.20799.296610.678439@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm in the process of upgrading a cluster of (nearly identical) PII's to 3.0-CURRENT & am installing the new 3-stage bootstrap. On some of the machines, using a comconsole wedges the bootloader solid ( well, 2 ctrl-alt-deletes on the local keyboard will reboot the machine). My /boot.config looks like: /boot/loader -h And /boot/boot.conf looks like: set console=comconsole autoboot 3 I see the following on console before it hangs: >> FreeBSD BOOT @ 0x10000: 638/65532 k of memory, serial console Boot default: 0:da(0,a)/boot/loader Usage: bios_drive:interface(unit,partition)kernel_name options <..snip..> boot: Booting 0:da(0,a)/boot/loader @ 0x100000 text=0x1000 data=0x1a000 bss=0x0 symbols=[+0x0+0x4+0x0+0x4+0xff8c] Can't find file /boot/loader.config total=0x12af94 entry point=0x100000 And there it stops. If I don't set console=comconsole, everything works great. Here's what I see with the same bootstrap on another machine: boot: Booting 0:da(0,a)/boot/loader @ 0x100000 text=0x1000 data=0x1a000 bss=0x0 symbols=[+0x0+0x4+0x0+0x4+0xff8c] Can't find file /boot/loader.config total=0x12af94 entry point=0x100000 Console: BIOS serial port BIOS drive A: is disk0 BIOS drive C: is disk1 FreeBSD/i386 bootstrap loader, Revision 0.2 638/65532kB (gallatin@grasshopper.cs.duke.edu, Tue Nov 17 15:51:23 EST 1998) > set console=comconsole > autoboot 3 Hit [Enter] to boot immediately, or any other key for command prompt. The old bootstrap has no problem with a serial console on this box, nor does any FreeBSD kernel I've ever used on these machines. The odd thing is that of the 8 nearly identical machines I upgraded today, only 2 had this problem. These machines are Dell Dimensions, all off the same pallette. I've appended boot -v messages from the latest a.out kernel I had handy: Thanks for any help you can provide, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 Booting 0:da(0,a)kernel.GENERIC @ 0x100000 text=0x172000 data=0x1b000 bss=0x1ddd0 symbols=[+0x230+0x4+0x179f4+0x4+0x211b1] Can't find file kernel.GENERIC.config total=0x2e3bad entry point=0x100000 BIOS basemem (638K) != RTC basemem (640K), setting to BIOS value BIOS extmem (65532K) != RTC extmem (65535K) Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Mon Oct 19 10:26:12 EDT 1998 gallatin@grasshopper.cs.duke.edu:/freebsd/src/sys/compile/GENERICupgrade Calibrating clock(s) ... TSC clock: 299939808 Hz, i8254 clock: 1193177 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz cost 3028 ns CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 299942826 Hz cost 163 ns CPU: Pentium II (299.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80f9ff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002b7000 - 0x07ffdfff, 131362816 bytes (32071 pages) avail memory = 127811584 (124816K bytes) Found BIOS32 Service Directory header at 0xf00f7530 Entry = 0xfd7b1 (0xf00fd7b1) Rev = 0 Len = 1 PCI BIOS entry at 0x21c DMI header at 0xf00f7520 Version 2.0 Table at 0xefa90, 39 entries, 1241 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000f7550 pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71808086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7180, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base f8000000, size 26 chip0: rev 0x03 on pci0.0.0 found-> vendor=0x8086, dev=0x7181, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip1: rev 0x03 on pci0.1.0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip2: rev 0x01 on pci0.7.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 ide_pci0: rev 0x01 on pci0.7.1 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 chip3: rev 0x01 int d irq 11 on pci0.7.2 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip4: rev 0x01 on pci0.7.3 found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000f800, size 8 map[1]: type 1, range 32, base fedff000, size 12 ahc0: rev 0x00 int a irq 10 on pci0.13.0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable is present, internal 68 cable is present ahc0: external cable not present ahc0: BIOS eeprom is present ahc0: High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Resetting Channel A ahc0: Downloading Sequencer Program... 411 instructions downloaded found-> vendor=0x8086, dev=0x1229, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 3, range 32, base fedfe000, size 12 map[1]: type 4, range 32, base 0000fcc0, size 5 map[2]: type 1, range 32, base fec00000, size 20 fxp0: rev 0x02 int a irq 9 on pci0.14.0 fxp0: Ethernet address 00:a0:c9:8a:ae:53 found-> vendor=0x10e8, dev=0x8043, revid=0x01 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base fea00000, size 21 Probing for devices on PCI bus 1: found-> vendor=0x12d2, dev=0x0018, revid=0x10 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 1, range 32, base fd000000, size 24 map[1]: type 3, range 32, base f6000000, size 24 vga0: rev 0x10 int a irq 9 on pci1.0.0 Probing for devices on the ISA bus: video: RTC equip. code:0x03, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c044e, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 01 90 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: the current keyboard controller command byte 0045 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: irq maps: 0x1 0x1 0x1 0x1 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 not found at 0x2f8 sio2: disabled, not probed. sio3: disabled, not probed. lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found mse0: wrong signature ff mse0 not found at 0x23c psm0: current command byte:0045 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fe kbdio: RESET_AUX return code:00fe kbdio: RESET_AUX return code:00fe kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 not found at 0x170 wt0 not found at 0x300 mcd0: timeout getting status mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0: Failed Status Reg Test - fe bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0: Failed Status Reg Test - ff bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. imasks: bio c0080040, tty c0070292, net c0070292 BIOS Geometries: 0:0209fe3f 0..521=522 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. new masks: bio c0080040, tty c0070292, net c0070292 Waiting 15 seconds for SCSI devices to settle (noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 15:40:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01100 for freebsd-current-outgoing; Wed, 18 Nov 1998 15:40:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01072 for ; Wed, 18 Nov 1998 15:40:27 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id AAA09749; Thu, 19 Nov 1998 00:44:48 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 19 Nov 1998 00:44:47 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Bill Woods cc: Doug White , FreeBsd-Current Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Bill Woods wrote: > > any idea when this may be possible? Untill then, do you know where I could > grab a copy of Star Office 4.0 that works on FreeBSD ? StarOffice 4.0 works perfectly on FreeBSD after applying a small patch to procfs. See my recent postings on the subject. (BTW. the patches are not mine, but I forgot who wrote them - see DejaNews for the original author). Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 15:54:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03192 for freebsd-current-outgoing; Wed, 18 Nov 1998 15:54:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03126 for ; Wed, 18 Nov 1998 15:53:59 -0800 (PST) (envelope-from bsdx@spawnet.com) Received: from spawnet.com (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.9.1/8.8.7) with ESMTP id SAA11996 for ; Wed, 18 Nov 1998 18:53:23 -0500 (EST) (envelope-from bsdx@spawnet.com) Message-ID: <36535DF0.B9E7EA1B@spawnet.com> Date: Wed, 18 Nov 1998 18:53:20 -0500 From: Adam McDougall X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: kernel make failure in smbus References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy Bush wrote: > > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -aout ../../dev/smbus/smbus.c > ../../dev/smbus/smbus.c:84: `bus_create_intr_desc' undeclared here (not in a function) > ../../dev/smbus/smbus.c:84: initializer element for `smbus_methods[7].desc' is not constant > ../../dev/smbus/smbus.c:84: `bus_generic_create_intr' undeclared here (not in a function) > ../../dev/smbus/smbus.c:84: initializer element for `smbus_methods[7].func' is not constant > ../../dev/smbus/smbus.c:85: `bus_connect_intr_desc' undeclared here (not in a function) > ../../dev/smbus/smbus.c:85: initializer element for `smbus_methods[8].desc' is not constant > ../../dev/smbus/smbus.c:85: `bus_generic_connect_intr' undeclared here (not in a function) > ../../dev/smbus/smbus.c:85: initializer element for `smbus_methods[8].func' is not constant > *** Error code 1 > > Stop. Confirmed still broken on Wednesday, wondering if anyone has looked into it yet :/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 15:57:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03652 for freebsd-current-outgoing; Wed, 18 Nov 1998 15:57:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03647 for ; Wed, 18 Nov 1998 15:57:48 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from william.cybcon.com (william@pm3a-34.cybcon.com [205.147.75.163]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id PAA12844; Wed, 18 Nov 1998 15:57:06 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 18 Nov 1998 15:55:33 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Andrzej Bialecki Subject: Re: StarOffice 5.0 Cc: FreeBsd-Current Cc: FreeBsd-Current , Doug White Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Care to inform me where I can get 4.0 ? On 18-Nov-98 Andrzej Bialecki wrote: > On Wed, 18 Nov 1998, Bill Woods wrote: > >> >> any idea when this may be possible? Untill then, do you know where I could >> grab a copy of Star Office 4.0 that works on FreeBSD ? > > StarOffice 4.0 works perfectly on FreeBSD after applying a small patch to > procfs. See my recent postings on the subject. (BTW. the patches are not > mine, but I forgot who wrote them - see DejaNews for the original author). > > Andrzej Bialecki > > -------------------- ++-------++ ------------------------------------- > ||PicoBSD|| FreeBSD in your pocket? Go and see: > Research & Academic |+-------+| "Small & Embedded FreeBSD" > Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ > -------------------- ~-+==---+-+ ------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: William Woods Date: 18-Nov-98 Time: 15:53:44 -->> FreeBSD 3.0 <<-- AIM bsdman1 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 16:00:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04136 for freebsd-current-outgoing; Wed, 18 Nov 1998 16:00:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04126 for ; Wed, 18 Nov 1998 16:00:11 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id BAA14910; Thu, 19 Nov 1998 01:05:12 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 19 Nov 1998 01:05:12 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: William Woods cc: FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, William Woods wrote: > Care to inform me where I can get 4.0 ? I don't know - I got it on a CD with one of Polish magazines. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 16:11:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07359 for freebsd-current-outgoing; Wed, 18 Nov 1998 16:11:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bashful.realminfo.com (bashful.realminfo.com [208.205.6.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07351 for ; Wed, 18 Nov 1998 16:11:14 -0800 (PST) (envelope-from smyth@bashful.realminfo.com) Received: from localhost (smyth@localhost) by bashful.realminfo.com (8.8.7/8.8.7) with SMTP id UAA31804; Wed, 18 Nov 1998 20:25:52 -0500 Date: Wed, 18 Nov 1998 20:25:52 -0500 (EST) From: Scott Smyth To: Archie Cobbs cc: FreeBSD Current Mailing List Subject: Re: can't find libnet.so.0.93 for perl stuff In-Reply-To: <199811182248.OAA28161@bubba.whistle.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your help. It turns out when I did an "upgrade" I build the 3.0 source, but that left some things in /usr/local/bin hanging around: perl, gcc, etc... that are now in the distribution rather than ports. I rid myself of perl and gcc stuff in /usr/local, and all is happy. Thanks again, Scott On Wed, 18 Nov 1998, Archie Cobbs wrote: > Mark Murray writes: > > Scott Smyth wrote: > > > On a couple occasions I have had the error: > > > "can't find libnet.so.0.92" for doing any perl stuff, which is > > > part of kernel build too. It goes away depending on what day I > > > download and build the FreeBSD-3.0 sources. The last day I > > > downloaded was 11/15 and rebuilt the system only to have this > > > error again. > > > > Sounds like you have an (old, broken) perl port. Delete the perl > > port and let 3.0's _system_ perl do the job. > > Or possibly an old kaffe port (?), which used to create a library > with that exact same name. > > -Archie > > ___________________________________________________________________________ > Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com > -- Scott Smyth, Senior Developer R&D (770) 446-1332 ssmyth@realminfo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 16:13:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07870 for freebsd-current-outgoing; Wed, 18 Nov 1998 16:13:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07865 for ; Wed, 18 Nov 1998 16:13:20 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id SAA66500; Wed, 18 Nov 1998 18:12:47 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199811190012.SAA66500@ns.tar.com> From: "Richard Seaman, Jr." To: "HighWind Software Information" Cc: "current@FreeBSD.ORG" , "green@unixhelp.org" Date: Wed, 18 Nov 98 18:12:47 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: LinuxThreads (was Re: RFSIGSHARE ready?) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998 17:52:17 -0500 (EST), HighWind Software Information wrote: > >I have a question with regard to LinuxThreads on FreeBSD 3.0 > >Is this a substitute for libc_r?? > >How does this fit into the picture? > >-Rob It is my impression, though I can't speak for him, that Brian Feldman was working on getting linuxthreads working in linux emulation. One clear benefit would be, if it works, that linux apps compiled against linuxthreads would run on FreeBSD using the linux emulation. I guess that if you can figure out how to link your app to the linux threads and glibc libraries, your "native" FreeBSD app could run linux threads too. I've also been playing around with a "port" of linuxthreads to FreeBSD that wouldn't need the linux shared libraries or linux emulation, and would link to native FreeBSD apps, and use the FreeBSD libc library. I wouldn't call it a substitute for libc_r, but rather an alternative. I recently asked how much interest there was in a "kernel" pthreads implementation that would be a "one-to-one" mapping of threads to kernel schedulable entities. There were 2 positive responses, and lots of responses about how FreeBSD should use various alternative "models". With the work Brian started on signal sharing (which would be necessary for almost any kind of "kernel threads" implementation, at least in varying degrees) I thought I would see how hard a linuxthreads port would be. My theory was that it might be a "quick fix" for kernel threads under FreeBSD, while everyone works on their more sophisticated kernel threads models. There are some libc issues to be worked out (which would have to be worked out for almost any "kernel threads" model), but if anyone is interested, I think linuxthreads can work. However, I haven't seen much interest in a "one-to-one" kernel threads implemenation, so I've just been poking around quietly on the subject. I'd be happy to tar up the "port" and send it to anyone who wants to play around with it, or to post it somewhere. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 16:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10982 for freebsd-current-outgoing; Wed, 18 Nov 1998 16:30:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10977 for ; Wed, 18 Nov 1998 16:30:16 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id QAA13234; Wed, 18 Nov 1998 16:29:42 -0800 (PST) Date: Wed, 18 Nov 1998 16:29:43 -0800 (PST) From: Tom Bartol To: Doug Rabson cc: freebsd-current@FreeBSD.ORG Subject: Problem with amd (was: NFS problems in -current) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Doug Rabson wrote: > On Tue, 17 Nov 1998, Tom Bartol wrote: > > > > > Hi all, > > > > I've been seeing the following problem for a while now (since > > 3.0-19981006-BETA) but was too busy at the time to report it or help > > diagnose it further. Now I've got some time on my hands... > > > > I can fairly consistently wedge NFS writes to our server with the > > following: > > > > dd if=/dev/zero of=ick bs=8192 count=1000 > > > > which tries to write an 8MB file to our file server which is an Auspex. I > > have mounted Auspex from my 3.0-current machine (cvsupped and built this > > morning) in NFSv3 mode. This command will wedge one or more of the nfsiod > > processes. "ps -auwx | grep nfsiod" reports the following: > > > > root 137 0.0 0.0 216 64 ?? I 9:12AM 0:02.31 nfsiod -n 4 > > root 138 0.0 0.0 216 64 ?? I 9:12AM 0:01.74 nfsiod -n 4 > > root 139 0.0 0.0 216 64 ?? D 9:12AM 0:00.27 nfsiod -n 4 > > root 140 0.0 0.0 216 64 ?? D 9:12AM 0:00.24 nfsiod -n 4 > > > > The two processes in state "D" are the wedged ones. A separate machine > > running -current from July 11 works fine. > > > > Eventually all the nfsiod's get wedged and I'm forced to reboot. NFS > > reads work fine. > > > > Is anyone else seeing similar behaviour? What can I do to try to fine > > tune a diagnosis and help solve the problem? > > > > Thanks for your help, > > The best place to start is to get a tcpdump of the set of transactions > which wedged the iod. > > -- O.K. Here's another big clue. I had been mounting using amd. If I mount without amd then all is well and performance is much better also. I now get ~9MBps instead of ~4MBps over a 100BT segment. So, I know we are now using a newer version of amd. This version seems to be causing me lots of problems. Is anyone else out there experiencing this??? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 16:39:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11960 for freebsd-current-outgoing; Wed, 18 Nov 1998 16:39:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA11954 for ; Wed, 18 Nov 1998 16:39:54 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <52281(4)>; Wed, 18 Nov 1998 16:39:21 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Wed, 18 Nov 1998 16:39:07 -0800 To: "Dmitry Eremin" cc: freebsd-current@FreeBSD.ORG, "Bill Fenner" Subject: Re: ARP problem with two same Ethernet cards. In-reply-to: Your message of "Tue, 17 Nov 98 13:40:21 PST." <00b401be1272$e4336de0$0200000a@winhome.sci-nnov.ru> Date: Wed, 18 Nov 1998 16:39:01 PST From: Bill Fenner Message-Id: <98Nov18.163907pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry, As you know, I'm the author of the code in question. I tested it on my machine at home, which has two different interfaces of two different types, and I did not see the behavior you are reporting. In the hopes that the problem can be replicated on a machine with two identical ethernet cards, I will go to the store this evening and try to find another card to install in my machine to try to replicate your problem. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 16:40:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA12288 for freebsd-current-outgoing; Wed, 18 Nov 1998 16:40:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-10.dialip.mich.net [192.195.231.212]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA12276 for ; Wed, 18 Nov 1998 16:40:34 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811190040.QAA12276@hub.freebsd.org> Received: (qmail 91314 invoked from smtpd); 19 Nov 1998 00:39:51 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 19 Nov 1998 00:39:51 -0000 Date: Wed, 18 Nov 1998 19:39:50 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: more dying daemons To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm still having the problems I described earlier. inetd, samba, and ssh exhibit symptoms where they wither away and die after a certain amount of time, and this is easily and rapidly reproducible (in the space of only an hour my freshly-started inetd will begin to die each time it forks...) obviously, this is quite an annoying problem. I have a debugging version of inetd compiled, along with samba. I'll repost my samba backtraces if they'll help. inetd gives the "junk pointer: too high to make sense" messages before it dies. I'm still figuring out how to debug that problem, as it dies before I can attach to it with gdb. what can I do to help diagnose/fix these problems? This is on -current as of ~2 days ago. (my machine has been up since then, and the problems only get worse the longer the machine has been up) my swap usage is: Device 1024-blocks Used Avail Capacity Type /dev/wd0s1b 69632 49032 20472 71% Interleaved /dev/wd2s1b 81920 47568 34224 58% Interleaved Total 151296 96600 54696 64% Mem: 54M Active, 2596K Inact, 16M Wired, 1664K Cache, 2844K Buf, 18M Free Swap: 148M Total, 94M Used, 53M Free, 64% Inuse and i do have one "suggest more swap" message in my logs: Nov 16 21:54:32 jason /kernel: swap_pager: suggest more swap space: 190 MB along with an "interesting" message from sshd (1.2.26): Nov 18 20:39:32 jason sshd[90364]: fatal: xmalloc: out of memory (allocating 107 3675515 bytes) (oddly enough it isn't even 8pm yet, weird. unrelated problem? :)) and many instances of inetd dying on sigsegv's. please, i'm willing to give people accounts on this machine, do debugging, test patches, whatever it takes. just tell me what data/information you need or point me in the right direction. i had none of these problems when i ran 2.2-stable a while back, on the same hardware. thanks, -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 17:11:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16280 for freebsd-current-outgoing; Wed, 18 Nov 1998 17:11:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16273 for ; Wed, 18 Nov 1998 17:11:48 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id UAA16936 for ; Wed, 18 Nov 1998 20:10:45 -0500 (EST) Date: Wed, 18 Nov 1998 20:10:45 -0500 (EST) From: John Fieber To: current@FreeBSD.ORG Subject: Re: more dying daemons In-Reply-To: <199811190040.QAA12276@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998 garman@earthling.net wrote: > what can I do to help diagnose/fix these problems? Has anyone come up with conclusive results from tests using a statically linked inetd? -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 18:03:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21368 for freebsd-current-outgoing; Wed, 18 Nov 1998 18:03:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-10.dialip.mich.net [192.195.231.212]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA21362 for ; Wed, 18 Nov 1998 18:03:12 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811190203.SAA21362@hub.freebsd.org> Received: (qmail 91910 invoked from smtpd); 19 Nov 1998 02:02:41 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 19 Nov 1998 02:02:41 -0000 Date: Wed, 18 Nov 1998 21:02:40 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: more dying daemons To: jfieber@indiana.edu cc: current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Nov, John Fieber wrote: > On Wed, 18 Nov 1998 garman@earthling.net wrote: > >> what can I do to help diagnose/fix these problems? > > Has anyone come up with conclusive results from tests using a > statically linked inetd? > more specifically, this is what I get when telnetting to my machine (compiled -g -static): bash-2.02$ telnet 192.195.231.212 Trying 192.195.231.212... Connected to pm106-10.dialip.mich.net. Escape character is '^]'. inetd in realloc(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too low to make sense. Connection closed by foreign host. then the inetd child dies with a segfault. i'll try adding some code to pause when forking, or some printfs to see where this is crashing, hopefully this weekend, but i'm imagining its going to be the same symptoms as my samba crashes (where a pointer is suddenly zeroed out) either way this looks like a kernel space issue, and that's out of my range of comprehension for the moment (especially the vm subsystem :)) it seems correlated with swap/memory usage, as i started wordperfect and gimp before it died. however, i didn't run out of swap space. (it is hovering around 60% per my previous message) enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 18:28:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24001 for freebsd-current-outgoing; Wed, 18 Nov 1998 18:28:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23987 for ; Wed, 18 Nov 1998 18:28:10 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id MAA17347; Thu, 19 Nov 1998 12:57:28 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA01068; Thu, 19 Nov 1998 12:57:27 +1030 (CST) Message-ID: <19981119125726.I467@freebie.lemis.com> Date: Thu, 19 Nov 1998 12:57:26 +1030 From: Greg Lehey To: Harold Gutch , freebsd-current@FreeBSD.ORG Subject: Re: page fault when rm'ing on ccd-partition References: <19981118113805.A5521@foobar.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981118113805.A5521@foobar.franken.de>; from Harold Gutch on Wed, Nov 18, 1998 at 11:38:05AM +0100 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 18 November 1998 at 11:38:05 +0100, Harold Gutch wrote: > Hi, > > I'm experiencing problems on a (non-local) 3.0-19980916-SNAP > non-SMP System. When rm'ing certain files from a ccd'd disk the > machine panics. I can't really localize the problem any further > as: > > - I don't know which files exactly cause the problem, or what > they have in common, > find -mtime 7 | xargs rm > over one of the ccd-partitions reproducebly panics the machine > though. > > - A person local to the machine wrote down the following > panic-output: > > Fatal Trap 12: page fault while in kernel mode > > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf01152c7 > stack pointer = 0x10:0xf0211f7c > frame pointer = 0x10:0xf0211f94 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL0, pres 1, def32 1, gran 1 > processor flags = interrupt enabled, resume, IOPL=0 > current process = Idle > interrupt mask = cam > trap number = 12 > panic: page fault > > $ nm -aout /kernel | grep f01152 > f0115288 t _ahc_handle_target_cmd You really need a little more information than this. Build a debug kernel and use gdb to show the lines that correspond to the IP where it fails. You can use /dev/mem as the dump file. > from /etc/ccd.conf: > ccd1 65536 0 /dev/sd4g /dev/sd5g /dev/sd6g /dev/sd7g > > So if it's the SCSI-driver which causes the panics, trying to > dump to a SCSI-disk isn't very likely to succeed :). > > - The kernel even refuses to dump to a newly plugged in IDE-disk, > a partition of which is configured as swap- and dumpdevice, but > after booting the output "savecore: no core dump" can be seen. What happens before the boot, when it's supposed to be dumping? > As the machine is about an hour's ride away from me, I'd rather > be able to debug the problem remotely. > I asked for a serial cable to a linux-box standing next to the > FreeBSD-machine, I guess I then could use it as console, get it to > fall to ddb when panicing and then get a stacktrace - or am I > missing something that wouldn't work ? No, that should work. It's liable to be a painful way of doing things, though. You'd be better off with a FreeBSD box with a copy of the sources and kernel gdb, which you could then use to debug the system relatively well. > If i got the kernel do dump to the IDE-disk, that too would of > course help... any ideas why this is failing ? I could only guess, and guesswork doesn't help in this kind of situation. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 18:47:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25811 for freebsd-current-outgoing; Wed, 18 Nov 1998 18:47:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-10.dialip.mich.net [192.195.231.212]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA25805 for ; Wed, 18 Nov 1998 18:47:50 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811190247.SAA25805@hub.freebsd.org> Received: (qmail 92221 invoked from smtpd); 19 Nov 1998 02:47:17 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 19 Nov 1998 02:47:17 -0000 Date: Wed, 18 Nov 1998 21:47:16 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: more dying daemons To: current@FreeBSD.ORG In-Reply-To: <199811190040.QAA12276@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18 Nov, I wrote: > > I'm still having the problems I described earlier. > inetd, samba, and ssh exhibit symptoms where they wither away and die > after a certain amount of time, and this is easily and rapidly > reproducible (in the space of only an hour my freshly-started inetd will > begin to die each time it forks...) > while sitting here trying to find a common thread through all this mess... it appears to happen only with servers that fork() copies of themselves on incoming requests. inetd does this, samba does this, and sshd does this. consequently, inetd dies, samba dies, and sshd dies :) however, servers that *don't* fork off a new connection on incoming requests don't die. a good example is mysql. i've never had a problem with it dying, even though it gets swapped out much more often than the other servers (it is rarely used)... another example is httpd which only has problems when its heavily used (i'm guessing that it has run out of pre-forked copies and has to fork off new children) so, it looks like a problem where parts of a daemon are swapped out and then when the daemon forks, some of the pages are never paged back in? i dunno, a guess at least :) that should help narrow down the source of the problem dramatically. when i get a free moment i'll try going through the commits on various parts of the vm subsystem and see what i can dig up... enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 19:21:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29109 for freebsd-current-outgoing; Wed, 18 Nov 1998 19:21:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29100 for ; Wed, 18 Nov 1998 19:21:07 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id WAA07777; Wed, 18 Nov 1998 22:20:39 -0500 (EST) Date: Wed, 18 Nov 1998 22:20:39 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: William Woods cc: Andrzej Bialecki , FreeBsd-Current , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, William Woods wrote: > Care to inform me where I can get 4.0 ? ftp://ftp.stardiv.de/pub/so4/linux/sp3/01/so40sp3_lnx_01.tar.gz > ---------------------------------- > E-Mail: William Woods > Date: 18-Nov-98 > Time: 15:53:44 > -->> FreeBSD 3.0 <<-- > AIM bsdman1 > --------------------------------- Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 19:25:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29545 for freebsd-current-outgoing; Wed, 18 Nov 1998 19:25:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from paris.dppl.com (paris.dppl.com [205.230.74.150]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA29540 for ; Wed, 18 Nov 1998 19:25:07 -0800 (PST) (envelope-from yds@ingress.net) Received: (qmail 7371 invoked from network); 19 Nov 1998 03:24:40 -0000 Received: from ichiban.ingress.com (HELO ichiban) (205.230.64.31) by paris.dppl.com with SMTP; 19 Nov 1998 03:24:40 -0000 Message-ID: <021f01be136c$244d6440$1f40e6cd@ichiban.ingress.com> From: "Yarema" To: Subject: Re: /etc/rc.d, and changes to /etc/rc? Date: Wed, 18 Nov 1998 22:24:39 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I strongly oppose this; rc.d already exists and is standardized in several >> releases. Such a change would be gratuitous. > >I wasn't suggesting that rc.d be ditched, merely that another option be >provided if a port wished to make use of it. >> >> rc.shutdown.d would be a self-documenting name. rcK.d doesn't mean >> anything to me. (K=kill?? I don't come from a Solaris background.) > >Yep, Knnscriptname generally means "this is a shutdown script, invoke >me as scriptname stop". rc.shutdown.d would be fine, the examples I >provided were merely a rough idea. >> >> It would save people from hacking /etc/rc.shutdown (like rc.d saves >> hacking /etc/rc.local). I believe someone pointed this out already, but there's no need to make any new rc*.d directories. So long as the scripts in /usr/local/etc/rc.d are written to accept start & stop parameters the way SysVinit /etc/init.d/ scripts are written. Simply applying the patch below to /etc/rc.shutdown should allow ports to be shutdown cleanly. Should be harmless if /usr/local/etc/rc.d/*.sh scripts do not accept the stop parameter. Better yet rename the current /etc/rc.shutdown to /etc/rc.shutdown.local (analogous to /etc/rc.local) and source it into a new /etc/rc.shutdown which only does the stuff below. BTW, ${local_startup} in /etc/rc.conf becomes rather misnamed if this patch is adopted. --- rc.shutdown.orig Fri Aug 1 20:22:45 1997 +++ rc.shutdown Wed Nov 18 22:10:04 1998 @@ -17,6 +17,23 @@ PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin export PATH +# If there is a global system configuration file, suck it in. +if [ -f /etc/rc.conf ]; then + . /etc/rc.conf +fi + +# for each valid dir in $local_startup, search for init scripts matching *.sh +if [ "X${local_startup}" != X"NO" ]; then + echo -n 'Local package shutdown:' + for dir in ${local_startup}; do + [ -d ${dir} ] && for script in ${dir}/*.sh; do + [ -x ${script} ] && \ + (trap 'exit 1' 2 ; ${script} stop ; echo -n) + done + done + echo . +fi + echo -n Shutting down daemon processes: # Insert shutdown procedures here To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 20:20:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04799 for freebsd-current-outgoing; Wed, 18 Nov 1998 20:20:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04794 for ; Wed, 18 Nov 1998 20:20:22 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA07192; Wed, 18 Nov 1998 21:19:42 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811190419.VAA07192@panzer.plutotech.com> Subject: Re: page fault when rm'ing on ccd-partition In-Reply-To: <19981118113805.A5521@foobar.franken.de> from Harold Gutch at "Nov 18, 98 11:38:05 am" To: logix@foobar.franken.de (Harold Gutch) Date: Wed, 18 Nov 1998 21:19:42 -0700 (MST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Harold Gutch wrote... > Hi, > > I'm experiencing problems on a (non-local) 3.0-19980916-SNAP > non-SMP System. When rm'ing certain files from a ccd'd disk the > machine panics. I can't really localize the problem any further > as: [ ... ] > $ nm -aout /kernel | grep f01152 > f0115288 t _ahc_handle_target_cmd I believe this panic was fixed a couple of days after that snapshot was made: [ log from sys/dev/aic7xxx/aic7xxx.c ] revision 1.3 date: 1998/09/18 03:42:16; author: gibbs; state: Exp; lines: +3 -2 Don't interpret SCB index 254 as a target mode completion when not in target mode. This hack of using the normal command complete mechanism for target cdb completion will go away soon. Submitted by: Tor.Egge@fast.no A number of other CAM bugs have been fixed since then. I would recommend upgrading to a recent -current snapshot. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 20:28:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05594 for freebsd-current-outgoing; Wed, 18 Nov 1998 20:28:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05569 for ; Wed, 18 Nov 1998 20:28:00 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id XAA03773; Wed, 18 Nov 1998 23:27:00 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Wed, 18 Nov 1998 23:27:00 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Andrew Gallatin cc: Robert Nordier , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader & comconsole In-Reply-To: <13907.20799.296610.678439@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Andrew Gallatin wrote: > > I'm in the process of upgrading a cluster of (nearly identical) PII's to 3.0-CURRENT & am > installing the new 3-stage bootstrap. On some of the machines, using > a comconsole wedges the bootloader solid ( well, 2 ctrl-alt-deletes on the > local keyboard will reboot the machine). > > My /boot.config looks like: > /boot/loader -h Try just putting -h, -D, or -P in boot.conf and nothing else. I just set up a bunch of machines with no video or keyboard and I simply put -P in boot.conf and the new bootstrap works just fine. The old bootblocks also work, but the screen can get garbled from time to time. Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 20:28:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05623 for freebsd-current-outgoing; Wed, 18 Nov 1998 20:28:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (tex-114.camalott.com [208.229.74.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05597 for ; Wed, 18 Nov 1998 20:28:05 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id WAA03145; Wed, 18 Nov 1998 22:24:59 -0600 (CST) (envelope-from joelh) To: Dan Nelson Cc: Harold Gutch , freebsd-current@FreeBSD.ORG Subject: Re: KGDB with aout References: <199811181803.MAA00465@detlev.UUCP> <19981118205229.A7476@foobar.franken.de> <19981118150641.A13349@emsphone.com> From: Joel Ray Holveck Date: 18 Nov 1998 22:24:59 -0600 In-Reply-To: Dan Nelson's message of "Wed, 18 Nov 1998 15:06:41 -0600" Message-ID: <86u2zwgvhg.fsf@detlev.UUCP> Lines: 26 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> Do we have any way to do post-mortem kernel debugging of an a.out >>> kernel, or do I need to bite the bullet and go to an ELF kernel? >> You need an a.out gdb, for example from an a.out system you still >> have somewhere - or from ftp://ftp.lemis.com/pub/vinum/gdb-aout. > revision 1.11 > date: 1998/10/15 00:19:08; author: peter; state: Exp; lines: +3 -1 > Add objformat links for gdb and (while we're at it) c++filt. > This means we can (assuming an a.out gdb is present) debug a.out kernels > and crashdumps with gdb -aout. > Just running: > gdb -aout -k kernel.0 vmcore.0 > should work (works for me). And if you don't have an a.out gdb, you > should be able to build one via "OBJFORMAT=aout ; make clean && make > all install" in the gdb source dir. Bad Joel! No cookie! Make world, make world, before asking, make world! :-) Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 21:11:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10091 for freebsd-current-outgoing; Wed, 18 Nov 1998 21:11:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10086 for ; Wed, 18 Nov 1998 21:11:19 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA24065; Wed, 18 Nov 1998 22:03:26 -0700 (MST) Date: Wed, 18 Nov 1998 22:03:26 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811190503.WAA24065@narnia.plutotech.com> To: Harold Gutch cc: current@FreeBSD.ORG Subject: Re: page fault when rm'ing on ccd-partition X-Newsgroups: pluto.freebsd.current In-Reply-To: <19981118113805.A5521@foobar.franken.de> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981118113805.A5521@foobar.franken.de> you wrote: > Hi, > > I'm experiencing problems on a (non-local) 3.0-19980916-SNAP This bug was fixed before 3.0R went out the door. You need to upgrade to 3.0R or a later snapshot. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 21:11:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10137 for freebsd-current-outgoing; Wed, 18 Nov 1998 21:11:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10102 for ; Wed, 18 Nov 1998 21:11:22 -0800 (PST) (envelope-from ggm@sleet.dstc.edu.au) Received: from sleet.dstc.edu.au (sleet.dstc.edu.au [130.102.176.45]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id PAA07159 for ; Thu, 19 Nov 1998 15:10:42 +1000 (EST) Received: (from ggm@localhost) by sleet.dstc.edu.au (8.8.5/8.8.4) id PAA02488 for freebsd-current@FreeBSD.ORG; Thu, 19 Nov 1998 15:10:42 +1000 (EST) Date: Thu, 19 Nov 1998 15:10:42 +1000 (EST) From: George Michaelson Message-Id: <199811190510.PAA02488@sleet.dstc.edu.au> To: freebsd-current@FreeBSD.ORG Subject: ps -ef (bloody solaris) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG while I'm wingeing, i wish sun could be shot for foisting ps -ef on us. but since they did, maybe we can make ps smart enough to complain, but process it anyway.. -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 21:13:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10243 for freebsd-current-outgoing; Wed, 18 Nov 1998 21:13:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thing.dyn.ml.org (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10235 for ; Wed, 18 Nov 1998 21:12:59 -0800 (PST) (envelope-from bsdx@spawnet.com) Received: from spawnet.com (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.9.1/8.8.7) with ESMTP id AAA15345 for ; Thu, 19 Nov 1998 00:12:31 -0500 (EST) (envelope-from bsdx@spawnet.com) Message-ID: <3653A8BE.3F0C1E58@spawnet.com> Date: Thu, 19 Nov 1998 00:12:30 -0500 From: Adam McDougall X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: vm_fault: pager read error Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently I got a new (to me) Hard drive, a Quantum Viking UW, 4.5g, and I use it with an Ultraplex on my DPT 2144UW. tosha used to work fine with my previous HD, but now I get this: (or worse) after executing tosha -v -t 1 on a cd with a cd that might be scratched 1 63:07'00 33 284057 668026800 60592835 144972 (output file: track01.pcm) (da0:dpt0:0:0:0): WRITE(06). CDB: a 9 e0 40 10 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 sks:c0,9 (da0:dpt0:0:0:0): READ(06). CDB: 8 2 95 58 8 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 sks:c0,9 swap_pager: I/O error - pagein failed; blkno 46424, size 4096, error 22 vm_fault: pager read error, pid 96 (syslogd) (da0:dpt0:0:0:0): WRITE(06). CDB: a 1 0 50 10 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 sks:c0,9 ^C (da0:dpt0:0:0:0): READ(06). CDB: 8 2 9 b0 28 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 sks:c0,9 swap_pager: I/O error - pagein failed; blkno 10672, size 20480, error 22 vm_fault: pager read error, pid 257 (tcsh) pid 257 (tcsh), uid 1001: exited on signal 11 (core dumped) FreeBSD/i386 (hostname.domain.com) (ttyv0) login: now im wondering, why does it think da0 has a problem, if the cd was scratched wouldnt it have problems with cd0? Also, I can dd a large file to the hd just fine, and exercise swapping enough that I have no reason to believe my HD is failing, it does not 'act' like it is having trouble, it just goes bananas ONLY when I run tosha. my present kernel is from a day or two ago. If I knew a good date to cvsup back to before the recent vm changes (I believe there were some) but after the 'vector blah' changes to config, I could try again there, but a kernel from ~8 days ago behaved the same. When tosha is running, and these kernel messages spew by, the dae operation seems to be progressing merrily anyway, until it or the shell crashes, or the kernel panics (with page fault in kernel mode) I have rebuilt tosha, and ran as root and nonroot, both cause the same symptoms. System continues to be unstable until reboot. Insight would be much appreciated, Thanks :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 21:15:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10340 for freebsd-current-outgoing; Wed, 18 Nov 1998 21:15:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10333 for ; Wed, 18 Nov 1998 21:15:05 -0800 (PST) (envelope-from ggm@sleet.dstc.edu.au) Received: from sleet.dstc.edu.au (sleet.dstc.edu.au [130.102.176.45]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id PAA24779 for ; Thu, 19 Nov 1998 15:09:37 +1000 (EST) Received: (from ggm@localhost) by sleet.dstc.edu.au (8.8.5/8.8.4) id PAA02120 for freebsd-current@FreeBSD.ORG; Thu, 19 Nov 1998 15:09:36 +1000 (EST) Date: Thu, 19 Nov 1998 15:09:36 +1000 (EST) From: George Michaelson Message-Id: <199811190509.PAA02120@sleet.dstc.edu.au> To: freebsd-current@FreeBSD.ORG Subject: ps augxw doesn't show PPID Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bummer. Digital unix, Sunos, Solaris and (I think) straight BSD4.2 all showed parent PID by default. am I being stupid, mis-remembering or all three? -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 21:25:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11111 for freebsd-current-outgoing; Wed, 18 Nov 1998 21:25:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (tex-114.camalott.com [208.229.74.114]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11106 for ; Wed, 18 Nov 1998 21:25:03 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id XAA03481; Wed, 18 Nov 1998 23:24:23 -0600 (CST) (envelope-from joelh) To: George Michaelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: ps -ef (bloody solaris) References: <199811190510.PAA02488@sleet.dstc.edu.au> From: Joel Ray Holveck Date: 18 Nov 1998 23:24:22 -0600 In-Reply-To: George Michaelson's message of "Thu, 19 Nov 1998 15:10:42 +1000 (EST)" Message-ID: <86lnl8gsqh.fsf@detlev.UUCP> Lines: 16 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > while I'm wingeing, i wish sun could be shot for foisting ps -ef on us. > but since they did, maybe we can make ps smart enough to complain, but > process it anyway.. I thought that -ef was a general SysVism, not Sun-specific. But sounds like a good local alias to me. I find that DWIM features lose more than they win, especially with the BSD-exclusive hackers. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 21:36:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11937 for freebsd-current-outgoing; Wed, 18 Nov 1998 21:36:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11929 for ; Wed, 18 Nov 1998 21:36:06 -0800 (PST) (envelope-from ggm@dstc.edu.au) Received: from dstc.edu.au (sleet.dstc.edu.au [130.102.176.45]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id PAA08178; Thu, 19 Nov 1998 15:35:26 +1000 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: Joel Ray Holveck cc: freebsd-current@FreeBSD.ORG Subject: Re: ps -ef (bloody solaris) In-reply-to: Your message of "18 Nov 1998 23:24:22 CST." <86lnl8gsqh.fsf@detlev.UUCP> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Nov 1998 15:35:25 +1000 Message-ID: <2584.911453725@dstc.edu.au> From: George Michaelson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm blowing smoke. ps -j has a long and noble history. How I have managed to mis-remember it is beyond me. Ignore thread. Please. (sigh) -George -- George Michaelson | DSTC Pty Ltd Email: ggm@dstc.edu.au | University of Qld 4072 Phone: +61 7 3365 4310 | Australia Fax: +61 7 3365 4311 | http://www.dstc.edu.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 21:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13454 for freebsd-current-outgoing; Wed, 18 Nov 1998 21:49:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isabase.philol.msu.ru (isabase.philol.msu.ru [195.208.217.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13437 for ; Wed, 18 Nov 1998 21:49:20 -0800 (PST) (envelope-from grg@philol.msu.ru) Received: from localhost (grg@localhost) by isabase.philol.msu.ru (8.9.1/8.9.1) with ESMTP id IAA04036; Thu, 19 Nov 1998 08:48:20 +0300 (MSK) (envelope-from grg@philol.msu.ru) X-Authentication-Warning: isabase.philol.msu.ru: grg owned process doing -bs Date: Thu, 19 Nov 1998 08:48:19 +0300 (MSK) From: Grigoriy Strokin To: garman@earthling.net cc: current@FreeBSD.ORG Subject: Re: more dying daemons In-Reply-To: <199811190247.SAA25805@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the same problem. However, my 'current' version is a bit old, so the daemons are a bit more stable. They do this 1-4 times per week. ftpd,sshd and inetd, exactly as your describe. Moreover, inetd has a more interesting behaviour sometimes: it can work good a day or longer then issue approx. 200 messages in 2 seconds about "exit on signal 11", then any logging activity disappears... Grigoriy. On Wed, 18 Nov 1998 garman@earthling.net wrote: > On 18 Nov, I wrote: > > > > I'm still having the problems I described earlier. > > inetd, samba, and ssh exhibit symptoms where they wither away and die > > after a certain amount of time, and this is easily and rapidly > > reproducible (in the space of only an hour my freshly-started inetd will > > begin to die each time it forks...) > > > while sitting here trying to find a common thread through all this > mess... > > it appears to happen only with servers that fork() copies of themselves > on incoming requests. > > inetd does this, samba does this, and sshd does this. consequently, > inetd dies, samba dies, and sshd dies :) > > however, servers that *don't* fork off a new connection on incoming > requests don't die. > > a good example is mysql. i've never had a problem with it dying, even > though it gets swapped out much more often than the other servers (it > is rarely used)... another example is httpd which only has problems > when its heavily used (i'm guessing that it has run out of pre-forked > copies and has to fork off new children) > > so, it looks like a problem where parts of a daemon are swapped out and > then when the daemon forks, some of the pages are never paged back in? > i dunno, a guess at least :) > > that should help narrow down the source of the problem dramatically. > when i get a free moment i'll try going through the commits on various > parts of the vm subsystem and see what i can dig up... > > enjoy > -- > Jason Garman http://garman.dyn.ml.org/ > Student, University of Maryland garman@earthling.net > And now... did you know that: Whois: JAG145 > "If you fart consistently for 6 years and 9 months, enough gas is > produced to create the energy of an atomic bomb." -- 0xdeadbeef posting > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > === Grigoriy Strokin, Lomonosov University (MGU), Moscow === === contact info: http://isabase.philol.msu.ru/~grg/ === To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 22:03:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14701 for freebsd-current-outgoing; Wed, 18 Nov 1998 22:03:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14696; Wed, 18 Nov 1998 22:03:14 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA07196; Wed, 18 Nov 1998 23:02:46 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA02331; Wed, 18 Nov 1998 23:02:46 -0700 Date: Wed, 18 Nov 1998 23:02:46 -0700 Message-Id: <199811190602.XAA02331@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Robinson Cc: freebsd-java@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, gunther@aurora.rg.iupui.edu Subject: Re: green threads vs. native threads ... In-Reply-To: <199811190202.KAA29588@public.bta.net.cn> References: <199811190202.KAA29588@public.bta.net.cn> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Moved from -stable to -current, since -stable will never see any such move ] > >> I came in on this thread late, so I'm not sure if this has been asked, but > >> does the FreeBSD-Java team have any plans for a native threads VM? > > > >You have to have native-threads in the OS before you can expect to have > >the JDK use them. It's kind of a moot point to ask for the JDK to use > >something that doesn't exist. > > Would it be a moot point to ask for the FreeBSD kernel to support native > threads? Sure. Patches to implement them are gladly accepted. Oh, you mean forcing someone to implement threads in FreeBSD? Naw, that's not the way it's done. New features get done because someone thems to be done and does them. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 18 23:13:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21212 for freebsd-current-outgoing; Wed, 18 Nov 1998 23:13:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21206 for ; Wed, 18 Nov 1998 23:13:17 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id XAA11758 for ; Wed, 18 Nov 1998 23:12:49 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma011756; Wed, 18 Nov 98 23:12:26 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id XAA23068 for freebsd-current@freebsd.org; Wed, 18 Nov 1998 23:12:25 -0800 (PST) From: Archie Cobbs Message-Id: <199811190712.XAA23068@bubba.whistle.com> Subject: snprintf() in the kernel To: freebsd-current@FreeBSD.ORG Date: Wed, 18 Nov 1998 23:12:24 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to do the following: 1. Add snprintf() to kern/subr_prf.c 2. Change all appropriate uses of sprintf() and/or strcat() to use snprintf() instead. The main reason for doing this is not to add kernel bloat :-) but rather to improve the reliability and maintainability of the kernel. In fact, the total byte count may even go down due to the several instances in the code that are forced to do their own bounds checking (the changes to subr_prf.c are minimal). Cases where it's "obvious" that the buffer can't overflow will be left alone, for some conservative definition of "obvious". A typical example: RCS file: /home/ncvs/src/sys/alpha/tc/espvar.h,v retrieving revision 1.1 diff -u -r1.1 espvar.h --- espvar.h 1998/08/20 08:27:10 1.1 +++ espvar.h 1998/11/19 07:03:55 @@ -74,8 +74,7 @@ #define ECB_TRACE(ecb, msg, a, b) do { \ const char *f = "[" msg "]"; \ int n = strlen((ecb)->trace); \ - if (n < (sizeof((ecb)->trace)-100)) \ - sprintf((ecb)->trace + n, f, a, b); \ + snprintf((ecb)->trace + n, sizeof((ecb)->trace) - n, f, a, b); \ } while(0) #else #define ECB_TRACE(ecb, msg, a, b) I count 131 files that use sprintf() and 28 that use strcat(), so this will touch a lot of files (but hopefully for the better). So.. does anyone have a huge problem with doing this before I jump in? [ Anyone willing to review for me? ] Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 00:32:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28649 for freebsd-current-outgoing; Thu, 19 Nov 1998 00:32:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28644 for ; Thu, 19 Nov 1998 00:32:49 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id IAA13739; Thu, 19 Nov 1998 08:33:40 GMT Date: Thu, 19 Nov 1998 08:33:39 +0000 (GMT) From: Doug Rabson To: Tom Bartol cc: freebsd-current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998, Tom Bartol wrote: > O.K. Here's another big clue. I had been mounting using amd. If I mount > without amd then all is well and performance is much better also. I now > get ~9MBps instead of ~4MBps over a 100BT segment. > > So, I know we are now using a newer version of amd. This version seems to > be causing me lots of problems. Is anyone else out there experiencing > this??? I guess that amd must be using different options to mount with. The brute force to figuring that out would be to put some code in amd to print out the NFS mount options it is going to use and then compare that to mount_nfs. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 01:04:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03621 for freebsd-current-outgoing; Thu, 19 Nov 1998 01:04:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-47-dbn.dial-up.net [196.34.155.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03584 for ; Thu, 19 Nov 1998 01:03:59 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA03790; Thu, 19 Nov 1998 11:02:03 +0200 (SAT) From: Robert Nordier Message-Id: <199811190902.LAA03790@ceia.nordier.com> Subject: Re: /boot/loader & comconsole In-Reply-To: <13907.20799.296610.678439@grasshopper.cs.duke.edu> from Andrew Gallatin at "Nov 18, 98 06:25:36 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Thu, 19 Nov 1998 11:02:00 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG, adrian@ubergeeks.com X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I see Adrian has already responded to this, so I've added him to the cc list.] Andrew Gallatin wrote: > I'm in the process of upgrading a cluster of (nearly identical) PII's > to 3.0-CURRENT & am installing the new 3-stage bootstrap. On some of > the machines, using a comconsole wedges the bootloader solid ( well, > 2 ctrl-alt-deletes on the local keyboard will reboot the machine). > > My /boot.config looks like: > /boot/loader -h > > And /boot/boot.conf looks like: > set console=comconsole > autoboot 3 There seem to be two separate, and possibly unrelated issues, here. The first is that the *old* boot blocks are still being used, as shown by the actual messages displayed: > I see the following on console before it hangs: > > >> FreeBSD BOOT @ 0x10000: 638/65532 k of memory, serial console [ ... ] The corresponding line, for the new boot blocks, is simply >> FreeBSD/i386 BOOT Installing the new boot blocks at this stage is probably a good idea (and I think this was your intention), so you'll need to do a disklabel -B -b /boot/boot1 -s /boot/boot2 (as disklabel still installs from /usr/mdec rather than /boot by default). The whole boot issue is rather confused at the moment, so for anyone trying to follow this: "old boot blocks" : /sys/i386/boot/biosboot (install to /usr/mdec) "new boot blocks" : /sys/boot/i386/boot2 (install to /boot) "boot loader" : /sys/boot/i386/loader (install to /boot) > Boot default: 0:da(0,a)/boot/loader > Usage: bios_drive:interface(unit,partition)kernel_name options > <..snip..> > boot: > Booting 0:da(0,a)/boot/loader @ 0x100000 > text=0x1000 data=0x1a000 bss=0x0 symbols=[+0x0+0x4+0x0+0x4+0xff8c] > Can't find file /boot/loader.config > total=0x12af94 entry point=0x100000 > > > And there it stops. If I don't set console=comconsole, everything > works great. One difference between boot loader and the old/new boot blocks, is that boot loader uses PC BIOS services (int 0x14) for comms; both lots of boot blocks do direct port I/O, instead. The trouble with using the BIOS is that the int 0x14 services (which tend to be used only to talk to serial printers under DOS) expect to do hardware handshaking. They therefore impose fussier cabling requirements than the boot blocks or the kernel have. (They don't work with the sloppy 2-wire, 9-pin null modem cables I have here, for instance.) [...] > The old bootstrap has no problem with a serial console on this box, > nor does any FreeBSD kernel I've ever used on these machines. The odd > thing is that of the 8 nearly identical machines I upgraded today, > only 2 had this problem. If your cables aren't identical, you might try swapping those and see if there's a difference. (FWIW, the wedge you're getting is just what I get myself, unless I use a better cable for boot loader.) > These machines are Dell Dimensions, all off the same pallette. I've > appended boot -v messages from the latest a.out kernel I had handy: > > Thanks for any help you can provide, Thanks for the feedback, and let us know how you go. If necessary, I can do some patches to get boot loader using the boot blocks serial routines, which may be a good idea anyway. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 01:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04781 for freebsd-current-outgoing; Thu, 19 Nov 1998 01:10:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04749; Thu, 19 Nov 1998 01:10:30 -0800 (PST) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id RAA01871; Thu, 19 Nov 1998 17:10:03 +0800 (GMT) Date: Thu, 19 Nov 1998 17:10:03 +0800 (GMT) From: Michael Robinson Message-Id: <199811190910.RAA01871@public.bta.net.cn> To: nate@mt.sri.com Subject: Re: green threads vs. native threads ... Cc: freebsd-current@FreeBSD.ORG, freebsd-java@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nate Williams writes: >> Would it be a moot point to ask for the FreeBSD kernel to support native >> threads? > >Sure. Patches to implement them are gladly accepted. Oh, you mean >forcing someone to implement threads in FreeBSD? Naw, that's not the >way it's done. New features get done because someone thems to be done >and does them. That's one way of looking at it. Here's another way of looking at it: "A good example of keeping sight of the larger picture is FreeBSD's attitude towards its Linux emulation. It's not only very important to us that FreeBSD continues to run Linux binaries effectively, it's also what we suggest to those ISVs who are coming back somewhat cautiously to this "new" Unix market and obviously want to maximize their gains while minimizing risk. We tell them to port to Linux and not FreeBSD, even though we'd certainly love to have native binaries for anything and everything, and, by telling them to port to Linux first (or at all), we are giving them the best advice on how to get access to the widest possible segment of the free software market, one which includes but is not limited to us." -Jordan Hubbard ( http://editorials.freshmeat.net/jordan980713/ ) As I mentioned in the part you cut out, Linux emulation is increasingly broken in FreeBSD as more software comes to rely on Linux native threads. If it is, in fact, "very important to us that FreeBSD continues to run Linux binaries effectively" (whoever "us" is), I would recommend to "us" that cooperating on a native threads solution be given a higher priority. Otherwise, FreeBSD will *not* be part of the free software market that developers get access to when they follow Jordan's advice. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 01:58:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09864 for freebsd-current-outgoing; Thu, 19 Nov 1998 01:58:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-56-dbn.dial-up.net [196.34.155.120]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09856 for ; Thu, 19 Nov 1998 01:58:11 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA04596; Thu, 19 Nov 1998 11:56:25 +0200 (SAT) From: Robert Nordier Message-Id: <199811190956.LAA04596@ceia.nordier.com> Subject: Re: snprintf() in the kernel In-Reply-To: <199811190712.XAA23068@bubba.whistle.com> from Archie Cobbs at "Nov 18, 98 11:12:24 pm" To: archie@whistle.com (Archie Cobbs) Date: Thu, 19 Nov 1998 11:56:18 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs wrote: > I would like to do the following: > > 1. Add snprintf() to kern/subr_prf.c > > 2. Change all appropriate uses of sprintf() and/or strcat() > to use snprintf() instead. > > The main reason for doing this is not to add kernel bloat :-) but > rather to improve the reliability and maintainability of the kernel. [...] > So.. does anyone have a huge problem with doing this before I jump in? > [ Anyone willing to review for me? ] Seems mainly an issue of more appropriate coding. I think it's a win, and would be willing to double-check the changes. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 02:26:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12537 for freebsd-current-outgoing; Thu, 19 Nov 1998 02:26:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12532 for ; Thu, 19 Nov 1998 02:26:31 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998052000) with ESMTP id LAA22068; Thu, 19 Nov 1998 11:25:55 +0100 (CET) Received: from cs.uni-sb.de (acc2-200.telip.uni-sb.de [134.96.112.200]) by cs.uni-sb.de (8.9.0/1998060300) with ESMTP id LAA23551; Thu, 19 Nov 1998 11:25:52 +0100 (CET) Message-ID: <3653F2AA.D3A7CA29@cs.uni-sb.de> Date: Thu, 19 Nov 1998 11:27:54 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: Robert Nordier CC: freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader & comconsole References: <199811190902.LAA03790@ceia.nordier.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier schrieb: [...] > One difference between boot loader and the old/new boot blocks, is > that boot loader uses PC BIOS services (int 0x14) for comms; both > lots of boot blocks do direct port I/O, instead. > > The trouble with using the BIOS is that the int 0x14 services (which > tend to be used only to talk to serial printers under DOS) expect to > do hardware handshaking. Using the BIOS for configuring the serial ports gives you also only 9600 bps. I usually ran the comconsole at 19200 bps. But the original BIOS int 0x14 services seem only support up to 9600 bps. I did a small patch on the bootblocks, so that it uses the "extended communication port control" service. I don't know if good ole 386 BIOS implement this routine, but it works on my machine (I think it was introduced with the PS/2 PCs). With this service I could go up to 19200 bps (wow! but my terminal can't do more, though). I haven't noticed any problems, but now my console is twice as fast (I sometimes even do some work on the terminal) Below is the small patch Daniel Index: i386/boot2/Makefile =================================================================== RCS file: /data/cvs/src/sys/boot/i386/boot2/Makefile,v retrieving revision 1.10 diff -c -r1.10 Makefile *** Makefile 1998/11/08 15:36:34 1.10 --- Makefile 1998/11/08 20:05:28 *************** *** 13,19 **** B2SIOPRT?= 0x3f8 B2SIOFMT?= 0x3 ! B2SIODIV?= 0xc .if exists(${.OBJDIR}/../btx) BTX= ${.OBJDIR}/../btx --- 13,19 ---- B2SIOPRT?= 0x3f8 B2SIOFMT?= 0x3 ! B2SIODIV?= 0x6 .if exists(${.OBJDIR}/../btx) BTX= ${.OBJDIR}/../btx Index: i386/libi386/comconsole.c =================================================================== RCS file: /data/cvs/src/sys/boot/i386/libi386/comconsole.c,v retrieving revision 1.4 diff -c -r1.4 comconsole.c *** comconsole.c 1998/10/11 10:05:13 1.4 --- comconsole.c 1998/10/24 22:10:20 *************** *** 70,76 **** comc_started = 1; v86.ctl = 0; v86.addr = 0x14; ! v86.eax = 0xe3; /* 9600N81 */ v86.edx = BIOS_COMPORT; /* XXX take as arg, or use env var? */ v86int(); --- 70,78 ---- comc_started = 1; v86.ctl = 0; v86.addr = 0x14; ! v86.eax = 0x400; /* Extended communication port control */ ! v86.ebx = 0; /* N1 */ ! v86.ecx = 0x308; /* 19200bps, 8bits */ v86.edx = BIOS_COMPORT; /* XXX take as arg, or use env var? */ v86int(); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 03:28:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16638 for freebsd-current-outgoing; Thu, 19 Nov 1998 03:28:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-39-dbn.dial-up.net [196.34.155.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16629 for ; Thu, 19 Nov 1998 03:28:11 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id NAA05575; Thu, 19 Nov 1998 13:25:44 +0200 (SAT) From: Robert Nordier Message-Id: <199811191125.NAA05575@ceia.nordier.com> Subject: Re: /boot/loader & comconsole In-Reply-To: <3653F2AA.D3A7CA29@cs.uni-sb.de> from "D. Rock" at "Nov 19, 98 11:27:54 am" To: rock@cs.uni-sb.de (D. Rock) Date: Thu, 19 Nov 1998 13:25:40 +0200 (SAT) Cc: rnordier@nordier.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG D. Rock wrote: > Robert Nordier schrieb: > [...] > > One difference between boot loader and the old/new boot blocks, is > > that boot loader uses PC BIOS services (int 0x14) for comms; both > > lots of boot blocks do direct port I/O, instead. > > > > The trouble with using the BIOS is that the int 0x14 services (which > > tend to be used only to talk to serial printers under DOS) expect to > > do hardware handshaking. > Using the BIOS for configuring the serial ports gives you also only > 9600 bps. I usually ran the comconsole at 19200 bps. But the original > BIOS int 0x14 services seem only support up to 9600 bps. I did a > small patch on the bootblocks, so that it uses the "extended communication > port control" service. I don't know if good ole 386 BIOS implement this > routine, but it works on my machine (I think it was introduced with the > PS/2 PCs). I'm not sure, either, how many BIOSes support this. The documentation I have suggests it is PS/2-specific, though it appears it's supported on at least some of the machines here. > With this service I could go up to 19200 bps (wow! but my terminal can't > do more, though). I haven't noticed any problems, but now my console is > twice as fast (I sometimes even do some work on the terminal) > > Below is the small patch Thanks. If we're going to stick with using the BIOS, it seems worthwhile to allow this as an option. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 05:44:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01669 for freebsd-current-outgoing; Thu, 19 Nov 1998 05:44:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01653 for ; Thu, 19 Nov 1998 05:44:44 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.8.8/8.8.8) id NAA21576 for current@FreeBSD.ORG; Thu, 19 Nov 1998 13:44:00 GMT (envelope-from joe) Message-ID: <19981119134400.N14113@pavilion.net> Date: Thu, 19 Nov 1998 13:44:00 +0000 From: Josef Karthauser To: current@FreeBSD.ORG Subject: devstat_end_transaction Mail-Followup-To: current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-1273-607072 Fax: +44-1273-607073 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A while back I mentioned a bug that was beening reported on my FreeBSD3.0 machine. It looks like its back: Nov 16 02:00:01 gandalf /kernel: devstat_end_transaction: HELP!! busy_count for wd0 is < 0 (-1)! Does this mean anything to anyone? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 05:52:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02460 for freebsd-current-outgoing; Thu, 19 Nov 1998 05:52:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wanadoo.fr (smtp-out-2.wanadoo.fr [193.252.19.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02455; Thu, 19 Nov 1998 05:52:50 -0800 (PST) (envelope-from stephane@wanadoo.fr) Received: from aralia.wanadoo.fr [193.252.19.42] by wanadoo.fr for Paris Thu, 19 Nov 1998 14:50:09 +0100 (MET) Received: from dij2-112.abo.wanadoo.fr [193.252.150.112] by smtp.wanadoo.fr for Paris Thu, 19 Nov 1998 14:50:04 +0100 (MET) Received: (from stephane@localhost) by sequoia.mondomaineamoi.megalo (8.9.1/8.9.1) id OAA00545; Thu, 19 Nov 1998 14:46:58 +0100 (CET) (envelope-from stephane) Date: Thu, 19 Nov 1998 14:46:58 +0100 (CET) Message-Id: <199811191346.OAA00545@sequoia.mondomaineamoi.megalo> From: Stephane Legrand MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Robinson Cc: nate@mt.sri.com, freebsd-current@FreeBSD.ORG, freebsd-java@FreeBSD.ORG Subject: Re: green threads vs. native threads ... In-Reply-To: <199811190910.RAA01871@public.bta.net.cn> References: <199811190910.RAA01871@public.bta.net.cn> X-Mailer: VM 6.34 under 20.3 "Vatican City" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think that someone is working on POSIX thread kernel on FreeBSD (see the following message posted on comp.arch.embedded, comp.realtime and comp.programming.literate). On the web page (http://www.cornfed.com/pk/index.html), the author says : "You need FreeBSD, Latex 2.09, and noweb to make the whole thing work. For the moment, the only support you get is this: 1.Untar the distribution using a command like tar xzvf pk.tgz 2.In the root directory of the distribution, pk, type make. 3.When the build completes, you'll have two files, pk.ps in the pk/doc directory, and os in the pk/sys/src/kern directory. pk.ps is the current documentation and os is a kernel executable image that can be booted using the FreeBSD boot sequence." -------- FORWARDED MESSAGE -------- Ok, this might sound insane but what the hell. I've started an an Open-Source POSIX Threads Kernel. I'm gonna call it Pkernel (unless this name is already taken) and the system is LGPL'd which basically means you can used it in anything you want. The only thing that has to be posted back to the net are changes to files in the official distribution. So, why am I doing this? There are several reasons: 1) I've been itching to do an open-source project. I've been using GNU and FreeBSD for years and I just sort of feel like I want to. 2) While eCos has recently been released, RTEMS is available, and uCos is out there, there are two problems associated with these systems. First, I hear lots of clamoring for POSIX compatibility. Second, these systems aren't POSIX compatible AND open-source, at least not yet. eCos may get there, don't know about RTEMS cuz it's sort of behind OAR, uCos never was and its licensing has recently changed. 3) I've been looking for a good project to do some literate programming on and this seems like a good one to try it on. Ok, for those that know about Roadrunner, here's the scoop on how this fits with that. Roadrunner is my primary thing and has a lot more function to it than Pkernel. Its what I do ``during the day'' and I'm trying to make money on it. That said, Pkernel has nothing to do with Roadrunner, its a completely different code base and is open-source, no tricks, no strings attached, and it never will. In addition, in the truest sense of an open-source project, I do this on a time-available basis. So, I've got a little something ready for folks, it close to what uCos-I had. So take a peek and have fun! The distribution is located at http://www.cornfed.com/pkernel. Later, FM -- Frank W Miller Cornfed Systems Inc www.cornfed.com -------- END OF FORWARDED MESSAGE -------- Michael Robinson writes: > Nate Williams writes: > >> Would it be a moot point to ask for the FreeBSD kernel to support native > >> threads? > > > >Sure. Patches to implement them are gladly accepted. Oh, you mean > >forcing someone to implement threads in FreeBSD? Naw, that's not the > >way it's done. New features get done because someone thems to be done > >and does them. > > That's one way of looking at it. Here's another way of looking at it: > > "A good example of keeping sight of the larger picture is FreeBSD's > attitude towards its Linux emulation. It's not only very important to > us that FreeBSD continues to run Linux binaries effectively, it's also > what we suggest to those ISVs who are coming back somewhat cautiously > to this "new" Unix market and obviously want to maximize their gains > while minimizing risk. We tell them to port to Linux and not FreeBSD, > even though we'd certainly love to have native binaries for anything > and everything, and, by telling them to port to Linux first (or at > all), we are giving them the best advice on how to get access to the > widest possible segment of the free software market, one which includes > but is not limited to us." > > -Jordan Hubbard ( http://editorials.freshmeat.net/jordan980713/ ) > > As I mentioned in the part you cut out, Linux emulation is increasingly > broken in FreeBSD as more software comes to rely on Linux native threads. > If it is, in fact, "very important to us that FreeBSD continues to run > Linux binaries effectively" (whoever "us" is), I would recommend to "us" > that cooperating on a native threads solution be given a higher priority. > > Otherwise, FreeBSD will *not* be part of the free software market that > developers get access to when they follow Jordan's advice. > > -Michael Robinson > -- Stephane.Legrand@wanadoo.fr | systeme d'exploitation FreeBSD http://perso.wanadoo.fr/stephane.legrand/ | http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 05:56:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02977 for freebsd-current-outgoing; Thu, 19 Nov 1998 05:56:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.algebra.com (kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02966 for ; Thu, 19 Nov 1998 05:56:47 -0800 (PST) (envelope-from mi@aldan.algebra.com) Received: (from mi@localhost) by aldan.algebra.com (8.8.8/8.8.7) id NAA03525 for current@freebsd.org; Thu, 19 Nov 1998 13:55:26 GMT (envelope-from mi) From: Mikhail Teterin Message-Id: <199811191355.NAA03525@aldan.algebra.com> Subject: strings in the kernel (was: snprintf() in the kernel) In-Reply-To: <199811190712.XAA23068@bubba.whistle.com> from Archie Cobbs at "Nov 18, 1998 11:12:24 pm" To: current@FreeBSD.ORG Date: Thu, 19 Nov 1998 13:55:25 +0000 (GMT) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09650 for freebsd-current-outgoing; Thu, 19 Nov 1998 07:22:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09636 for ; Thu, 19 Nov 1998 07:22:22 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA05018; Thu, 19 Nov 1998 10:21:38 -0500 (EST) (envelope-from wollman) Date: Thu, 19 Nov 1998 10:21:38 -0500 (EST) From: Garrett Wollman Message-Id: <199811191521.KAA05018@khavrinen.lcs.mit.edu> To: George Michaelson Cc: freebsd-current@FreeBSD.ORG Subject: ps augxw doesn't show PPID In-Reply-To: <199811190509.PAA02120@sleet.dstc.edu.au> References: <199811190509.PAA02120@sleet.dstc.edu.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > bummer. Digital unix, Sunos, Solaris and (I think) straight BSD4.2 all > showed parent PID by default. `ps -o' is your friend. -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, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 07:35:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10784 for freebsd-current-outgoing; Thu, 19 Nov 1998 07:35:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10775; Thu, 19 Nov 1998 07:35:26 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id IAA09800; Thu, 19 Nov 1998 08:34:27 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811191534.IAA09800@panzer.plutotech.com> Subject: Re: devstat_end_transaction In-Reply-To: <19981119134400.N14113@pavilion.net> from Josef Karthauser at "Nov 19, 98 01:44:00 pm" To: joe@pavilion.net (Josef Karthauser) Date: Thu, 19 Nov 1998 08:34:27 -0700 (MST) Cc: current@FreeBSD.ORG, bde@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote... > A while back I mentioned a bug that was beening reported on my FreeBSD3.0 > machine. It looks like its back: > > Nov 16 02:00:01 gandalf /kernel: devstat_end_transaction: HELP!! busy_count for > wd0 is < 0 (-1)! > > > Does this mean anything to anyone? Yes, it means the devstat support in the IDE driver may not be completely fixed... Don't worry about the message, it's harmless. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 08:27:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16069 for freebsd-current-outgoing; Thu, 19 Nov 1998 08:27:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16050; Thu, 19 Nov 1998 08:27:03 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA10854; Thu, 19 Nov 1998 09:26:35 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA04855; Thu, 19 Nov 1998 09:26:34 -0700 Date: Thu, 19 Nov 1998 09:26:34 -0700 Message-Id: <199811191626.JAA04855@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Robinson Cc: nate@mt.sri.com, freebsd-current@FreeBSD.ORG, freebsd-java@FreeBSD.ORG Subject: Re: green threads vs. native threads ... In-Reply-To: <199811190910.RAA01871@public.bta.net.cn> References: <199811190910.RAA01871@public.bta.net.cn> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Nate Williams writes: > >> Would it be a moot point to ask for the FreeBSD kernel to support native > >> threads? > > > >Sure. Patches to implement them are gladly accepted. Oh, you mean > >forcing someone to implement threads in FreeBSD? Naw, that's not the > >way it's done. New features get done because someone thems to be done > >and does them. > > That's one way of looking at it. Here's another way of looking at it: > > "A good example of keeping sight of the larger picture is FreeBSD's > attitude towards its Linux emulation. [ Marketing type deleted ] That doesn't matter a whole lot if there isn't any technology added to keep the emulation up to date. It's one thing to say 'Linux emulation is important to us', it's a completely other thing to say 'we don't have sufficient BSD copyrighted technology to completely emulate all of the Linux kernel functions'. If you don't have, you don't have it. And, patches are gladly accepted. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 08:33:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16879 for freebsd-current-outgoing; Thu, 19 Nov 1998 08:33:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16860; Thu, 19 Nov 1998 08:33:11 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA10919; Thu, 19 Nov 1998 09:32:30 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA04879; Thu, 19 Nov 1998 09:32:29 -0700 Date: Thu, 19 Nov 1998 09:32:29 -0700 Message-Id: <199811191632.JAA04879@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Stephane Legrand Cc: Michael Robinson , nate@mt.sri.com, freebsd-current@FreeBSD.ORG, freebsd-java@FreeBSD.ORG Subject: Re: green threads vs. native threads ... In-Reply-To: <199811191346.OAA00545@sequoia.mondomaineamoi.megalo> References: <199811190910.RAA01871@public.bta.net.cn> <199811191346.OAA00545@sequoia.mondomaineamoi.megalo> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think that someone is working on POSIX thread kernel on FreeBSD (see > the following message posted on comp.arch.embedded, comp.realtime and > comp.programming.literate). >From what I read and what I downloaded, it appears that this is a replacement kernel that does threads, but what FreeBSD needs is threads added to it's current kernel, not a replacement kernel that removes all of it's existing functionality. This may grow into something that can be ported, but I doubt it given that it doesn't live within the constraints of the existing kernel environment. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 08:48:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18733 for freebsd-current-outgoing; Thu, 19 Nov 1998 08:48:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18705 for ; Thu, 19 Nov 1998 08:48:09 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA26074; Thu, 19 Nov 1998 11:47:33 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id LAA16874; Thu, 19 Nov 1998 11:47:24 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 19 Nov 1998 11:47:24 -0500 (EST) To: Robert Nordier Cc: freebsd-current@FreeBSD.ORG, adrian@ubergeeks.com Subject: Re: /boot/loader & comconsole In-Reply-To: <199811190902.LAA03790@ceia.nordier.com> References: <13907.20799.296610.678439@grasshopper.cs.duke.edu> <199811190902.LAA03790@ceia.nordier.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13908.18678.322099.46359@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier writes: > [I see Adrian has already responded to this, so I've added him to the > cc list.] > > Andrew Gallatin wrote: > There seem to be two separate, and possibly unrelated issues, here. > > The first is that the *old* boot blocks are still being used, as shown > by the actual messages displayed: >  > > I see the following on console before it hangs: > > > > >> FreeBSD BOOT @ 0x10000: 638/65532 k of memory, serial console > [ ... ] > > The corresponding line, for the new boot blocks, is simply > > >> FreeBSD/i386 BOOT > > Installing the new boot blocks at this stage is probably a good idea > (and I think this was your intention), so you'll need to do a > > disklabel -B -b /boot/boot1 -s /boot/boot2 > > (as disklabel still installs from /usr/mdec rather than /boot by > default). Thanks for reminding me. My install script read 'disklabel -B $slice' I've just fixed it to install the real new bootbocks from /boot. <...> > One difference between boot loader and the old/new boot blocks, is > that boot loader uses PC BIOS services (int 0x14) for comms; both > lots of boot blocks do direct port I/O, instead. > > The trouble with using the BIOS is that the int 0x14 services (which > tend to be used only to talk to serial printers under DOS) expect to > do hardware handshaking. > > They therefore impose fussier cabling requirements than the boot > blocks or the kernel have. (They don't work with the sloppy 2-wire, > 9-pin null modem cables I have here, for instance.) That was it! Well, sort of. The cabling was OK, but the terminal server (AlphaServer w/a Digiboard) was slightly misconfigured on the port that failed. Everything's working great now! Thanks! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 09:21:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23363 for freebsd-current-outgoing; Thu, 19 Nov 1998 09:21:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lorax.ubergeeks.com (lorax.ubergeeks.com [206.205.41.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23343 for ; Thu, 19 Nov 1998 09:21:01 -0800 (PST) (envelope-from adrian@lorax.ubergeeks.com) Received: from localhost (adrian@localhost) by lorax.ubergeeks.com (8.8.8/8.8.8) with SMTP id MAA04942; Thu, 19 Nov 1998 12:20:07 -0500 (EST) (envelope-from adrian@lorax.ubergeeks.com) Date: Thu, 19 Nov 1998 12:20:07 -0500 (EST) From: ADRIAN Filipi-Martin Reply-To: Adrian Filipi-Martin To: Robert Nordier cc: Andrew Gallatin , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader & comconsole In-Reply-To: <199811190902.LAA03790@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Nov 1998, Robert Nordier wrote: > One difference between boot loader and the old/new boot blocks, is > that boot loader uses PC BIOS services (int 0x14) for comms; both > lots of boot blocks do direct port I/O, instead. > > The trouble with using the BIOS is that the int 0x14 services (which > tend to be used only to talk to serial printers under DOS) expect to > do hardware handshaking. > > They therefore impose fussier cabling requirements than the boot > blocks or the kernel have. (They don't work with the sloppy 2-wire, > 9-pin null modem cables I have here, for instance.) Ugh... I just discovered tis this morning all by myself. Now that I have six rack mounted machines with serial consoles, I can only reboot them one at a time, because I only have one terminal. I peeked at the code for a second and quickly realized I don't have the necessary docs. Is there any chance of doing away with this limitation? If necessary, I guess I could just wire the CTS/RTS/whatever pins together so it will boot unattended, but that's... uh.. suboptimal. I guess you could call it a null-terminal cable? Adrian -- [ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 10:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00641 for freebsd-current-outgoing; Thu, 19 Nov 1998 10:11:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from under.suspicion.org (UNDER.SUSPICION.ORG [216.27.37.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00634 for ; Thu, 19 Nov 1998 10:11:12 -0800 (PST) (envelope-from ventrex@UNDER.suspicion.org) Received: from UNDER.SUSPICION.ORG (root@UNDER.SUSPICION.ORG [216.27.37.14]) by under.suspicion.org (8.9.1/8.9.1) with ESMTP id NAA57916 for ; Thu, 19 Nov 1998 13:10:23 -0500 (EST) (envelope-from ventrex@UNDER.suspicion.org) Date: Thu, 19 Nov 1998 13:10:18 -0500 (EST) From: Thomas Stromberg X-Sender: ventrex@under.suspicion.org To: freebsd-current@FreeBSD.ORG Subject: junk pointers in inetd again.. yay. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG inetd in realloc(): warning: junk pointer, too low to make sense error came up again, and then by the time I got half way through this email (3 minutes) inetd/tcpd started dying off completely. Kernel (CVSupped a few minutes before built) ============================================= FreeBSD under.suspicion.org 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed Nov 18 12:35:51 EST 1998 ventrex@under.suspicion.org:/vol/1/usr/src/sys/compile/blowntoad i386 Machine: ======== P200 MMX with 96M RAM and 200M SWAP. Settings: ========= 16 users, 1.98 load. Swap Info: ========== with just the junk pointer I was at 131M used (64%) of the 200M SWAP I had. When I had to kill off inetd because tcpd kept doing exist status 0xb and then started core dumping itself I was at 63%. Some Relevant Syslog Entries: (parsed w/ syslogcat -x) ============================= - under (Nov19/10:49:40) /kernel: swap_pager: suggest more swap space: 189 MB ** [tons of stuff taken out, now I'm testing -l -l for an ftpd option] - under (Nov19/12:52:43) ftpd: connect from localhost - under (Nov19/12:52:49) ftpd: login failure for quit (localhost) - under (Nov19/12:53:04) ftpd: connect from localhost - under (Nov19/12:53:33) ftpd: login failure for ventrex (localhost) - under (Nov19/12:53:34) ftpd: connect from localhost - under (Nov19/12:57:23) su: su to root from ventrex (/dev/ttyPk) ** [I think this is where I was getting my junk pointer errors] - under (Nov19/12:57:40) kernel: inetd(57259) owned by 0/root exited with a signal (sig11) - under (Nov19/12:58:05) kernel: inetd(57266) owned by 0/root exited with a signal (sig11) - under (Nov19/12:58:15) kernel: inetd(57269) owned by 0/root exited with a signal (sig11) ** [and now it just ALL goes wrong] - under (Nov19/13:00:19) kernel: inetd(57365) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57366) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57367) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57368) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57369) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57370) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57371) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57372) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57374) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57375) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57376) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57377) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57378) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57379) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57380) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57381) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57382) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57383) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57384) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:19) inetd[167]: /usr/local/libexec/tcpd[57365]: exit status 0xb - under (Nov19/13:00:20) kernel: inetd(57385) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57386) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:20) kernel: inetd(57387) owned by 0/root exited with a signal (sig11) - under (Nov19/13:00:19) inetd[167]: /usr/local/libexec/tcpd[57366]: exit status 0xb - under (Nov19/13:00:19) inetd[167]: /usr/local/libexec/tcpd[57367]: exit status 0xb - under (Nov19/13:00:19) inetd[167]: /usr/local/libexec/tcpd[57368]: exit status 0xb ** [tons of dying inetd and tcpd entries clipped out here before I killed inetd] - under (Nov19/13:02:55) tcplog: TCP connect: 209.115.149.34(15835)->UNDER.SUSPICION.ORG(21) - under (Nov19/13:02:58) tcplog: TCP connect: 209.115.149.34(15835)->UNDER.SUSPICION.ORG(21) - nuclear (Nov19/12:54:36) sendmail: MAA09575 has been lost! (savemail panic) - nuclear (Nov19/12:54:36) === message repeated 4 times === - nuclear (Nov19/12:54:36) sendmail: MAA09575 has been rejected but cannot be saved. ======================================================================== Thomas Stromberg | smtp -> thomas@stromberg.org System Administrator, RTC Inc. | http -> thomas.stromberg.org Cary, NC. : talk -> ventrex@stromberg.org (919) 380-9771 ext. 3210 : icq -> 17468041/ventrex "the more we know, the less we are" . irc -> ventrex@EFnet ======================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 11:12:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07580 for freebsd-current-outgoing; Thu, 19 Nov 1998 11:12:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07571 for ; Thu, 19 Nov 1998 11:12:21 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from cybcon.com (wwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id LAA28561; Thu, 19 Nov 1998 11:11:10 -0800 (PST) Date: Thu, 19 Nov 1998 11:11:10 -0800 (PST) From: Bill Woods To: Brian Feldman cc: Andrzej Bialecki , FreeBsd-Current , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am going to assume that this version works on FreeBSD in linux emulation ok? On Wed, 18 Nov 1998, Brian Feldman wrote: > On Wed, 18 Nov 1998, William Woods wrote: > > > Care to inform me where I can get 4.0 ? > > ftp://ftp.stardiv.de/pub/so4/linux/sp3/01/so40sp3_lnx_01.tar.gz > > > ---------------------------------- > > E-Mail: William Woods > > Date: 18-Nov-98 > > Time: 15:53:44 > > -->> FreeBSD 3.0 <<-- > > AIM bsdman1 > > --------------------------------- > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 11:16:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08015 for freebsd-current-outgoing; Thu, 19 Nov 1998 11:16:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from okeefe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08010 for ; Thu, 19 Nov 1998 11:16:19 -0800 (PST) (envelope-from geniusj@suarez.bestweb.net) Received: from suarez.bestweb.net (suarez.bestweb.net [209.94.100.150]) by okeefe.bestweb.net (8.9.0/8.9.0) with ESMTP id OAA09245; Thu, 19 Nov 1998 14:15:15 -0500 (EST) Date: Thu, 19 Nov 1998 14:15:17 -0500 (EST) From: Jason Dicioccio To: Bill Woods cc: Brian Feldman , Andrzej Bialecki , FreeBsd-Current , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually I htink 4.0 does not work with FreeBSD either, I beleive 3.0 is only working now although they say they are in the middle of porting it (since they have iit on every other OS) On Thu, 19 Nov 1998, Bill Woods wrote: > I am going to assume that this version works on FreeBSD in linux emulation > ok? > > On Wed, 18 Nov 1998, Brian Feldman wrote: > > > On Wed, 18 Nov 1998, William Woods wrote: > > > > > Care to inform me where I can get 4.0 ? > > > > ftp://ftp.stardiv.de/pub/so4/linux/sp3/01/so40sp3_lnx_01.tar.gz > > > > > ---------------------------------- > > > E-Mail: William Woods > > > Date: 18-Nov-98 > > > Time: 15:53:44 > > > -->> FreeBSD 3.0 <<-- > > > AIM bsdman1 > > > --------------------------------- > > > > Brian Feldman _ __ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 11:21:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08792 for freebsd-current-outgoing; Thu, 19 Nov 1998 11:21:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (tex-111.camalott.com [208.229.74.111]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08785 for ; Thu, 19 Nov 1998 11:21:28 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id NAA05282; Thu, 19 Nov 1998 13:20:18 -0600 (CST) (envelope-from joelh) To: "D. Rock" Cc: Robert Nordier , freebsd-current@FreeBSD.ORG Subject: Re: /boot/loader & comconsole References: <199811190902.LAA03790@ceia.nordier.com> <3653F2AA.D3A7CA29@cs.uni-sb.de> From: Joel Ray Holveck Date: 19 Nov 1998 13:20:17 -0600 In-Reply-To: "D. Rock"'s message of "Thu, 19 Nov 1998 11:27:54 +0100" Message-ID: <86g1bfh4lq.fsf@detlev.UUCP> Lines: 19 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Using the BIOS for configuring the serial ports gives you also only > 9600 bps. I usually ran the comconsole at 19200 bps. But the original > BIOS int 0x14 services seem only support up to 9600 bps. I did a > small patch on the bootblocks, so that it uses the "extended communication > port control" service. I don't know if good ole 386 BIOS implement this > routine, but it works on my machine (I think it was introduced with the > PS/2 PCs). It was introduced with the PS/2, but was not implemented on many clones for many years after that. Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 11:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09751 for freebsd-current-outgoing; Thu, 19 Nov 1998 11:29:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09738 for ; Thu, 19 Nov 1998 11:29:39 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.9.1) with ESMTP id OAA18675; Thu, 19 Nov 1998 14:24:52 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 19 Nov 1998 14:24:52 -0500 (EST) From: "Alok K. Dhir" To: Jason Dicioccio cc: Bill Woods , Brian Feldman , Andrzej Bialecki , FreeBsd-Current , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 4.0 works great under -current's Linux emu... Been using it for months... Al On Thu, 19 Nov 1998, Jason Dicioccio wrote: > > > Actually I htink 4.0 does not work with FreeBSD either, I beleive 3.0 is > only working now although they say they are in the middle of porting it > (since they have iit on every other OS) > > On Thu, 19 Nov 1998, Bill Woods wrote: > > > I am going to assume that this version works on FreeBSD in linux > emulation > > ok? > > > > On Wed, 18 Nov 1998, Brian Feldman wrote: > > > > > On Wed, 18 Nov 1998, William Woods wrote: > > > > > > > Care to inform me where I can get 4.0 ? > > > > > > ftp://ftp.stardiv.de/pub/so4/linux/sp3/01/so40sp3_lnx_01.tar.gz > > > > > > > ---------------------------------- > > > > E-Mail: William Woods > > > > Date: 18-Nov-98 > > > > Time: 15:53:44 > > > > -->> FreeBSD 3.0 <<-- > > > > AIM bsdman1 > > > > --------------------------------- > > > > > > Brian Feldman _ __ ___ > ___ ___ > > > green@unixhelp.org _ __ ___ | _ ) __| \ > > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) > | > > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ > |___/___/___/ > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 11:37:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10706 for freebsd-current-outgoing; Thu, 19 Nov 1998 11:37:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bashful.realminfo.com (bashful.realminfo.com [208.205.6.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10689; Thu, 19 Nov 1998 11:37:48 -0800 (PST) (envelope-from smyth@bashful.realminfo.com) Received: from localhost (smyth@localhost) by bashful.realminfo.com (8.8.7/8.8.7) with SMTP id PAA09134; Thu, 19 Nov 1998 15:52:28 -0500 Date: Thu, 19 Nov 1998 15:52:28 -0500 (EST) From: Scott Smyth To: FreeBSD Current Mailing List cc: freebsd-questions Subject: ccd with tape devices Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am a little befuddled...the example for ccd config file shows it setting up RAID with st devices (tape). Yet, when I try that, it says you must use block, which is what I would have expected, but the example through me off. Can someone confirm whether only block devices are supported at this time? thanks, scott -- Scott Smyth, Senior Developer R&D (770) 446-1332 ssmyth@realminfo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 11:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11590 for freebsd-current-outgoing; Thu, 19 Nov 1998 11:43:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11579 for ; Thu, 19 Nov 1998 11:43:22 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from cybcon.com (wwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id LAA29835; Thu, 19 Nov 1998 11:42:02 -0800 (PST) Date: Thu, 19 Nov 1998 11:42:02 -0800 (PST) From: Bill Woods To: "Alok K. Dhir" cc: Jason Dicioccio , Brian Feldman , Andrzej Bialecki , FreeBsd-Current , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seems that link that was posted here for me is REAL SSLLOOWW, even on a t3 it said it would take 800 miniutes!! Is there aneother place I could grab it from? Maby some kind soul here on this list could post it to an anon FTP site for me :) Thanks On Thu, 19 Nov 1998, Alok K. Dhir wrote: > > 4.0 works great under -current's Linux emu... Been using it for months... > > Al > > On Thu, 19 Nov 1998, Jason Dicioccio wrote: > > > > > > > Actually I htink 4.0 does not work with FreeBSD either, I beleive 3.0 is > > only working now although they say they are in the middle of porting it > > (since they have iit on every other OS) > > > > On Thu, 19 Nov 1998, Bill Woods wrote: > > > > > I am going to assume that this version works on FreeBSD in linux > > emulation > > > ok? > > > > > > On Wed, 18 Nov 1998, Brian Feldman wrote: > > > > > > > On Wed, 18 Nov 1998, William Woods wrote: > > > > > > > > > Care to inform me where I can get 4.0 ? > > > > > > > > ftp://ftp.stardiv.de/pub/so4/linux/sp3/01/so40sp3_lnx_01.tar.gz > > > > > > > > > ---------------------------------- > > > > > E-Mail: William Woods > > > > > Date: 18-Nov-98 > > > > > Time: 15:53:44 > > > > > -->> FreeBSD 3.0 <<-- > > > > > AIM bsdman1 > > > > > --------------------------------- > > > > > > > > Brian Feldman _ __ ___ > > ___ ___ > > > > green@unixhelp.org _ __ ___ | _ ) __| \ > > > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) > > | > > > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ > > |___/___/___/ > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -------------------------------------------------------------------- \||/_ > Alok K. Dhir Phone: +1.202.473.2446 oo \ > S11-151, ISGMC Email: adhir@worldbank.org L_ > The World Bank Group Washington, DC \/ > ------------------------------------------------------------------------| > "Unix _is_ user friendly - it just chooses friends selectively..." > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 12:10:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14360 for freebsd-current-outgoing; Thu, 19 Nov 1998 12:10:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14319 for ; Thu, 19 Nov 1998 12:10:19 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.255]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5831; Thu, 19 Nov 1998 21:09:38 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3652DC31.9A1754FE@rtci.com> Date: Thu, 19 Nov 1998 21:14:18 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Damon Hopkins Subject: Re: Random rebooting Cc: Current Mailing list Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Nov-98 Damon Hopkins wrote: > This sounds like what is happening to me. This machine is a AMD 486-133 > w/ 24 MB RAM no funky drivers or anything.. it has NEVER rebooted like > this before.. I don't know about the heavy network load I did some huge > file transfers yesterday on our lan and had no ill effects. Well, well, > well, what to do. >> This is on a 486DX/4-100, no L2 cache, sufficient stepping that the >> L1 cache should be OK, but I have tried it with the L1 cache >> disabled (had to hack a control register in locore.s to do it), >> with the same effect. Hmmm, unfortunately this has been happening to me the last few days... Problem being that I have tested my hardware extensively lately because NT used to BSoD me (bad memory). Everything in this box is all tested. It was a CURRENT kernel from around the 15th/16th. It appeared to be working and then as soon as I started accessing pages on the web or trying to dial in it would appear to do it's job, then all of a sudden the mouse freezes and after a few secs the whole thing reboots. I have checked all the fans and I know it's almost not a hardware problem as this kernel from yesterday (18th) works perfectly... No reset yet... Mayhaps somehow a brother of the Dying Daemons? --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 12:22:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15456 for freebsd-current-outgoing; Thu, 19 Nov 1998 12:22:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15448 for ; Thu, 19 Nov 1998 12:22:47 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sjx-ca115-49.ix.netcom.com [207.223.162.113]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id MAA12530; Thu, 19 Nov 1998 12:22:17 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id MAA13823; Thu, 19 Nov 1998 12:22:14 -0800 (PST) Date: Thu, 19 Nov 1998 12:22:14 -0800 (PST) Message-Id: <199811192022.MAA13823@silvia.hip.berkeley.edu> To: smyth@bashful.realminfo.com CC: freebsd-current@FreeBSD.ORG In-reply-to: (message from Scott Smyth on Thu, 19 Nov 1998 15:52:28 -0500 (EST)) Subject: Re: ccd with tape devices From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * I am a little befuddled...the example for ccd config file shows * it setting up RAID with st devices (tape). Yet, when I try * that, it says you must use block, which is what I would have * expected, but the example through me off. Can someone confirm * whether only block devices are supported at this time? Actually it said "sd" the old notation of SCSI disk. I changed it to "da" in -current. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 12:30:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16312 for freebsd-current-outgoing; Thu, 19 Nov 1998 12:30:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16296 for ; Thu, 19 Nov 1998 12:30:53 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id VAA27184; Thu, 19 Nov 1998 21:35:16 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 19 Nov 1998 21:35:16 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Bill Woods cc: Brian Feldman , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Nov 1998, Bill Woods wrote: > I am going to assume that this version works on FreeBSD in linux emulation > ok? Please read carefully what has been told on this list many times before jumping into conclusions. This question has been precisely answered several times. Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | http://www.freebsd.org/~picobsd/ -------------------- ~-+==---+-+ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 13:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18636 for freebsd-current-outgoing; Thu, 19 Nov 1998 13:03:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-10.ppp.wenet.net [206.15.85.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18626 for ; Thu, 19 Nov 1998 13:03:53 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id NAA04707 for ; Thu, 19 Nov 1998 13:06:14 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 19 Nov 1998 13:06:14 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: New bootloader oddities Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1480774551-911509574=:1624" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1480774551-911509574=:1624 Content-Type: TEXT/PLAIN; charset=US-ASCII Anyways, I figured I'd try out the new bootloader and see how it handles an ELF kernel. I noticed the bootloader itself doesn't detect any PnP anything. So I tried to boot the ELF kernel. It hung at the detecting PnP stuff stage. My box has a singular PCI card (video), and a ISA PnP card (shown below from an a.out kernel). The config file used for the [elf] kernel is attached. Made world yesterday, boot loader is v0.85 or something similar. Award BIOS, generic mobo, integrated aic7880. Probing for PnP devices: CSN 1 Vendor ID: CTL009c [0x9c008c0e] Serial 0x1003d0c7 Comp ID: PNP0600 [0x0006 d041] pcm1 (SB16pnp sn 0x1003d0c7) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | --0-1480774551-911509574=:1624 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=ZIPPY-SOFT-ELF Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=ZIPPY-SOFT-ELF bWFjaGluZQkJImkzODYiDQpjcHUJCSJJNTg2X0NQVSINCmlkZW50CQkiWklQ UFktU09GVFVQREFURVMtRUxGIg0KbWF4dXNlcnMJMjUNCm9wdGlvbnMJCUlO RVQJCQkjSW50ZXJORVR3b3JraW5nDQpvcHRpb25zCQlGRlMJCQkjQmVya2Vs ZXkgRmFzdCBGaWxlc3lzdGVtDQpvcHRpb25zCQkiQ09NUEFUXzQzIgkJI0Nv bXBhdGlibGUgd2l0aCBCU0QgNC4zIFtLRUVQIFRISVMhXQ0Kb3B0aW9ucwkJ U0NTSV9ERUxBWT0wCQkjQmUgcGVzc2ltaXN0aWMgYWJvdXQgSm9lIFNDU0kg ZGV2aWNlDQpvcHRpb25zCQlVQ09OU09MRQkJI0FsbG93IHVzZXJzIHRvIGdy YWIgdGhlIGNvbnNvbGUNCm9wdGlvbnMJCVVTRVJDT05GSUcJCSNib290IC1j IGVkaXRvcg0Kb3B0aW9ucwkJVklTVUFMX1VTRVJDT05GSUcJI3Zpc3VhbCBi b290IC1jIGVkaXRvcg0KY29uZmlnCQlrZXJuZWwJcm9vdCBvbiBkYTANCmNv bnRyb2xsZXIJaXNhMA0KY29udHJvbGxlcglwY2kwDQpjb250cm9sbGVyCXBu cDANCmNvbnRyb2xsZXIJZmRjMAlhdCBpc2E/IHBvcnQgIklPX0ZEMSIgYmlv IGlycSA2IGRycSAyIHZlY3RvciBmZGludHINCmRpc2sJCWZkMAlhdCBmZGMw IGRyaXZlIDANCiNkaXNrCQlmZDEJYXQgZmRjMCBkcml2ZSAxDQojdGFwZQkJ ZnQwCWF0IGZkYzAgZHJpdmUgMg0KY29udHJvbGxlcglhaGMwDQpjb250cm9s bGVyCXNjYnVzMCBhdCBhaGMwICAgICAgICAgICMgU2luZ2xlIGJ1cyBkZXZp Y2UNCmRpc2sJCWRhMCBhdCBzY2J1czAgdGFyZ2V0IDAgdW5pdCAwDQpkaXNr CQlkYTEgYXQgc2NidXMwIHRhcmdldCAxIHVuaXQgMA0KZGV2aWNlCQljZDAJ I09ubHkgbmVlZCBvbmUgb2YgdGhlc2UsIHRoZSBjb2RlIGR5bmFtaWNhbGx5 IGdyb3dzDQpkZXZpY2UJCXNjMAlhdCBpc2E/IHBvcnQgIklPX0tCRCIgdHR5 IGlycSAxIHZlY3RvciBzY2ludHINCmRldmljZQkJbnB4MAlhdCBpc2E/IHBv cnQgIklPX05QWCIgaXJxIDEzIHZlY3RvciBucHhpbnRyDQpkZXZpY2UJCWFw bTAgICAgYXQgaXNhPwkJIyBBZHZhbmNlZCBQb3dlciBNYW5hZ2VtZW50DQpk ZXZpY2UJCXNpbzAJYXQgaXNhPyBwb3J0ICJJT19DT00xIiB0dHkgaXJxIDQg dmVjdG9yIHNpb2ludHINCmRldmljZQkJc2lvMQlhdCBpc2E/IHBvcnQgIklP X0NPTTIiIHR0eSBpcnEgMyB2ZWN0b3Igc2lvaW50cg0KI2RldmljZQkJc2lv MglhdCBpc2E/IGRpc2FibGUgcG9ydCAiSU9fQ09NMyIgdHR5IGlycSA1IHZl Y3RvciBzaW9pbnRyDQojZGV2aWNlCQlzaW8zCWF0IGlzYT8gZGlzYWJsZSBw b3J0ICJJT19DT000IiB0dHkgaXJxIDkgdmVjdG9yIHNpb2ludHINCmNvbnRy b2xsZXIgICAgICBwcGJ1czANCmNvbnRyb2xsZXIgICAgICBwcGMwICAgIGF0 IGlzYT8gcG9ydCA/IHR0eSBpcnEgNyB2ZWN0b3IgcHBjaW50cg0KZGV2aWNl ICAgICAgICAgIG5scHQwICAgYXQgcHBidXM/DQpkZXZpY2UgICAgICAgICAg cHBpMCAgICBhdCBwcGJ1cz8NCmRldmljZSBlZDAgYXQgaXNhPyBwb3J0IDB4 MjgwIG5ldCBpcnEgMTAgaW9tZW0gMHhkODAwMCB2ZWN0b3IgZWRpbnRyDQpk ZXZpY2UgZXAwIGF0IGlzYT8gcG9ydCAweDMwMCBuZXQgaXJxIDEwIHZlY3Rv ciBlcGludHINCiNjb250cm9sbGVyICAgICAgc25kMA0KI2RldmljZSBzYjAg ICAgICBhdCBpc2E/IHBvcnQgMHgyMjAgaXJxIDUgZHJxIDEgdmVjdG9yIHNi aW50cg0KI2RldmljZSBzYnh2aTAgICBhdCBpc2E/IGRycSA1DQojZGV2aWNl IHNibWlkaTAgIGF0IGlzYT8gcG9ydCAweDMzMA0KI2RldmljZSBvcGwwICAg ICBhdCBpc2E/IHBvcnQgMHgzODgNCmRldmljZQlwY20wIGF0IGlzYT8gcG9y dCA/IHR0eSBpcnEgMTAgZHJxIDEgdmVjdG9yIHBjbWludHIJI0x1aWdpJ3Mg U291bmQgY29kZQ0KZGV2aWNlIAlwY2EwIGF0IGlzYT8gcG9ydCBJT19USU1F UjEgdHR5DQpvcHRpb25zCQlLVFJBQ0UJCQkja2VybmVsIHRyYWNpbmcNCm9w dGlvbnMJCVNZU1ZTSE0NCm9wdGlvbnMJCVNZU1ZNU0cNCm9wdGlvbnMJCVNZ U1ZTRU0NCm9wdGlvbnMgICAgICAgICBJTkNMVURFX0NPTkZJR19GSUxFICAg ICAjIEluY2x1ZGUgdGhpcyBmaWxlIGluIGtlcm5lbA0Kb3B0aW9ucwkJVVNF Ul9MRFQNCm9wdGlvbnMJCVBFUkZNT04NCm9wdGlvbnMJCVFVT1RBDQpvcHRp b25zCQkiQVVUT19FT0lfMSINCm9wdGlvbnMJCSJBVVRPX0VPSV8yIg0Kb3B0 aW9ucwkJTUFYQ09OUz0yNAkJIyBudW1iZXIgb2YgdmlydHVhbCBjb25zb2xl cw0Kb3B0aW9ucwkJQUhDX0FMTE9XX01FTUlPDQpvcHRpb25zICAgICAgICAg IkVYVDJGUyINCm9wdGlvbnMgICAgICAgICAiTUFYRFNJWj0oMjU2KjEwMjQq MTAyNCkiDQpvcHRpb25zICAgICAgICAgIkRGTERTSVo9KDY0KjEwMjQqMTAy NCkiDQpvcHRpb25zCQkiVk04NiINCm9wdGlvbnMgICAgICAgICBEREINCnBz ZXVkby1kZXZpY2UgICBicGZpbHRlcgk0CSNCZXJrZWxleSBwYWNrZXQgZmls dGVyDQpwc2V1ZG8tZGV2aWNlICAgc3BlYWtlciAgICAgICAgIAkjUGxheSBJ Qk0gQkFTSUMtc3R5bGUgbm9pc2VzIG91dCB5b3VyIHNwZWFrZXINCnBzZXVk by1kZXZpY2UgICB2biAgICAgICAgICAgICAgCSNWbm9kZSBkcml2ZXIgKHR1 cm5zIGEgZmlsZSBpbnRvIGEgZGV2aWNlKQ0KcHNldWRvLWRldmljZSAgIHNu cCAgICAgMyAgICAgICAJI1Nub29wIGRldmljZSAtIHRvIGxvb2sgYXQgcHR5 L3Z0eS9ldGMuLg0KcHNldWRvLWRldmljZQlsb29wCQkJIw0KcHNldWRvLWRl dmljZQlldGhlcgkJCSMNCnBzZXVkby1kZXZpY2UJc2wJMQkJIw0KcHNldWRv LWRldmljZQlwcHAJMQkJIw0KcHNldWRvLWRldmljZQl0dW4JMQkJIw0KcHNl dWRvLWRldmljZQlwdHkJMjQJCSMNCnBzZXVkby1kZXZpY2UJZ3ppcAkJCSMg RXhlYyBnemlwcGVkIGEub3V0J3MNCiNvcHRpb25zCQkiQ0xLX1VTRV9JODI1 NF9DQUxJQlJBVElPTiINCiNvcHRpb25zCQkiQ0xLX1VTRV9UU0NfQ0FMSUJS QVRJT04iDQpvcHRpb25zCQkiUDEwMDNfMUIiDQpvcHRpb25zCQkiX0tQT1NJ WF9QUklPUklUWV9TQ0hFRFVMSU5HIg0Kb3B0aW9ucwkJIl9LUE9TSVhfVkVS U0lPTj0xOTkzMDlMIg0Kb3B0aW9ucwkJU09GVFVQREFURVMNCm9wdGlvbnMJ CVBRX0xBUkdFQ0FDSEUJIyBDb2xvciBmb3IgNTEyay8xNmsgY2FjaGUNCg== --0-1480774551-911509574=:1624-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 13:47:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23279 for freebsd-current-outgoing; Thu, 19 Nov 1998 13:47:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eterna.binary.net (eterna.binary.net [12.13.120.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23266 for ; Thu, 19 Nov 1998 13:47:49 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id PAA19901 for ; Thu, 19 Nov 1998 15:46:31 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id PAA10573 for freebsd-current@freebsd.org; Thu, 19 Nov 1998 15:47:20 -0600 (CST) Message-ID: <19981119164720.A28892@rtfm.net> Date: Thu, 19 Nov 1998 16:47:20 -0500 From: Nathan Dorfman To: freebsd-current@FreeBSD.ORG Subject: linuxdoom and pcm0 (Re: pcm0 A/V sync off after unusual behavior w/xanim) References: <19981116011537.A1173@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981116011537.A1173@top.worldcontrol.com>; from brian@worldcontrol.com on Mon, Nov 16, 1998 at 01:15:37AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Similar problem with linuxdoom, the sound effects are always considerably late. Again, no problem with snd0. Doom isn't too essential so I kinda forgot about it ,but its been there for a while. -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 13:54:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24452 for freebsd-current-outgoing; Thu, 19 Nov 1998 13:54:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadow.worldbank.org (shadow.worldbank.org [138.220.104.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24350 for ; Thu, 19 Nov 1998 13:53:57 -0800 (PST) (envelope-from adhir@worldbank.org) Received: from localhost (adhir@localhost) by shadow.worldbank.org (8.9.1/8.9.1) with ESMTP id QAA21030; Thu, 19 Nov 1998 16:52:21 -0500 (EST) (envelope-from adhir@worldbank.org) X-Authentication-Warning: shadow.worldbank.org: adhir owned process doing -bs Date: Thu, 19 Nov 1998 16:52:21 -0500 (EST) From: "Alok K. Dhir" To: Nathan Dorfman cc: freebsd-current@FreeBSD.ORG Subject: Re: linuxdoom and pcm0 (Re: pcm0 A/V sync off after unusual behavior w/xanim) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also happens in xgal... On Thu, 19 Nov 1998, Nathan Dorfman wrote: > Similar problem with linuxdoom, the sound effects are always considerably > late. Again, no problem with snd0. Doom isn't too essential so I kinda > forgot about it ,but its been there for a while. > -- > ________________ ___________________________________________ > / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* > / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing > / finger for PGP key \ religion to the pope?" -Jamie Bowden > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -------------------------------------------------------------------- \||/_ Alok K. Dhir Phone: +1.202.473.2446 oo \ S11-151, ISGMC Email: adhir@worldbank.org L_ The World Bank Group Washington, DC \/ ------------------------------------------------------------------------| "Unix _is_ user friendly - it just chooses friends selectively..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 13:57:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24824 for freebsd-current-outgoing; Thu, 19 Nov 1998 13:57:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-60-dbn.dial-up.net [196.34.155.124]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24791 for ; Thu, 19 Nov 1998 13:57:21 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA07970; Thu, 19 Nov 1998 23:54:47 +0200 (SAT) From: Robert Nordier Message-Id: <199811192154.XAA07970@ceia.nordier.com> Subject: Re: /boot/loader & comconsole In-Reply-To: from ADRIAN Filipi-Martin at "Nov 19, 98 12:20:07 pm" To: adrian@ubergeeks.com Date: Thu, 19 Nov 1998 23:54:45 +0200 (SAT) Cc: rnordier@nordier.com, gallatin@cs.duke.edu, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ADRIAN Filipi-Martin wrote: > On Thu, 19 Nov 1998, Robert Nordier wrote: > > > They therefore impose fussier cabling requirements than the boot > > blocks or the kernel have. (They don't work with the sloppy 2-wire, > > 9-pin null modem cables I have here, for instance.) > > Ugh... I just discovered tis this morning all by myself. Now > that I have six rack mounted machines with serial consoles, I can only > reboot them one at a time, because I only have one terminal. > > I peeked at the code for a second and quickly realized I don't > have the necessary docs. Is there any chance of doing away with this > limitation? If necessary, I guess I could just wire the CTS/RTS/whatever > pins together so it will boot unattended, but that's... uh.. suboptimal. > I guess you could call it a null-terminal cable? Probably sensible to avoid the BIOS services then: other people are sure to be bitten by this sooner or later. If you're up for it, I can send you some patches to try in a day or two (most likely using Joerg's serial.S routines from biosboot: the boot2 stuff makes use of different calling conventions to save space). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 14:22:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28150 for freebsd-current-outgoing; Thu, 19 Nov 1998 14:22:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28135 for ; Thu, 19 Nov 1998 14:22:29 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA29388; Thu, 19 Nov 1998 14:21:10 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA09145; Thu, 19 Nov 1998 14:21:09 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 19 Nov 1998 14:21:09 -0800 (PST) Message-Id: <199811192221.OAA09145@vashon.polstra.com> To: bartol@salk.edu Subject: Re: Problem with amd (was: NFS problems in -current) Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Tom Bartol wrote: > > O.K. Here's another big clue. I had been mounting using amd. If I mount > without amd then all is well and performance is much better also. I now > get ~9MBps instead of ~4MBps over a 100BT segment. Aha! The new amd uses different options to select the protocol for NFS. I bet you still have an old amd.map file. For the new amd, the desired options are "proto=udp,vers=2". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 14:23:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28289 for freebsd-current-outgoing; Thu, 19 Nov 1998 14:23:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28201; Thu, 19 Nov 1998 14:22:55 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id OAA18068; Thu, 19 Nov 1998 14:21:55 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 19 Nov 1998 14:21:54 -0800 (PST) From: Doug White To: Scott Smyth cc: FreeBSD Current Mailing List , freebsd-questions Subject: Re: ccd with tape devices In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Nov 1998, Scott Smyth wrote: > I am a little befuddled...the example for ccd config file shows > it setting up RAID with st devices (tape). No, I think you misread it. RAID stands for Redundant Array of Inexpensive Disks, not Tapes ... Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 14:23:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28354 for freebsd-current-outgoing; Thu, 19 Nov 1998 14:23:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28341 for ; Thu, 19 Nov 1998 14:23:20 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id RAA13858; Thu, 19 Nov 1998 17:22:42 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA14557; Thu, 19 Nov 1998 17:22:42 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id RAA26312; Thu, 19 Nov 1998 17:22:42 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199811192222.RAA26312@bb01f39.unx.sas.com> Subject: Re: page fault when rm'ing on ccd-partition In-Reply-To: From "Justin T. Gibbs" at "Nov 18, 98 10:03:26 pm" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Thu, 19 Nov 1998 17:22:41 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Just to pipe in on this conversation, my 3.0-CURRENT machine panic'd last night while I was rm'ing some old snaps in my /pub directory... kernel from late monday evenning. FreeBSD FreeBSD.pc.sas.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Mon Nov 16 22:46:54 EST 1998 root@FreeBSD.pc.sas.com:/usr/src/sys/compile/FreeBSD i386 bad block -105597952, ino 1325574 dev=0x1503, bno=-1267041689 bsize=8192, size=8192, fs=/pub panic: ffs_blkfree: bad size This machine had all it's disks fsck'd less than 24hrs before the panic... $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 254063 41440 192298 18% / /dev/wd0s1g 3054702 852789 1957537 30% /mirror /dev/wd0s1f 2032623 848212 1021802 45% /usr /dev/wd0s1e 508143 15258 452234 3% /var procfs 4 4 0 100% /proc /dev/ccd0a 1077775 1 991552 0% /snap /dev/ccd0b 1077775 398105 593448 40% /usr/obj /dev/ccd0d 8622315 5816175 2116355 73% /pub pid143@FreeBSD:/u 0 0 0 100% /u pid143@FreeBSD:/nfs 0 0 0 100% /nfs Thanks for listening :-) John > In article <19981118113805.A5521@foobar.franken.de> you wrote: > > Hi, > > > > I'm experiencing problems on a (non-local) 3.0-19980916-SNAP > > This bug was fixed before 3.0R went out the door. You need to > upgrade to 3.0R or a later snapshot. > > - -- > Justin > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ------------------------------ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 14:30:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29157 for freebsd-current-outgoing; Thu, 19 Nov 1998 14:30:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pau-amma.whistle.com (s205m64.whistle.com [207.76.205.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29147 for ; Thu, 19 Nov 1998 14:30:13 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.1/8.9.1) id OAA13755 for current@FreeBSD.ORG; Thu, 19 Nov 1998 14:27:16 -0800 (PST) (envelope-from dhw) Date: Thu, 19 Nov 1998 14:27:16 -0800 (PST) From: David Wolfskill Message-Id: <199811192227.OAA13755@pau-amma.whistle.com> Subject: Re: Problem with amd (was: NFS problems in -current) Cc: current@FreeBSD.ORG In-Reply-To: <199811192221.OAA09145@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: John Polstra >Date: Thu, 19 Nov 1998 14:21:09 -0800 (PST) >Aha! The new amd uses different options to select the protocol for >NFS. I bet you still have an old amd.map file. For the new amd, >the desired options are "proto=udp,vers=2". How... interesting. So, any recommended strategy for using the *same* amd maps for machines that use both versions of amd? I really like consistency in the maps; that's why I use NIS to provide them. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 14:46:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01340 for freebsd-current-outgoing; Thu, 19 Nov 1998 14:46:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01334 for ; Thu, 19 Nov 1998 14:46:55 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id OAA29507; Thu, 19 Nov 1998 14:46:26 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id OAA09993; Thu, 19 Nov 1998 14:46:26 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 19 Nov 1998 14:46:26 -0800 (PST) Message-Id: <199811192246.OAA09993@vashon.polstra.com> To: dhw@whistle.com Subject: Re: Problem with amd (was: NFS problems in -current) Newsgroups: polstra.freebsd.current In-Reply-To: <199811192227.OAA13755@pau-amma.whistle.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811192227.OAA13755@pau-amma.whistle.com>, David Wolfskill wrote: > >Aha! The new amd uses different options to select the protocol for > >NFS. I bet you still have an old amd.map file. For the new amd, > >the desired options are "proto=udp,vers=2". > > How... interesting. > > So, any recommended strategy for using the *same* amd maps for machines > that use both versions of amd? You might be able to get away with the hack of putting both the old-style options and the new ones in the amd.map files. I think amd just ignores the options it doesn't recognize. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 14:57:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03098 for freebsd-current-outgoing; Thu, 19 Nov 1998 14:57:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from acetylene.vapornet.net (acetylene.vapornet.net [209.100.218.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03088 for ; Thu, 19 Nov 1998 14:57:21 -0800 (PST) (envelope-from john@vapornet.net) Received: from nitromethane.vapornet.net (vapornet.xnet.com. [205.243.141.107]) by acetylene.vapornet.net (8.9.1/8.9.1/VaporServer C1.3.1) with ESMTP id QAA07741 for ; Thu, 19 Nov 1998 16:57:00 -0600 (CST) (envelope from: john@vapornet.net) Received: from habanero.chili-pepper.net (habanero.chili-pepper.net [192.168.0.11]) by nitromethane.vapornet.net (8.9.1/8.9.1/VaporServer v1.3.1) with ESMTP id QAA25353 for ; Thu, 19 Nov 1998 16:57:06 -0600 (CST) (envelope from: john@vapornet.net) Received: (from john@localhost) by habanero.chili-pepper.net (8.9.1/8.9.1/VaporClient v3.1) id QAA16798; Thu, 19 Nov 1998 16:56:41 -0600 (CST) (envelope from: john@vapornet.net) From: John Preisler MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 19 Nov 1998 16:56:41 -0600 (CST) To: freebsd-current@FreeBSD.ORG Subject: upgrading and pam X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13908.41339.895733.695465@habanero.chili-pepper.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've been trying to upgrade an older 3.0-current box by rebuilding from source but no matter what i do, it stops at ===> libpam/modules ===> libpam/modules/pam_cleartext_pass_ok cc -O -pipe -I/usr/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libpam/modules/pam_cleartext_pass_ok/pam_cleartext_pass_ok.c cc -O -pipe -I/usr/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall -I/usr/obj/aout/usr/src/tmp/usr/include -shared -o pam_cleartext_pass_ok.so pam_cleartext_pass_ok.o -lskey -lgcc_pic ld: -lskey: no match *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 I've tried altering the makefile so that libskey gets built before libpam but that didnt help any. suggestions? -j To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 15:07:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04598 for freebsd-current-outgoing; Thu, 19 Nov 1998 15:07:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04582 for ; Thu, 19 Nov 1998 15:07:15 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id PAA29639; Thu, 19 Nov 1998 15:06:33 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id PAA10089; Thu, 19 Nov 1998 15:06:20 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 19 Nov 1998 15:06:20 -0800 (PST) Message-Id: <199811192306.PAA10089@vashon.polstra.com> To: john@vapornet.net Subject: Re: upgrading and pam Newsgroups: polstra.freebsd.current In-Reply-To: <13908.41339.895733.695465@habanero.chili-pepper.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <13908.41339.895733.695465@habanero.chili-pepper.net>, John Preisler wrote: > > Hello, > > I've been trying to upgrade an older 3.0-current box by rebuilding > from source but no matter what i do, it stops at > > ===> libpam/modules > ===> libpam/modules/pam_cleartext_pass_ok > cc -O -pipe -I/usr/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libpam/modules/pam_cleartext_pass_ok/pam_cleartext_pass_ok.c > cc -O -pipe -I/usr/src/lib/libpam/modules/pam_cleartext_pass_ok/../../../../contrib/libpam/libpam/include -fpic -Wall -I/usr/obj/aout/usr/src/tmp/usr/include -shared -o pam_cleartext_pass_ok.so pam_cleartext_pass_ok.o -lskey -lgcc_pic > ld: -lskey: no match > *** Error code 1 Eeek. I believe you've found a bug that I created. Sorry! I'll commit a fix forthwith. > I've tried altering the makefile so that libskey gets built before > libpam but that didnt help any. suggestions? You're on the right track, but the same change has to be made in "src/Makefile.inc1" too, in the "libraries:" target. Thanks for reporting this problem! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 15:09:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04892 for freebsd-current-outgoing; Thu, 19 Nov 1998 15:09:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04876 for ; Thu, 19 Nov 1998 15:08:58 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA21302; Fri, 20 Nov 1998 09:38:18 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id JAA03128; Fri, 20 Nov 1998 09:38:18 +1030 (CST) Message-ID: <19981120093817.K467@freebie.lemis.com> Date: Fri, 20 Nov 1998 09:38:17 +1030 From: Greg Lehey To: Archie Cobbs , freebsd-current@FreeBSD.ORG Subject: Re: snprintf() in the kernel References: <199811190712.XAA23068@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199811190712.XAA23068@bubba.whistle.com>; from Archie Cobbs on Wed, Nov 18, 1998 at 11:12:24PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 18 November 1998 at 23:12:24 -0800, Archie Cobbs wrote: > I would like to do the following: > > 1. Add snprintf() to kern/subr_prf.c > > 2. Change all appropriate uses of sprintf() and/or strcat() > to use snprintf() instead. > > The main reason for doing this is not to add kernel bloat :-) but > rather to improve the reliability and maintainability of the kernel. > > In fact, the total byte count may even go down due to the several > instances in the code that are forced to do their own bounds checking > (the changes to subr_prf.c are minimal). > > Cases where it's "obvious" that the buffer can't overflow will > be left alone, for some conservative definition of "obvious". > > A typical example: > > ... > > I count 131 files that use sprintf() and 28 that use strcat(), so > this will touch a lot of files (but hopefully for the better). I'm very much in favour. The code I need to do bounds checking in vinum is some of the ugliest I've seen. > So.. does anyone have a huge problem with doing this before I jump in? > [ Anyone willing to review for me? ] I'll take a look. Are you going to implement %qd while you're at it? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 16:14:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14350 for freebsd-current-outgoing; Thu, 19 Nov 1998 16:14:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14342 for ; Thu, 19 Nov 1998 16:14:25 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id QAA18595; Thu, 19 Nov 1998 16:13:49 -0800 (PST) Date: Thu, 19 Nov 1998 16:13:50 -0800 (PST) From: Tom Bartol To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) In-Reply-To: <199811192221.OAA09145@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for the info. I'll try it out tomorrow. If I want NFSv3 with UDP I suppose I would say: proto=udp,vers=3 correct? BTW, I can't find these options documented in amd(8) amd.conf(5) or mount_nfs(8). Any place else I should be looking? Tom On Thu, 19 Nov 1998, John Polstra wrote: > In article , > Tom Bartol wrote: > > > > O.K. Here's another big clue. I had been mounting using amd. If I mount > > without amd then all is well and performance is much better also. I now > > get ~9MBps instead of ~4MBps over a 100BT segment. > > Aha! The new amd uses different options to select the protocol for > NFS. I bet you still have an old amd.map file. For the new amd, > the desired options are "proto=udp,vers=2". > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Nobody ever went broke underestimating the taste of the American public." > -- H. L. Mencken > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 16:18:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14791 for freebsd-current-outgoing; Thu, 19 Nov 1998 16:18:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14784 for ; Thu, 19 Nov 1998 16:18:25 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id QAA29898; Thu, 19 Nov 1998 16:17:52 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id QAA10401; Thu, 19 Nov 1998 16:17:49 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 19 Nov 1998 16:17:49 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Tom Bartol Subject: Re: Problem with amd (was: NFS problems in -current) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Nov-98 Tom Bartol wrote: > > Thanks for the info. I'll try it out tomorrow. If I want NFSv3 with UDP > I suppose I would say: > > proto=udp,vers=3 > > correct? Correct. I had problems using NFSv3 the last time I tried it, but that was several months ago. Maybe it's better now. > BTW, I can't find these options documented in amd(8) amd.conf(5) or > mount_nfs(8). Any place else I should be looking? Not that I know of. The documentation is pretty broken. I had a very hard time even finding the right options in the sources. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 16:28:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15773 for freebsd-current-outgoing; Thu, 19 Nov 1998 16:28:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15766 for ; Thu, 19 Nov 1998 16:28:13 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id QAA03479; Thu, 19 Nov 1998 16:29:00 -0800 (PST) Message-Id: <199811200029.QAA03479@root.com> To: "John W. DeBoskey" cc: gibbs@narnia.plutotech.com (Justin T. Gibbs), freebsd-current@FreeBSD.ORG Subject: Re: page fault when rm'ing on ccd-partition In-reply-to: Your message of "Thu, 19 Nov 1998 17:22:41 EST." <199811192222.RAA26312@bb01f39.unx.sas.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 19 Nov 1998 16:29:00 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just to pipe in on this conversation, my 3.0-CURRENT machine >panic'd last night while I was rm'ing some old snaps in my >/pub directory... kernel from late monday evenning. > >FreeBSD FreeBSD.pc.sas.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: > Mon Nov 16 22:46:54 EST 1998 > root@FreeBSD.pc.sas.com:/usr/src/sys/compile/FreeBSD i386 > > >bad block -105597952, ino 1325574 dev=0x1503, bno=-1267041689 > bsize=8192, size=8192, fs=/pub >panic: ffs_blkfree: bad size ...not -current enough. There was a bug that was fixed a day after you built the above kernel that caused the 'bad size' panic. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 16:34:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16574 for freebsd-current-outgoing; Thu, 19 Nov 1998 16:34:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16569 for ; Thu, 19 Nov 1998 16:34:24 -0800 (PST) (envelope-from bartol@salk.edu) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with SMTP id QAA19149; Thu, 19 Nov 1998 16:33:23 -0800 (PST) Date: Thu, 19 Nov 1998 16:33:24 -0800 (PST) From: Tom Bartol To: John Polstra cc: current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Nov 1998, John Polstra wrote: > On 20-Nov-98 Tom Bartol wrote: > > > > Thanks for the info. I'll try it out tomorrow. If I want NFSv3 with UDP > > I suppose I would say: > > > > proto=udp,vers=3 > > > > correct? > > Correct. I had problems using NFSv3 the last time I tried it, but > that was several months ago. Maybe it's better now. > I'm using NFSv3 right now (without amd) and it's been excellent -- ~9MBps for file writes over 100BT, half duplex at the moment to our Auspex file server. We're waiting on a patch from Auspex to allow us to go full duplex. I've tried full duplex between FreeBSD machines with NFSv3 and I get ~11MBps file writes!! Which is basically full wire speed. I LOVE FreeBSD! > > BTW, I can't find these options documented in amd(8) amd.conf(5) or > > mount_nfs(8). Any place else I should be looking? > > Not that I know of. The documentation is pretty broken. I had a > very hard time even finding the right options in the sources. > > John > --- Perhaps I can find some time to at least help with the documentation, instead of always complaining about this thing or that. I'll look at the amd source and texinfo in /usr/src/contrib/amd and see what I can do... Thanks again for your help, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 16:59:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19382 for freebsd-current-outgoing; Thu, 19 Nov 1998 16:59:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19374 for ; Thu, 19 Nov 1998 16:59:43 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id QAA22544; Thu, 19 Nov 1998 16:58:04 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma022537; Thu, 19 Nov 98 16:57:48 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id QAA29023; Thu, 19 Nov 1998 16:57:47 -0800 (PST) From: Archie Cobbs Message-Id: <199811200057.QAA29023@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <19981120093817.K467@freebie.lemis.com> from Greg Lehey at "Nov 20, 98 09:38:17 am" To: grog@lemis.com (Greg Lehey) Date: Thu, 19 Nov 1998 16:57:47 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey writes: > > I count 131 files that use sprintf() and 28 that use strcat(), so > > this will touch a lot of files (but hopefully for the better). > > I'm very much in favour. The code I need to do bounds checking in > vinum is some of the ugliest I've seen. Cool.. I know the feeling. The only subtle gotcha with snprintf() is that it returns the number of characters that *would* have been printed, not the number that actually were printed. So you can't count on the return value being less than the buffer size. > > So.. does anyone have a huge problem with doing this before I jump in? > > [ Anyone willing to review for me? ] > > I'll take a look. Are you going to implement %qd while you're at it? One thing at a time.. :-) Thanks for the offers from you and Robert Nordier to review, you folks will hear from me soon.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 17:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22322 for freebsd-current-outgoing; Thu, 19 Nov 1998 17:29:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep2-orange.clear.net.nz (fep2-orange.clear.net.nz [203.97.32.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22315 for ; Thu, 19 Nov 1998 17:28:56 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep2-orange.clear.net.nz (1.5/1.9) with ESMTP id OAA18871; Fri, 20 Nov 1998 14:27:43 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id OAA17562; Fri, 20 Nov 1998 14:27:29 +1300 (NZDT) Message-ID: <19981120142729.B17506@clear.co.nz> Date: Fri, 20 Nov 1998 14:27:29 +1300 From: Joe Abley To: Bill Woods , "Alok K. Dhir" Cc: Jason Dicioccio , Brian Feldman , Andrzej Bialecki , FreeBsd-Current , Doug White , jabley@clear.co.nz Subject: Re: StarOffice 5.0 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Bill Woods on Thu, Nov 19, 1998 at 11:42:02AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 19, 1998 at 11:42:02AM -0800, Bill Woods wrote: > Seems that link that was posted here for me is REAL SSLLOOWW, even on a t3 > it said it would take 800 miniutes!! Encourage your provider to provision a direct circuit to Germany :) In fact, encourage your provider to purchase _any_ international circuits. It's about time US providers started paying for access to content outside the US, instead of charging offshore providers for it :( -- Joe Abley Tel +64 9 912-4065, Fax +64 9 912-5008 Network Architect, CLEAR Communications Ltd http://www.clear.net.nz/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 17:31:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22584 for freebsd-current-outgoing; Thu, 19 Nov 1998 17:31:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22579 for ; Thu, 19 Nov 1998 17:31:48 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id SAA27659; Thu, 19 Nov 1998 18:31:19 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd027576; Thu Nov 19 18:31:12 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id SAA23560; Thu, 19 Nov 1998 18:31:09 -0700 (MST) From: Terry Lambert Message-Id: <199811200131.SAA23560@usr09.primenet.com> Subject: Re: /boot/loader & comconsole To: rnordier@nordier.com (Robert Nordier) Date: Fri, 20 Nov 1998 01:31:08 +0000 (GMT) Cc: rock@cs.uni-sb.de, rnordier@nordier.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199811191125.NAA05575@ceia.nordier.com> from "Robert Nordier" at Nov 19, 98 01:25:40 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Using the BIOS for configuring the serial ports gives you also only > > 9600 bps. I usually ran the comconsole at 19200 bps. But the original > > BIOS int 0x14 services seem only support up to 9600 bps. I did a > > small patch on the bootblocks, so that it uses the "extended communication > > port control" service. I don't know if good ole 386 BIOS implement this > > routine, but it works on my machine (I think it was introduced with the > > PS/2 PCs). > > I'm not sure, either, how many BIOSes support this. The documentation I > have suggests it is PS/2-specific, though it appears it's supported on > at least some of the machines here. You can determine support by the return value from the call. Most BIOS support up to 115k now, at the expense of some of the lower baud rates. See the Ralf Brown list for details, or any one of dozens of books on serial I/O on the PC. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 18:40:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29083 for freebsd-current-outgoing; Thu, 19 Nov 1998 18:40:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29077 for ; Thu, 19 Nov 1998 18:40:02 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id SAA00363; Thu, 19 Nov 1998 18:39:33 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id SAA17040; Thu, 19 Nov 1998 18:39:33 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 19 Nov 1998 18:39:33 -0800 (PST) Message-Id: <199811200239.SAA17040@vashon.polstra.com> To: garman@earthling.net Subject: Re: more dying daemons Newsgroups: polstra.freebsd.current In-Reply-To: <199811190247.SAA25805@hub.freebsd.org> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811190247.SAA25805@hub.freebsd.org>, wrote: > while sitting here trying to find a common thread through all this > mess... > > it appears to happen only with servers that fork() copies of themselves > on incoming requests. > > inetd does this, samba does this, and sshd does this. consequently, > inetd dies, samba dies, and sshd dies :) > > however, servers that *don't* fork off a new connection on incoming > requests don't die. This comment nudged my feeble memory and caused me to notice that there are some definite similarities between this problem and the "can't build Modula-3 on an SMP system" bug which I watched Tor Egge fix a few months ago. I won't recap all the details here, but it had to do with forking and corrupted memory and SMP. (Somebody remarked that the dying daemon problem went away for him when he switched to SMP.) Someone who is experiencing this problem please try a very simple experiment for me. On a freshly rebooted system (to ensure a clean slate), do this: sysctl -w kern.fast_vfork=0 Better yet, add it to your /etc/rc.local file too, so that you won't forget to do it the next time you reboot. Then see if the dying daemon problem still happens, and let me know. This is just a hunch, but it's an easy experiment to try. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 20:31:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09133 for freebsd-current-outgoing; Thu, 19 Nov 1998 20:31:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09128 for ; Thu, 19 Nov 1998 20:31:23 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id UAA04139; Thu, 19 Nov 1998 20:30:50 -0800 (PST) (envelope-from obrien) Message-ID: <19981119203050.A4033@nuxi.com> Date: Thu, 19 Nov 1998 20:30:50 -0800 From: "David O'Brien" To: Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: snprintf() in the kernel Reply-To: obrien@NUXI.com References: <19981120093817.K467@freebie.lemis.com> <199811200057.QAA29023@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811200057.QAA29023@bubba.whistle.com>; from Archie Cobbs on Thu, Nov 19, 1998 at 04:57:47PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The only subtle gotcha with snprintf() is that it returns > the number of characters that *would* have been printed, > not the number that actually were printed. So, create a new function called ksprintf() that has the calling semantics of sprintf(), but the return semantics you like. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 20:32:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09607 for freebsd-current-outgoing; Thu, 19 Nov 1998 20:32:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09567 for ; Thu, 19 Nov 1998 20:32:24 -0800 (PST) (envelope-from oleg@ogurok.com) Received: from nexus (nexus.globix.net [204.254.224.103]) by ogurok.com (8.9.1/8.9.1) with SMTP id XAA06464 for ; Thu, 19 Nov 1998 23:37:14 -0500 (EST) (envelope-from oleg@ogurok.com) Message-ID: <01fb01be143e$db4df600$67e0fecc@nexus.globix.net> From: "Oleg Ogurok" To: Subject: Can't "make world" to update 3.0-RELEASE to STABLE. Date: Thu, 19 Nov 1998 23:33:01 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01F8_01BE1414.F2565C40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_01F8_01BE1414.F2565C40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, All. I just installed fresh version of 3.0-RELEASE, installed cvsup and got = CURENT sources, then I tried to "make world", but got an error. Then I removed all /usr/src/ and ran cvsup again. Here's what I am = getting (last 100 lines). The config file for cvsup I got from = /usr/src/share/cvsup/ I believe. ---------------------------------- cd /usr/src/lib/libutil && /usr/obj/usr/src/tmp/usr/bin/make = beforeinstall install -C -o bin -g bin -m 444 /usr/src/lib/libutil/libutil.h = /usr/obj/usr/src/tmp/usr/include install -C -o bin -g bin -m 444 /usr/src/lib/libutil/login_cap.h = /usr/obj/usr/src/tmp/usr/include cd /usr/src/lib/libz && /usr/obj/usr/src/tmp/usr/bin/make beforeinstall install -C -o bin -g bin -m 444 /usr/src/lib/libz/zconf.h = /usr/obj/usr/src/tmp/usr/include install -C -o bin -g bin -m 444 /usr/src/lib/libz/zlib.h = /usr/obj/usr/src/tmp/usr/include -------------------------------------------------------------- Rebuilding tools needed to build the libraries -------------------------------------------------------------- cd /usr/src && = PATH=3D/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/u= sr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin= :/usr/games:/usr/local/bin:/usr/X11R6/bin:/root/bin = BISON_SIMPLE=3D/usr/obj/usr/src/tmp/usr/share/misc/bison.simple = COMPILER_PATH=3D/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr= /bin GCC_EXEC_PREFIX=3D/usr/obj/usr/src/tmp/usr/lib/ = LD_LIBRARY_PATH=3D/usr/obj/usr/src/tmp/usr/lib = LIBRARY_PATH=3D/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib = NOEXTRADEPEND=3Dt /usr/obj/usr/src/tmp/usr/bin/make = DESTDIR=3D/usr/obj/usr/src/tmp lib-tools cd /usr/src/gnu/usr.bin/gperf && /usr/obj/usr/src/tmp/usr/bin/make = depend && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN = -DNOPROFILE all && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN = -DNOPROFILE -B install cleandir obj rm -f .depend mkdep -f .depend -a -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/options.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/iterator.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/perfect.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/keylist.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/listnode.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/xmalloc.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/hashtable.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/boolarray.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/readline.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/stderr.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/version.c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/getopt.c =3D=3D=3D> doc cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/options.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/iterator.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/perfect.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/keylist.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/listnode.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/xmalloc.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/hashtable.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/boolarray.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/readline.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/stderr.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/version.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/getopt.c cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS = -I/usr/obj/usr/src/tmp/usr/include -o gperf options.o iterator.o main.o = perfect.o keylist.o listnode.o xmalloc.o hashtable.o boolarray.o = readline.o stderr.o version.o getopt.o =20 =3D=3D=3D> doc install -c -s -o bin -g bin -m 555 gperf /usr/obj/usr/src/tmp/usr/bin =3D=3D=3D> doc =3D=3D=3D> doc /usr/obj/usr/src/gnu/usr.bin/gperf created for = /usr/src/gnu/usr.bin/gperf =3D=3D=3D> doc /usr/obj/usr/src/gnu/usr.bin/gperf/doc created for = /usr/src/gnu/usr.bin/gperf/doc cd /usr/src/gnu/usr.bin/ld && /usr/obj/usr/src/tmp/usr/bin/make depend = && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE all = && /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE -B = install cleandir obj rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/usr.bin/ld = -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include = /usr/src/gnu/usr.bin/ld/ld.c /usr/src/gnu/usr.bin/ld/symbol.c = /usr/src/gnu/usr.bin/ld/lib.c /usr/src/gnu/usr.bin/ld/shlib.c = /usr/src/gnu/usr.bin/ld/warnings.c /usr/src/gnu/usr.bin/ld/support.c = /usr/src/gnu/usr.bin/ld/rrs.c /usr/src/gnu/usr.bin/ld/xbits.c = /usr/src/gnu/usr.bin/ld/i386/md.c = /usr/src/gnu/usr.bin/ld/../../../contrib/gcc/cplus-dem.c =3D=3D=3D> ldconfig rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/usr.bin/ld/ldconfig/.. = -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 = -I/usr/obj/usr/src/tmp/usr/include = /usr/src/gnu/usr.bin/ld/ldconfig/ldconfig.c = /usr/src/gnu/usr.bin/ld/ldconfig/../shlib.c = /usr/src/gnu/usr.bin/ld/ldconfig/../support.c =3D=3D=3D> ldd rm -f .depend mkdep -f .depend -a -I/usr/obj/usr/src/tmp/usr/include = /usr/src/gnu/usr.bin/ld/ldd/ldd.c /usr/src/gnu/usr.bin/ld/ldd/sods.c =3D=3D=3D> rtld rm -f .depend mkdep -f .depend -a -I/usr/src/gnu/usr.bin/ld/rtld/.. = -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 = -DRTLD -I/usr/obj/usr/src/tmp/usr/include = /usr/src/gnu/usr.bin/ld/rtld/../i386/mdprologue.S mkdep -f .depend -a -I/usr/src/gnu/usr.bin/ld/rtld/.. = -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 = -DRTLD -I/usr/obj/usr/src/tmp/usr/include = /usr/src/gnu/usr.bin/ld/rtld/rtld.c = /usr/src/gnu/usr.bin/ld/rtld/malloc.c = /usr/src/gnu/usr.bin/ld/rtld/../shlib.c = /usr/src/gnu/usr.bin/ld/rtld/../i386/md.c = /usr/src/gnu/usr.bin/ld/rtld/../support.c = /usr/src/gnu/usr.bin/ld/rtld/sbrk.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/ld.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/symbol.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/lib.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/shlib.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/warnings.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/support.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/rrs.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/xbits.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/i386/md.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/../../../contrib/gcc/cplus-dem.c cc -O -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 = -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS -I/usr/obj/usr/src/tmp/usr/include -static -o ld = ld.o symbol.o lib.o shlib.o warnings.o support.o rrs.o xbits.o md.o = cplus-dem.o =20 =3D=3D=3D> ldconfig cc -O -I/usr/src/gnu/usr.bin/ld/ldconfig/.. = -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/ldconfig/ldconfig.c cc -O -I/usr/src/gnu/usr.bin/ld/ldconfig/.. = -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/ldconfig/../shlib.c cc -O -I/usr/src/gnu/usr.bin/ld/ldconfig/.. = -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/ldconfig/../support.c cc -O -I/usr/src/gnu/usr.bin/ld/ldconfig/.. = -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386 = -I/usr/obj/usr/src/tmp/usr/include -static -o ldconfig ldconfig.o = shlib.o support.o =20 =3D=3D=3D> ldd cc -O -Wall -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/ldd/ldd.c /usr/src/gnu/usr.bin/ld/ldd/ldd.c: In function `main': /usr/src/gnu/usr.bin/ld/ldd/ldd.c:98: warning: implicit declaration of = function `dump_file' cc -O -Wall -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/ldd/sods.c cc -O -Wall -I/usr/obj/usr/src/tmp/usr/include -o ldd ldd.o sods.o =20 =3D=3D=3D> rtld cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/rtld/../i386/mdprologue.S cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/rtld/rtld.c cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/rtld/malloc.c cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/rtld/../shlib.c cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/rtld/../i386/md.c cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/rtld/../support.c cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/rtld/sbrk.c cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = -I/usr/obj/usr/src/tmp/usr/include -nostdlib -Wl,-Bshareable = -Wl,-Bsymbolic -Wl,-assert -Wl,nosymbolic -o ld.so mdprologue.o rtld.o = malloc.o shlib.o md.o support.o sbrk.o -lc_pic -lgcc_pic mdprologue.o(.text+0x22): undefined reference to `_rtld' mdprologue.o(.text+0x40): undefined reference to `_binder' rtld.o: In function `reloc_map': rtld.o(.text+0xe99): undefined reference to `binder_entry' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. viking# exit viking# exit Script done on Thu Nov 19 23:10:05 1998 ------=_NextPart_000_01F8_01BE1414.F2565C40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi, All.

I just = installed fresh=20 version of 3.0-RELEASE, installed cvsup and got CURENT sources, then I = tried to=20 "make world", but got an error.
Then I removed all /usr/src/ = and ran cvsup=20 again. Here's what I am getting (last 100 lines). The config file for = cvsup I=20 got from /usr/src/share/cvsup/ I believe.
 
----------------------------------
 
cd /usr/src/lib/libutil && = /usr/obj/usr/src/tmp/usr/bin/make=20 beforeinstall
install -C -o bin -g bin -m 444=20 /usr/src/lib/libutil/libutil.h  = /usr/obj/usr/src/tmp/usr/include
install=20 -C -o bin -g bin -m 444 /usr/src/lib/libutil/login_cap.h =20 /usr/obj/usr/src/tmp/usr/include
cd /usr/src/lib/libz &&=20 /usr/obj/usr/src/tmp/usr/bin/make beforeinstall
install -C -o bin -g = bin -m=20 444 /usr/src/lib/libz/zconf.h  = /usr/obj/usr/src/tmp/usr/include
install=20 -C -o bin -g bin -m 444 /usr/src/lib/libz/zlib.h =20 /usr/obj/usr/src/tmp/usr/include

---------------------------------= -----------------------------
Rebuilding=20 tools needed to build the=20 libraries
------------------------------------------------------------= --
cd=20 /usr/src &&=20 PATH=3D/usr/obj/usr/src/tmp/sbin:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/u= sr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin= :/usr/games:/usr/local/bin:/usr/X11R6/bin:/root/bin=20 BISON_SIMPLE=3D/usr/obj/usr/src/tmp/usr/share/misc/bison.simple =20 COMPILER_PATH=3D/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr= /bin =20 GCC_EXEC_PREFIX=3D/usr/obj/usr/src/tmp/usr/lib/ =20 LD_LIBRARY_PATH=3D/usr/obj/usr/src/tmp/usr/lib =20 LIBRARY_PATH=3D/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib = NOEXTRADEPEND=3Dt /usr/obj/usr/src/tmp/usr/bin/make = DESTDIR=3D/usr/obj/usr/src/tmp=20 lib-tools
cd /usr/src/gnu/usr.bin/gperf &&=20 /usr/obj/usr/src/tmp/usr/bin/make depend && =20 /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE all=20 &&  /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN = -DNOPROFILE=20 -B install cleandir obj
rm -f .depend
mkdep -f .depend=20 -a    -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS=20 -I/usr/obj/usr/src/tmp/usr/include =20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/options.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/iterator.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/perfect.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/keylist.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/listnode.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/xmalloc.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/hashtable.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/boolarray.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/readline.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/stderr.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/version.c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/getopt.c
=3D=3D=3D= >=20 doc
cc -O -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/options.c
cc -O = -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/iterator.c
cc = -O=20 -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/main.c
cc -O=20 -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/perfect.c
cc -O = -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/keylist.c
cc -O = -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/listnode.c
cc = -O=20 -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/xmalloc.c
cc -O = -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/hashtable.c
cc = -O=20 -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/boolarray.c
cc = -O=20 -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/readline.c
cc = -O=20 -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/stderr.c
cc -O=20 -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/version.c
cc -O = -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/getopt.c
cc -O=20 -D_HAVE_PARAM_H -DLO_CAL -DGATHER_STATISTICS  =20 -I/usr/obj/usr/src/tmp/usr/include  -o gperf options.o iterator.o = main.o=20 perfect.o keylist.o listnode.o xmalloc.o hashtable.o boolarray.o = readline.o=20 stderr.o version.o getopt.o 
=3D=3D=3D> doc
install -c -s = -o bin -g bin=20 -m 555   gperf /usr/obj/usr/src/tmp/usr/bin
=3D=3D=3D> = doc
=3D=3D=3D>=20 doc
/usr/obj/usr/src/gnu/usr.bin/gperf created for=20 /usr/src/gnu/usr.bin/gperf
=3D=3D=3D>=20 doc
/usr/obj/usr/src/gnu/usr.bin/gperf/doc created for=20 /usr/src/gnu/usr.bin/gperf/doc
cd /usr/src/gnu/usr.bin/ld &&=20 /usr/obj/usr/src/tmp/usr/bin/make depend && =20 /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPROFILE all=20 &&  /usr/obj/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN = -DNOPROFILE=20 -B install cleandir obj
rm -f .depend
mkdep -f .depend=20 -a    -I/usr/src/gnu/usr.bin/ld = -I/usr/src/gnu/usr.bin/ld/i386=20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC = -DDEMANGLE_CPLUSPLUS=20 -I/usr/obj/usr/src/tmp/usr/include  /usr/src/gnu/usr.bin/ld/ld.c=20 /usr/src/gnu/usr.bin/ld/symbol.c /usr/src/gnu/usr.bin/ld/lib.c=20 /usr/src/gnu/usr.bin/ld/shlib.c /usr/src/gnu/usr.bin/ld/warnings.c=20 /usr/src/gnu/usr.bin/ld/support.c /usr/src/gnu/usr.bin/ld/rrs.c=20 /usr/src/gnu/usr.bin/ld/xbits.c /usr/src/gnu/usr.bin/ld/i386/md.c=20 /usr/src/gnu/usr.bin/ld/../../../contrib/gcc/cplus-dem.c
=3D=3D=3D>= =20 ldconfig
rm -f .depend
mkdep -f .depend -a   =20 -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386=20 -I/usr/obj/usr/src/tmp/usr/include =20 /usr/src/gnu/usr.bin/ld/ldconfig/ldconfig.c=20 /usr/src/gnu/usr.bin/ld/ldconfig/../shlib.c=20 /usr/src/gnu/usr.bin/ld/ldconfig/../support.c
=3D=3D=3D> ldd
rm = -f=20 .depend
mkdep -f .depend -a   =20 -I/usr/obj/usr/src/tmp/usr/include  = /usr/src/gnu/usr.bin/ld/ldd/ldd.c=20 /usr/src/gnu/usr.bin/ld/ldd/sods.c
=3D=3D=3D> rtld
rm -f = .depend
mkdep -f=20 .depend -a    -I/usr/src/gnu/usr.bin/ld/rtld/..=20 -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 = -DRTLD=20 -I/usr/obj/usr/src/tmp/usr/include   =20 /usr/src/gnu/usr.bin/ld/rtld/../i386/mdprologue.S
mkdep -f .depend=20 -a    -I/usr/src/gnu/usr.bin/ld/rtld/..=20 -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 = -DRTLD=20 -I/usr/obj/usr/src/tmp/usr/include  = /usr/src/gnu/usr.bin/ld/rtld/rtld.c=20 /usr/src/gnu/usr.bin/ld/rtld/malloc.c = /usr/src/gnu/usr.bin/ld/rtld/../shlib.c=20 /usr/src/gnu/usr.bin/ld/rtld/../i386/md.c=20 /usr/src/gnu/usr.bin/ld/rtld/../support.c=20 /usr/src/gnu/usr.bin/ld/rtld/sbrk.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/ld.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/symbol.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/lib.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/shlib.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/warnings.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/support.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/rrs.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/xbits.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/i386/md.c
cc -O -I/usr/src/gnu/usr.bin/ld=20 -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/../../../contrib/gcc/cplus-dem.c
cc -O=20 -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/i386 =20 -I/usr/src/gnu/usr.bin/ld/../../../contrib/gcc -DIN_GCC=20 -DDEMANGLE_CPLUSPLUS   = -I/usr/obj/usr/src/tmp/usr/include =20 -static -o ld ld.o symbol.o lib.o shlib.o warnings.o support.o rrs.o = xbits.o=20 md.o cplus-dem.o 
=3D=3D=3D> ldconfig
cc -O=20 -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/ldconfig/ldconfig.c
cc -O=20 -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/ldconfig/../shlib.c
cc -O=20 -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/ldconfig/../support.c
cc -O=20 -I/usr/src/gnu/usr.bin/ld/ldconfig/.. -I/usr/src/gnu/usr.bin/ld/ldconfig = -I/usr/src/gnu/usr.bin/ld/ldconfig/../i386  =20 -I/usr/obj/usr/src/tmp/usr/include  -static -o ldconfig ldconfig.o = shlib.o=20 support.o 
=3D=3D=3D> ldd
cc -O -Wall  =20 -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/ldd/ldd.c
/usr/src/gnu/usr.bin/ld/ldd/ldd.c: = In=20 function `main':
/usr/src/gnu/usr.bin/ld/ldd/ldd.c:98: warning: = implicit=20 declaration of function `dump_file'
cc -O -Wall  =20 -I/usr/obj/usr/src/tmp/usr/include -c = /usr/src/gnu/usr.bin/ld/ldd/sods.c
cc=20 -O -Wall   -I/usr/obj/usr/src/tmp/usr/include  -o ldd = ldd.o=20 sods.o 
=3D=3D=3D> rtld
cc -O = -I/usr/src/gnu/usr.bin/ld/rtld/..=20 -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 = -fpic=20 -fno-function-cse -DRTLD   -I/usr/obj/usr/src/tmp/usr/include = -c=20 /usr/src/gnu/usr.bin/ld/rtld/../i386/mdprologue.S
cc -O=20 -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld=20 -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse=20 -DRTLD   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/rtld/rtld.c
cc -O = -I/usr/src/gnu/usr.bin/ld/rtld/..=20 -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 = -fpic=20 -fno-function-cse -DRTLD   -I/usr/obj/usr/src/tmp/usr/include = -c=20 /usr/src/gnu/usr.bin/ld/rtld/malloc.c
cc -O = -I/usr/src/gnu/usr.bin/ld/rtld/..=20 -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 = -fpic=20 -fno-function-cse -DRTLD   -I/usr/obj/usr/src/tmp/usr/include = -c=20 /usr/src/gnu/usr.bin/ld/rtld/../shlib.c
cc -O=20 -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld=20 -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse=20 -DRTLD   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/rtld/../i386/md.c
cc -O=20 -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld=20 -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse=20 -DRTLD   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/rtld/../support.c
cc -O=20 -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld=20 -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse=20 -DRTLD   -I/usr/obj/usr/src/tmp/usr/include -c=20 /usr/src/gnu/usr.bin/ld/rtld/sbrk.c
cc -O = -I/usr/src/gnu/usr.bin/ld/rtld/..=20 -I/usr/src/gnu/usr.bin/ld/rtld -I/usr/src/gnu/usr.bin/ld/rtld/../i386 = -fpic=20 -fno-function-cse -DRTLD   = -I/usr/obj/usr/src/tmp/usr/include =20 -nostdlib -Wl,-Bshareable -Wl,-Bsymbolic -Wl,-assert -Wl,nosymbolic -o = ld.so=20 mdprologue.o rtld.o malloc.o shlib.o md.o support.o sbrk.o  -lc_pic = -lgcc_pic
mdprologue.o(.text+0x22): undefined reference to=20 `_rtld'
mdprologue.o(.text+0x40): undefined reference to = `_binder'
rtld.o:=20 In function `reloc_map':
rtld.o(.text+0xe99): undefined reference to=20 `binder_entry'
*** Error code 1

Stop.
*** Error code=20 1

Stop.
*** Error code 1

Stop.
*** Error code=20 1

Stop.
viking# exit
viking# exit

Script done on Thu = Nov 19=20 23:10:05 1998
------=_NextPart_000_01F8_01BE1414.F2565C40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 20:37:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10257 for freebsd-current-outgoing; Thu, 19 Nov 1998 20:37:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10248; Thu, 19 Nov 1998 20:37:37 -0800 (PST) (envelope-from oleg@ogurok.com) Received: from nexus (nexus.globix.net [204.254.224.103]) by ogurok.com (8.9.1/8.9.1) with SMTP id XAA06479; Thu, 19 Nov 1998 23:42:25 -0500 (EST) (envelope-from oleg@ogurok.com) Message-ID: <020701be143f$94f79020$67e0fecc@nexus.globix.net> From: "Oleg Ogurok" To: , Subject: Can't "make world" in 3.0-RELEASE, to STABLE. Date: Thu, 19 Nov 1998 23:38:11 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0204_01BE1415.AB581DA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0204_01BE1415.AB581DA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, All,=20 I just posted my problem with "make world". Sorry, it's not CURENT, it's STABLE. I am trying to update 3.0-RELEASE = to STABLE. I got the config file "stable-supfile" from = /usr/src/share/examples/. -Oleg. ------=_NextPart_000_0204_01BE1415.AB581DA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi, All,
 
I just posted my problem with = "make=20 world".
Sorry, it's not CURENT, it's STABLE. = I am trying=20 to update 3.0-RELEASE to STABLE. I got the config file=20 "stable-supfile" from /usr/src/share/examples/.
 
 
-Oleg.
------=_NextPart_000_0204_01BE1415.AB581DA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 20:42:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10995 for freebsd-current-outgoing; Thu, 19 Nov 1998 20:42:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10990 for ; Thu, 19 Nov 1998 20:42:45 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id UAA24366; Thu, 19 Nov 1998 20:41:42 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma024362; Thu, 19 Nov 98 20:41:41 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id UAA18801; Thu, 19 Nov 1998 20:41:40 -0800 (PST) From: Archie Cobbs Message-Id: <199811200441.UAA18801@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <19981119203050.A4033@nuxi.com> from David O'Brien at "Nov 19, 98 08:30:50 pm" To: obrien@NUXI.com Date: Thu, 19 Nov 1998 20:41:40 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien writes: > > The only subtle gotcha with snprintf() is that it returns > > the number of characters that *would* have been printed, > > not the number that actually were printed. > > So, create a new function called ksprintf() that has the calling semantics > of sprintf(), but the return semantics you like. I don't have a problem with it.. I'm just pointing that out so people don't make the wrong assumption (I found out the hard way once :-) -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 20:59:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12762 for freebsd-current-outgoing; Thu, 19 Nov 1998 20:59:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm106-05.dialip.mich.net [192.195.231.207]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA12755 for ; Thu, 19 Nov 1998 20:59:07 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811200459.UAA12755@hub.freebsd.org> Received: (qmail 461 invoked from smtpd); 20 Nov 1998 04:58:41 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 20 Nov 1998 04:58:41 -0000 Date: Thu, 19 Nov 1998 23:58:40 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: more dying daemons To: jdp@polstra.com cc: current@FreeBSD.ORG In-Reply-To: <199811200239.SAA17040@vashon.polstra.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19 Nov, John Polstra wrote: > Someone who is experiencing this problem please try a very simple > experiment for me. On a freshly rebooted system (to ensure a clean > slate), do this: > > sysctl -w kern.fast_vfork=0 > unfortunately this didn't have any effect :( inetd and samba still die as before :( i'll keep my machine running with this knob turned and see if anything else turns up that might be a clue. back to the search... next up: dima's kernel patches... enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 20:59:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA12971 for freebsd-current-outgoing; Thu, 19 Nov 1998 20:59:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12812; Thu, 19 Nov 1998 20:59:13 -0800 (PST) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-121.laker.net [208.0.233.21]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id XAA28504; Thu, 19 Nov 1998 23:58:43 -0500 Message-Id: <199811200458.XAA28504@laker.net> From: "Steve Friedrich" To: "freebsd-current@FreeBSD.ORG" , "freebsd-stable@FreeBSD.ORG" , "Oleg Ogurok" Date: Thu, 19 Nov 1998 23:56:38 -0500 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Can't "make world" in 3.0-RELEASE, to STABLE. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Original Message Text--- From: Oleg Ogurok Date: Thu, 19 Nov 1998 23:38:11 -0500 I just posted my problem with "make world". Sorry, it's not CURENT, it's STABLE. I am trying to update 3.0-RELEASE to STABLE. I got the config file "stable-supfile" from /usr/src/share/examples/. You can't update 3.0-RELEASE to -stable, because -stable is the 2.2 line!! You need to track -current. I strongly suggest that you reinstall 3.0-RELEASE and then cvsup -current, don't try to "fix" it any other way (unless you have backup tapes from just after installing 3.0-R). Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 20:59:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA13007 for freebsd-current-outgoing; Thu, 19 Nov 1998 20:59:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA12997 for ; Thu, 19 Nov 1998 20:59:22 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id UAA04605; Thu, 19 Nov 1998 20:58:23 -0800 (PST) (envelope-from obrien) Message-ID: <19981119205823.C4033@nuxi.com> Date: Thu, 19 Nov 1998 20:58:23 -0800 From: "David O'Brien" To: John Polstra , bartol@salk.edu Cc: current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) Reply-To: obrien@NUXI.com References: <199811192221.OAA09145@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811192221.OAA09145@vashon.polstra.com>; from John Polstra on Thu, Nov 19, 1998 at 02:21:09PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Aha! The new amd uses different options to select the protocol for > NFS. I bet you still have an old amd.map file. For the new amd, > the desired options are "proto=udp,vers=2". Acutally I've got the default /etc/amd.map file specifing "vers=3,proto=tcp". I would like to leave the default of NFSv3/TCP as that is the modern setting... but if this is causing a failure on too many boxes I guess we have to revisit that. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 21:01:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13371 for freebsd-current-outgoing; Thu, 19 Nov 1998 21:01:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13366 for ; Thu, 19 Nov 1998 21:01:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id VAA04664; Thu, 19 Nov 1998 21:00:56 -0800 (PST) (envelope-from obrien) Message-ID: <19981119210056.D4033@nuxi.com> Date: Thu, 19 Nov 1998 21:00:56 -0800 From: "David O'Brien" To: David Wolfskill Cc: current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) Reply-To: obrien@NUXI.com References: <199811192221.OAA09145@vashon.polstra.com> <199811192227.OAA13755@pau-amma.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811192227.OAA13755@pau-amma.whistle.com>; from David Wolfskill on Thu, Nov 19, 1998 at 02:27:16PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, any recommended strategy for using the *same* amd maps for machines > that use both versions of amd? The new amd treats the old map's "nfsv2" as "proto=udp,vers=2". So you shouldn't have a problem. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 21:02:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13641 for freebsd-current-outgoing; Thu, 19 Nov 1998 21:02:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA13630 for ; Thu, 19 Nov 1998 21:02:35 -0800 (PST) (envelope-from terbart@aye.net) Received: (qmail 22261 invoked by uid 3185); 20 Nov 1998 05:00:28 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Nov 1998 05:00:28 -0000 Date: Fri, 20 Nov 1998 00:00:28 -0500 (EST) From: Barrett Richardson To: garman@earthling.net cc: current@FreeBSD.ORG Subject: Re: more dying daemons In-Reply-To: <199811190040.QAA12276@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Swap usage at 64% after only hour seems awfully high. I've seem similar behaviour in the world of SCO. Folks just under the threshold of what they can get out of their box with given swap/memory size with 3.2v4.2 are having no problems. They upgrade to Open Server 5, put the same load on it, and the box starts a slow downward spiral and finally becomes unusable. They reboot it, and its ok for a couple of hours. In Greg Lehey's book there is a hint that swap be around 2.5 times what the physical memory is _if_ you have a sizable amount of memory (looks like you have around 128 mb) _and_ expect to be paging. You can use vnconfig to test the beast without reslicing if you have ample disk space. dd if=/dev/zero of=bigswapfile bs=1024 count=262144 vnconfig /dev/vn0c bigswapfile swap swapon /dev/vn0c That will give you another 256 mb of swap (may have to trim to availability of disk space). If your swap usage stabilizes at some point and your box lives, then you've nailed the problem. If problems persist, entertain the idea that something you are using has a mongo memory leak. In the Mem: line in your message memory dedicated to Cache and Bufs looks really low. May want to shove some more RAM in it if the above test works out. It looks like a bonafide memory starvation problem to me. -- Barrett Richardson What is a magician but a practicing theorist? barrett@aye.net On Wed, 18 Nov 1998 garman@earthling.net wrote: > > I'm still having the problems I described earlier. > inetd, samba, and ssh exhibit symptoms where they wither away and die > after a certain amount of time, and this is easily and rapidly > reproducible (in the space of only an hour my freshly-started inetd will > begin to die each time it forks...) > > obviously, this is quite an annoying problem. I have a debugging > version of inetd compiled, along with samba. I'll repost my samba > backtraces if they'll help. inetd gives the "junk pointer: too high to > make sense" messages before it dies. I'm still figuring out how to > debug that problem, as it dies before I can attach to it with gdb. > > what can I do to help diagnose/fix these problems? > > This is on -current as of ~2 days ago. (my machine has been up since > then, and the problems only get worse the longer the machine has been > up) > > my swap usage is: > Device 1024-blocks Used Avail Capacity Type > /dev/wd0s1b 69632 49032 20472 71% Interleaved > /dev/wd2s1b 81920 47568 34224 58% Interleaved > Total 151296 96600 54696 64% > > Mem: 54M Active, 2596K Inact, 16M Wired, 1664K Cache, 2844K Buf, 18M Free > Swap: 148M Total, 94M Used, 53M Free, 64% Inuse > > and i do have one "suggest more swap" message in my logs: > Nov 16 21:54:32 jason /kernel: swap_pager: suggest more swap space: 190 MB > > along with an "interesting" message from sshd (1.2.26): > Nov 18 20:39:32 jason sshd[90364]: fatal: xmalloc: out of memory (allocating 107 > 3675515 bytes) > (oddly enough it isn't even 8pm yet, weird. unrelated problem? :)) > > and many instances of inetd dying on sigsegv's. > > please, i'm willing to give people accounts on this machine, do > debugging, test patches, whatever it takes. just tell me what > data/information you need or point me in the right direction. > > i had none of these problems when i ran 2.2-stable a while back, on the > same hardware. > > thanks, > -- > Jason Garman http://garman.dyn.ml.org/ > Student, University of Maryland garman@earthling.net > And now... did you know that: Whois: JAG145 > "If you fart consistently for 6 years and 9 months, enough gas is > produced to create the energy of an atomic bomb." -- 0xdeadbeef posting > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 21:05:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14026 for freebsd-current-outgoing; Thu, 19 Nov 1998 21:05:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14020 for ; Thu, 19 Nov 1998 21:05:18 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id VAA04743; Thu, 19 Nov 1998 21:04:42 -0800 (PST) (envelope-from obrien) Message-ID: <19981119210442.E4033@nuxi.com> Date: Thu, 19 Nov 1998 21:04:42 -0800 From: "David O'Brien" To: John Polstra , Tom Bartol Cc: current@FreeBSD.ORG Subject: Re: Problem with amd (was: NFS problems in -current) Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from John Polstra on Thu, Nov 19, 1998 at 04:17:49PM -0800 X-Operating-System: FreeBSD 3.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not that I know of. The documentation is pretty broken. I had a > very hard time even finding the right options in the sources. Acutally the documentation is fine (see /usr/src/contrib/amd/docs/am-utils.texi). Problem is our texinfo (in src/contrib) is too old to build these docs. -- -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 19 21:13:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14852 for freebsd-current-outgoing; Thu, 19 Nov 1998 21:13:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14847 for ; Thu, 19 Nov 1998 21:13:16 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA24641; Thu, 19 Nov 1998 21:12:15 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma024639; Thu, 19 Nov 98 21:12:04 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA18941; Thu, 19 Nov 1998 21:12:04 -0800 (PST) From: Archie Cobbs Message-Id: <199811200512.VAA18941@bubba.whistle.com> Subject: Re: strings in the kernel (was: snprintf() in the kernel) In-Reply-To: <199811191355.NAA03525@aldan.algebra.com> from Mikhail Teterin at "Nov 19, 98 01:55:25 pm" To: mi@aldan.algebra.com (Mikhail Teterin) Date: Thu, 19 Nov 1998 21:12:04 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mikhail Teterin writes: > This reminds me of a marginally related issue: > > strings /kernel | sort -u | wc > 14409 22343 235606 > vs. > strings /kernel | wc > 25522 34130 317264 > > In other words, there are 11113 duplicate lines in my kernel, > amounting for a total of 91658 bytes. And this does not even include > different strings with huge common sub-strings, such as: Sounds like a job for mr. linker.. is there support the smashing together of identical strings in the text segment? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 00:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01357 for freebsd-current-outgoing; Fri, 20 Nov 1998 00:01:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from myrddin.demon.co.uk (myrddin.demon.co.uk [158.152.54.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01345 for ; Fri, 20 Nov 1998 00:01:33 -0800 (PST) (envelope-from dom@myrddin.demon.co.uk) Received: from localhost (myrddin.demon.co.uk) [127.0.0.1] by myrddin.demon.co.uk with esmtp (Exim 1.92 #1) id 0zglH3-0000Co-00; Fri, 20 Nov 1998 07:46:37 +0000 To: Jos Backus Cc: current@FreeBSD.ORG Subject: Re: /etc/rc.d, and changes to /etc/rc? References: <19981117235709.20735@nothing-going-on.org> <19981118135413.C3308@hal.mpn.cp.philips.com> From: Dom Mitchell In-Reply-To: Jos Backus's message of "Wed, 18 Nov 1998 13:54:13 +0100" X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Date: Fri, 20 Nov 1998 07:46:37 +0000 Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jos Backus writes: > On Wed, Nov 18, 1998 at 02:35:03PM +0300, Grigoriy Strokin wrote: > > For example, I'd like to restart inetd in my FreeBSD current every time it > > dies 1-4 times per week :) > > In that case, you may find http://pobox.com/~djb/daemontools.html to be of > interest. Also available as /usr/ports/sysutils/daemontools. -- ``Bernstein versus Venema Celebrity Deathmatch: I see a great need.'' -- MR To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 00:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01578 for freebsd-current-outgoing; Fri, 20 Nov 1998 00:03:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01567 for ; Fri, 20 Nov 1998 00:02:58 -0800 (PST) (envelope-from root@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id IAA11207 for ; Fri, 20 Nov 1998 08:58:58 +0100 (CET) (envelope-from root@swimsuit.internet.dk) Date: Fri, 20 Nov 1998 08:58:57 +0100 (CET) From: Leif Neland To: freebsd-current@FreeBSD.ORG Subject: Netscape4.5, 3.0-current-elf, libXt.so.6.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can't start netscape: (netscape-4.5-navigator, cvsupped today) ld.so failed: Can't find shared library "libXt.so.6.0" But I have it: -rwxr-xr-x 1 root wheel 291585 22 Okt 23:58 /usr/X11R6/lib/libXt.so.6.0 -rwxr-xr-x 1 root wheel 310502 25 Okt 1996 /usr/compat/linux/usr/X11R6/lib/libXt.so.6.0 -rwxr-xr-x 1 root wheel 320516 25 Okt 1996 /usr/compat/linux/usr/i486-linuxaout/lib/libXt.so.6.0 Now what? Leif Neland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 00:51:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06786 for freebsd-current-outgoing; Fri, 20 Nov 1998 00:51:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgw1.fhg.de (mailgw1.fhg.de [153.96.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06756 for ; Fri, 20 Nov 1998 00:50:49 -0800 (PST) (envelope-from runge@egd.igd.fhg.de) Received: by mailgw1.fhg.de (fhg.de); Fri, 20 Nov 1998 09:50:09 +0100 (MET) X-ENV: (mailgw1.fhg.de) runge@egd.igd.fhg.de -> freebsd-current@freebsd.ORG.VIA-SMTP X-BULK-CHECK-1-981120.09.49.44: egd.egd.igd.fhg.de [153.96.43.2] Received: by mailgw1.fhg.de (fhg.de) with SMTP; Fri, 20 Nov 1998 09:49:36 +0100 (MET) from brussel.egd.igd.fhg.de Received: by brussel.egd.igd.fhg.de; Fri, 20 Nov 98 09:47:46 +0100 Message-Id: <36552CB2.8D37E3FA@rostock.zgdv.de> Date: Fri, 20 Nov 1998 09:47:47 +0100 From: Thomas Runge Organization: http://www.rostock.zgdv.de X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.6 sun4u) Mime-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: 3.0, pcm and ed Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded to 3.0-release from an 3.0-snapshot via rebuild from sources. I'm using luigis sound driver and an cheap pnp ET4000 ethernet card. If I switch the sound driver on, the kernel can't find ed0 anymore. It works, if sound code is switched off (pnp still enabled). I tried tracing the gnats database, but couldnt find anything. (Thats not a new problem, it was the same with my old snapshot.) How can I get both devices to work? -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 01:13:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08906 for freebsd-current-outgoing; Fri, 20 Nov 1998 01:13:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgw1.fhg.de (mailgw1.fhg.de [153.96.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08899 for ; Fri, 20 Nov 1998 01:13:32 -0800 (PST) (envelope-from runge@egd.igd.fhg.de) Received: by mailgw1.fhg.de (fhg.de); Fri, 20 Nov 1998 10:12:52 +0100 (MET) X-ENV: (mailgw1.fhg.de) runge@egd.igd.fhg.de -> freebsd-current@freebsd.ORG.VIA-SMTP X-BULK-CHECK-1-981120.10.12.36: egd.egd.igd.fhg.de [153.96.43.2] Received: by mailgw1.fhg.de (fhg.de) with SMTP; Fri, 20 Nov 1998 10:12:31 +0100 (MET) from brussel.egd.igd.fhg.de Received: by brussel.egd.igd.fhg.de; Fri, 20 Nov 98 10:10:42 +0100 Message-Id: <36553211.C4A2D543@rostock.zgdv.de> Date: Fri, 20 Nov 1998 10:10:41 +0100 From: Thomas Runge Organization: http://www.rostock.zgdv.de X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.6 sun4u) Mime-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: Netscape4.5, 3.0-current-elf, libXt.so.6.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > I can't start netscape: > (netscape-4.5-navigator, cvsupped today) > > ld.so failed: Can't find shared library "libXt.so.6.0" > > But I have it: > > > Now what? The last two libs are irrelevant. And the first lib is (I guess) elf, while netscape is still aout. If your X-libs are still aout, you could change your LD_LIBRARY_PATH or reconfigure via ldconfig. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 01:22:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09623 for freebsd-current-outgoing; Fri, 20 Nov 1998 01:22:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-56-dbn.dial-up.net [196.34.155.120]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09584 for ; Fri, 20 Nov 1998 01:21:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA00535; Fri, 20 Nov 1998 11:09:52 +0200 (SAT) From: Robert Nordier Message-Id: <199811200909.LAA00535@ceia.nordier.com> Subject: Re: /boot/loader & comconsole In-Reply-To: <199811200131.SAA23560@usr09.primenet.com> from Terry Lambert at "Nov 20, 98 01:31:08 am" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 20 Nov 1998 11:09:49 +0200 (SAT) Cc: rnordier@nordier.com, rock@cs.uni-sb.de, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > > Using the BIOS for configuring the serial ports gives you also only > > > 9600 bps. I usually ran the comconsole at 19200 bps. But the original > > > BIOS int 0x14 services seem only support up to 9600 bps. I did a > > > small patch on the bootblocks, so that it uses the "extended communication > > > port control" service. I don't know if good ole 386 BIOS implement this > > > routine, but it works on my machine (I think it was introduced with the > > > PS/2 PCs). > > > > I'm not sure, either, how many BIOSes support this. The documentation I > > have suggests it is PS/2-specific, though it appears it's supported on > > at least some of the machines here. > > > You can determine support by the return value from the call. > > Most BIOS support up to 115k now, at the expense of some of the > lower baud rates. > > See the Ralf Brown list for details, or any one of dozens of > books on serial I/O on the PC. I know how to detect support if I have to, dammit (and the same evidently applies to D. Rock). The actual problem is (to put it in terms sufficiently complex for a Terry to understand): For a given BIOS (where, in this context, "BIOS" may be defined as a member of that set of PC BIOSes having a maximized probability of occupying the event space), determine the likelihood of encountering viable int 0x14/0x4 support, without resorting to statistical sampling techniques. :-) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 01:24:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09943 for freebsd-current-outgoing; Fri, 20 Nov 1998 01:24:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (21.san-francisco-03.ca.dial-access.att.net [12.64.2.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09938 for ; Fri, 20 Nov 1998 01:24:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id BAA00658; Fri, 20 Nov 1998 01:20:51 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811200920.BAA00658@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Zepeda cc: current Subject: Re: New bootloader oddities In-reply-to: Your message of "Thu, 19 Nov 1998 13:06:14 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Nov 1998 01:20:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyways, I figured I'd try out the new bootloader and see how it handles > an ELF kernel. I noticed the bootloader itself doesn't detect any PnP > anything. So I tried to boot the ELF kernel. It hung at the detecting > PnP stuff stage. My box has a singular PCI card (video), and a ISA PnP > card (shown below from an a.out kernel). The config file used for the > [elf] kernel is attached. Made world yesterday, boot loader is v0.85 or > something similar. Award BIOS, generic mobo, integrated aic7880. > > Probing for PnP devices: > CSN 1 Vendor ID: CTL009c [0x9c008c0e] Serial 0x1003d0c7 Comp ID: PNP0600 [0x0006 > d041] > pcm1 (SB16pnp sn 0x1003d0c7) at 0x220-0x22f irq 5 drq 1 flags 0x15 on > isa If it's printed the message, it's finished with the probe. It's likely that it was looking for something else and either hung or you got impatient before it timed out. Normal procedure as documented by anyone that's ever written up the configuration process is to disable everything that you don't have using userconfig; if you haven't tried this, you should. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 01:50:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11565 for freebsd-current-outgoing; Fri, 20 Nov 1998 01:50:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luke.cpl.net (luke.cpl.net [209.150.92.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11560 for ; Fri, 20 Nov 1998 01:49:58 -0800 (PST) (envelope-from shawn@luke.cpl.net) Received: (from shawn@localhost) by luke.cpl.net (8.8.8/8.8.8) id BAA19774; Fri, 20 Nov 1998 01:49:03 -0800 (PST) Message-ID: <19981120014903.A29062@cpl.net> Date: Fri, 20 Nov 1998 01:49:03 -0800 From: Shawn Ramsey To: Jason Dicioccio , Bill Woods Cc: Brian Feldman , Andrzej Bialecki , FreeBsd-Current , Doug White Subject: Re: StarOffice 5.0 References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: ; from Jason Dicioccio on Thu, Nov 19, 1998 at 02:15:17PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually I htink 4.0 does not work with FreeBSD either, I beleive 3.0 is > only working now although they say they are in the middle of porting it > (since they have iit on every other OS) 4.0 works fine on 2.2.7, sp3 requires a small patch though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 02:04:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12893 for freebsd-current-outgoing; Fri, 20 Nov 1998 02:04:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12888 for ; Fri, 20 Nov 1998 02:04:20 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost.swimsuit.internet.dk [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id LAA03765; Fri, 20 Nov 1998 11:03:09 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Fri, 20 Nov 1998 11:03:09 +0100 (CET) From: Leif Neland To: Thomas Runge cc: freebsd-current@FreeBSD.ORG Subject: Re: Netscape4.5, 3.0-current-elf, libXt.so.6.0 In-Reply-To: <36553211.C4A2D543@rostock.zgdv.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Nov 1998, Thomas Runge wrote: > Leif Neland wrote: > > > > I can't start netscape: > > (netscape-4.5-navigator, cvsupped today) > > > > ld.so failed: Can't find shared library "libXt.so.6.0" > > > > But I have it: > > > > > > > Now what? > > The last two libs are irrelevant. And the first lib > is (I guess) elf, while netscape is still aout. > > If your X-libs are still aout, you could change your > LD_LIBRARY_PATH or reconfigure via ldconfig. > /usr/X11R6/lib/libXt.so.6.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped Am I f*cked^h^h^h^h^hlost? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 02:06:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13045 for freebsd-current-outgoing; Fri, 20 Nov 1998 02:06:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13040 for ; Fri, 20 Nov 1998 02:06:46 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from william.cybcon.com (william@usr1-7.cybcon.com [205.147.76.8]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id CAA10105; Fri, 20 Nov 1998 02:05:43 -0800 (PST) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981120014903.A29062@cpl.net> Date: Fri, 20 Nov 1998 02:04:04 -0800 (PST) Reply-To: wwoods@cybcon.com From: William Woods To: Shawn Ramsey Subject: Re: StarOffice 5.0 Cc: Doug White Cc: Doug White , FreeBsd-Current , Andrzej Bialecki , Brian Feldman , Jason Dicioccio Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found a copy of 4.0 at www.filez.com last night and am running it now on 3.0 -current also, thanks for all the help folks. On 20-Nov-98 Shawn Ramsey wrote: >> Actually I htink 4.0 does not work with FreeBSD either, I beleive 3.0 is >> only working now although they say they are in the middle of porting it >> (since they have iit on every other OS) > > 4.0 works fine on 2.2.7, sp3 requires a small patch though. ---------------------------------- E-Mail: William Woods Date: 20-Nov-98 Time: 02:01:36 -->> FreeBSD 3.0 <<-- AIM bsdman1 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 02:14:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13674 for freebsd-current-outgoing; Fri, 20 Nov 1998 02:14:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgw1.fhg.de (mailgw1.fhg.de [153.96.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13668 for ; Fri, 20 Nov 1998 02:14:04 -0800 (PST) (envelope-from runge@egd.igd.fhg.de) Received: by mailgw1.fhg.de (fhg.de); Fri, 20 Nov 1998 11:13:17 +0100 (MET) X-ENV: (mailgw1.fhg.de) runge@egd.igd.fhg.de -> freebsd-current@freebsd.ORG.VIA-SMTP X-BULK-CHECK-1-981120.11.12.56: egd.egd.igd.fhg.de [153.96.43.2] Received: by mailgw1.fhg.de (fhg.de) with SMTP; Fri, 20 Nov 1998 11:12:36 +0100 (MET) from brussel.egd.igd.fhg.de Received: by brussel.egd.igd.fhg.de; Fri, 20 Nov 98 11:10:47 +0100 Message-Id: <36554027.FF1C6809@rostock.zgdv.de> Date: Fri, 20 Nov 1998 11:10:47 +0100 From: Thomas Runge Organization: http://www.rostock.zgdv.de X-Mailer: Mozilla 4.04 [en] (X11; U; SunOS 5.6 sun4u) Mime-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: Netscape4.5, 3.0-current-elf, libXt.so.6.0 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > /usr/X11R6/lib/libXt.so.6.0: ELF 32-bit LSB shared object, Intel 80386, > version 1 (FreeBSD), not stripped > > Am I f*cked^h^h^h^h^hlost? > No. Just get a copy of the "old" a.out libs and install it under /usr/X11R6/lib/aout. -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 06:08:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06304 for freebsd-current-outgoing; Fri, 20 Nov 1998 06:08:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA06291 for ; Fri, 20 Nov 1998 06:08:25 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KCZKISEJ; Fri, 20 Nov 98 14:07:55 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981120150754.009c4100@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Fri, 20 Nov 1998 15:07:54 +0100 To: Archie Cobbs , mi@aldan.algebra.com (Mikhail Teterin) From: Marius Bendiksen Subject: Re: strings in the kernel (was: snprintf() in the kernel) Cc: current@FreeBSD.ORG In-Reply-To: <199811200512.VAA18941@bubba.whistle.com> References: <199811191355.NAA03525@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Sounds like a job for mr. linker.. is there support >the smashing together of identical strings in the >text segment? How could you get sum up how much is wasted with shared substrings as well? --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 06:30:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA08843 for freebsd-current-outgoing; Fri, 20 Nov 1998 06:30:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA08832 for ; Fri, 20 Nov 1998 06:30:30 -0800 (PST) (envelope-from jfieber@fallout.campusview.indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.9.1/8.9.1) with ESMTP id JAA05870; Fri, 20 Nov 1998 09:28:35 -0500 (EST) Date: Fri, 20 Nov 1998 09:28:35 -0500 (EST) From: John Fieber To: Barrett Richardson cc: garman@earthling.net, current@FreeBSD.ORG Subject: Re: more dying daemons In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Nov 1998, Barrett Richardson wrote: > That will give you another 256 mb of swap (may have to trim to > availability of disk space). If your swap usage stabilizes at > some point and your box lives, then you've nailed the problem. High swap usage isn't (apparently) the problem being pursued here. Rather it appears to be a trigger factor. A system configured with a small amount of swap makes testing easier. Configuring more swap makes seems to make the problem go away...mostly...but not really.a -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 07:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12429 for freebsd-current-outgoing; Fri, 20 Nov 1998 07:10:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from aldan.algebra.com (kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12423 for ; Fri, 20 Nov 1998 07:10:39 -0800 (PST) (envelope-from mi@aldan.algebra.com) Received: (from mi@localhost) by aldan.algebra.com (8.8.8/8.8.7) id PAA09911; Fri, 20 Nov 1998 15:07:49 GMT (envelope-from mi) From: Mikhail Teterin Message-Id: <199811201507.PAA09911@aldan.algebra.com> Subject: Re: Netscape4.5, 3.0-current-elf, libXt.so.6.0 In-Reply-To: from Leif Neland at "Nov 20, 1998 08:58:57 am" To: root@swimsuit.internet.dk (Leif Neland) Date: Fri, 20 Nov 1998 15:07:48 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18942 for freebsd-current-outgoing; Fri, 20 Nov 1998 08:18:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18934 for ; Fri, 20 Nov 1998 08:18:13 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA03506; Fri, 20 Nov 1998 08:17:43 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id IAA17967; Fri, 20 Nov 1998 08:17:42 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199811200458.UAA00791@wall.polstra.com> Date: Fri, 20 Nov 1998 08:17:42 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: garman@earthling.net Subject: Re: more dying daemons Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20-Nov-98 garman@earthling.net wrote: >> >> sysctl -w kern.fast_vfork=0 >> > unfortunately this didn't have any effect :( inetd and samba still die > as before :( i'll keep my machine running with this knob turned and > see if anything else turns up that might be a clue. Thanks for trying it. Too bad it didn't make any difference. You might as well go back to the default value of 1 at this point. At 0, its net effect is more or less to make vfork() act like fork(). Since it didn't solve the dying daemons problem, you're better off with the default value. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 08:52:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22182 for freebsd-current-outgoing; Fri, 20 Nov 1998 08:52:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22170 for ; Fri, 20 Nov 1998 08:52:25 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id IAA03616; Fri, 20 Nov 1998 08:51:55 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id IAA18059; Fri, 20 Nov 1998 08:51:55 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 20 Nov 1998 08:51:55 -0800 (PST) Message-Id: <199811201651.IAA18059@vashon.polstra.com> To: obrien@NUXI.com Subject: Re: snprintf() in the kernel Newsgroups: polstra.freebsd.current In-Reply-To: <19981119203050.A4033@nuxi.com> References: <19981120093817.K467@freebie.lemis.com> <199811200057.QAA29023@bubba.whistle.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981119203050.A4033@nuxi.com>, David O'Brien wrote: > > The only subtle gotcha with snprintf() is that it returns > > the number of characters that *would* have been printed, > > not the number that actually were printed. > > So, create a new function called ksprintf() that has the calling semantics > of sprintf(), but the return semantics you like. Too confusing. Either make it act exactly like snprintf() (or at least a subset), or give it a dissimilar name. Extra much so, since there's unlikely to be a man page for the new function. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 09:01:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22912 for freebsd-current-outgoing; Fri, 20 Nov 1998 09:01:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22904 for ; Fri, 20 Nov 1998 09:01:52 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id JAA03653; Fri, 20 Nov 1998 09:01:22 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id JAA18109; Fri, 20 Nov 1998 09:01:22 -0800 (PST) (envelope-from jdp@polstra.com) Date: Fri, 20 Nov 1998 09:01:22 -0800 (PST) Message-Id: <199811201701.JAA18109@vashon.polstra.com> To: oleg@ogurok.com Subject: Re: Can't "make world" to update 3.0-RELEASE to STABLE. Newsgroups: polstra.freebsd.current In-Reply-To: <01fb01be143e$db4df600$67e0fecc@nexus.globix.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <01fb01be143e$db4df600$67e0fecc@nexus.globix.net>, Oleg Ogurok wrote: > I just installed fresh version of 3.0-RELEASE, installed cvsup and got = > CURENT sources, then I tried to "make world", but got an error. Your subject line says "STABLE" and here you say current. Which one is it really? > Then I removed all /usr/src/ and ran cvsup again. Here's what I am = > getting (last 100 lines). The config file for cvsup I got from = > /usr/src/share/cvsup/ I believe. In order to help you, we need to see the actual CVSup config file. > cc -O -I/usr/src/gnu/usr.bin/ld/rtld/.. -I/usr/src/gnu/usr.bin/ld/rtld = > -I/usr/src/gnu/usr.bin/ld/rtld/../i386 -fpic -fno-function-cse -DRTLD = > -I/usr/obj/usr/src/tmp/usr/include -nostdlib -Wl,-Bshareable = > -Wl,-Bsymbolic -Wl,-assert -Wl,nosymbolic -o ld.so mdprologue.o rtld.o = > malloc.o shlib.o md.o support.o sbrk.o -lc_pic -lgcc_pic > mdprologue.o(.text+0x22): undefined reference to `_rtld' > mdprologue.o(.text+0x40): undefined reference to `_binder' > rtld.o: In function `reloc_map': > rtld.o(.text+0xe99): undefined reference to `binder_entry' > *** Error code 1 This directory "src/gnu/usr.bin/ld/rtld" doesn't exist in 3.0 or in -current. This indicates that either (a) your source tree is all screwed up, or (b) you are trying to downgrade from 3.0 to -stable. If (b), then you need to know that it's probably not possible, and definitly not easy. My guess is that you intended to upgrade from 3.0 to -current. But you used a supfile that got you -stable instead. If that's what happened, then I suggest that you delete your source tree, fix your supfile, and try again. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 10:10:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29981 for freebsd-current-outgoing; Fri, 20 Nov 1998 10:10:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ogurok.com (ogurok.com [208.212.72.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29976 for ; Fri, 20 Nov 1998 10:10:50 -0800 (PST) (envelope-from oleg@ogurok.com) Received: from homepc (ppp07.pfmc.net [204.254.227.9]) by ogurok.com (8.9.1/8.9.1) with SMTP id NAA08225; Fri, 20 Nov 1998 13:14:00 -0500 (EST) (envelope-from oleg@ogurok.com) Message-ID: <007801be14b1$e448dd60$09e3fecc@homepc> From: "Oleg Ogurok" To: "Leif Neland" , "Thomas Runge" Cc: Subject: Re: Netscape4.5, 3.0-current-elf, libXt.so.6.0 Date: Fri, 20 Nov 1998 13:16:22 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think you need to install security sources (DES, Kerberos, etc..). Last time I didn't do that and I couldn't even run fvwm2. -Oleg. -----Original Message----- From: Leif Neland To: Thomas Runge Cc: freebsd-current@FreeBSD.ORG Date: Friday, November 20, 1998 5:10 AM Subject: Re: Netscape4.5, 3.0-current-elf, libXt.so.6.0 > > >On Fri, 20 Nov 1998, Thomas Runge wrote: > >> Leif Neland wrote: >> > >> > I can't start netscape: >> > (netscape-4.5-navigator, cvsupped today) >> > >> > ld.so failed: Can't find shared library "libXt.so.6.0" >> > >> > But I have it: >> > >> >> > >> > Now what? >> >> The last two libs are irrelevant. And the first lib >> is (I guess) elf, while netscape is still aout. >> >> If your X-libs are still aout, you could change your >> LD_LIBRARY_PATH or reconfigure via ldconfig. >> > >/usr/X11R6/lib/libXt.so.6.0: ELF 32-bit LSB shared object, Intel 80386, >version 1 (FreeBSD), not stripped > > >Am I f*cked^h^h^h^h^hlost? > >Leif > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 12:07:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10543 for freebsd-current-outgoing; Fri, 20 Nov 1998 12:07:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10538; Fri, 20 Nov 1998 12:07:37 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.47]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA24C5; Fri, 20 Nov 1998 20:07:01 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 20 Nov 1998 21:11:51 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current , FreeBSD Current , FreeBSD Security Subject: FW: NetBSD Security Advisory 1998-005 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Might be interesting, I sended it to Current as well regarding the mentioning of mmap (dying Daemons mayhaps?) Sorry if that was not appropriate, but to me it seemed that way... FYI, -----FW: <24978.911534701@eterna.com.au>----- Date: Fri, 20 Nov 1998 15:05:01 +1100 Sender: netbsd-announce-owner@netbsd.org From: matthew green To: netbsd-announce@netbsd.org Subject: NetBSD Security Advisory 1998-005 Cc: tech-security@netbsd.org, current-users@netbsd.org, bugtraq@netspace.org, cert@cert.org, auscert@auscert.org.au -----BEGIN PGP SIGNED MESSAGE----- NetBSD Security Advisory 1998-005 --------------------------------- Topic: Problem with mmap(2) and many drivers. Version: NetBSD 1.3.2 and prior; NetBSD-current to 19981120. Severity: Local users may be able to access physical and device memory or cause system instability. Abstract - -------- Many character device drivers that provide mmap access do not properly bounds check their arguments. The impact of this varies widely across each affected driver. Some drivers allow access to portions of physical or device memory or may cause the system to panic or act unreliably. Technical Details - ----------------- The NetBSD character device d_mmap driver-provided service entry is called by the device page fault routine to check for valid access and return a machine dependant value (normally a physicaly address or a page frame number) used to create a virtual to physical address mapping. One of the arguments to the d_mmap() routine is `int offset;' which is a signed value. Many of the device drivers which implement mmap access do not properly check for negative values, each having different failure modes. For example, on NetBSD/i386 the text console drivers can be fooled into allowing the console user access to physical memory from 0 to 640KB, but on NetBSD/macppc, the console driver may allow the console user access to any memory location. The NetBSD d_mmap interface was inherited by NetBSD from 4.4BSD, and there may be problems in other 4.4BSD derived operating systems. Solutions and Workarounds - ------------------------- NetBSD 1.3.2 users should upgrade to NetBSD 1.3.3 when it becomes available, or apply the following patch to their kernel source and rebuild their kernel. ftp://ftp.netbsd.org/pub/NetBSD/misc/security/patches/19981120-d_mmap NetBSD-current users should update to a source tree newer than 19981120 and rebuild their kernel. If these actions can not be taken, the following section can be used to remove access to devices at the file system level, on a per-port and per-device basis. Port and Device Specific Details - -------------------------------- Below are the NetBSD port and device specific details for each of the affected drivers. These do not list `attacks' possible for someone who is already root, or do not elevate current access. This list may be incomplete or even incorrect; the best efforts have been made to ensure its accuracy in the time permitted. NetBSD/arm32 and NetBSD/i386 specific problems: The pccons and pcvt console drivers allow access from 0 to the base address of video memory (640KB). These drivers must be associated with the system console and are normally only exploitable to the user logged in on the console. Device: /dev/ttyv? NetBSD/arm32 specific problems: On the RISCPC and RC7500 models the physical console driver allows access from 0 to the base address of video memory. These drivers must be associated with the system console and the device nodes for these may not even exist. Device: no default device. NetBSD/mac68k specific problems: The grf console driver allows access from 0 to the base address of video memory. This driver must be associated with the system console and is normally only exploitable to the user logged in on the console. The Apple Sound Chip (asc) driver which provides access to Apple Sound and console bell support may allow access to page 0 to anyone. Both of these drivers may also cause unpredictable system activity. Devices: /dev/grf* & /dev/asc* NetBSD/macppc (not available in NetBSD 1.3.2) specific problems: The nvram d_mmap routine incorrectly returns EOPNOTSUPP instead of -1 to indicate error, possibly causing the system to panic. This is exploitable by anyone. The ofb driver allows console users access to any memory location. Devices: /dev/nvram and no default device for ofb. NetBSD/sparc specific problems: The cgeight and cgfour console drivers allow access from 0 to the base address of video memory (0x500000), or may cause unpredictable system activity. These drivers must be associated with the system console and are normally only exploitable to the user logged in on the console. Devices: /dev/fb, /dev/cgfour* & /dev/cgeight* NetBSD/vax specific problems: The smg console driver may allow the console user access to memory from 0 to 128KB and may cause the unpredictable system activity. Note that this not a problem in NetBSD/vax 1.3.2. Device: /dev/vt* PCI device specific problems: The tga console driver allow access from 0 to the base address of video memory. This drivers must be associated with the system console and is normally only exploitable to the user logged in on the console. Device: /dev/ttyE? Turbo Channel (pmax & alpha) device specific problems: The cfb, sfb, mfb and xcfb console drivers allow access from 0 to the base address of video memory, or may cause unpredictable system activity. These drivers must be associated with the system console and are normally only exploitable to the user logged in on the console. Note that these devices are only available in the TurboChannel Alpha models. Device: /dev/fb? (pmax) & /dev/ttyE? (alpha) Thanks To - --------- Many thanks to Chris G. Demetriou and Ted Lemon for finding the original problem. Chris also provided an initial investigation & analysis of the problem. Matthew Green found, analysed and fixed the system as a whole. Tsubai Masanari provided technical input for the NetBSD/macppc port and Kazuki Sakamoto provided technical input for the NetBSD/bebox port. More Information - ---------------- Information about NetBSD and NetBSD security can be found at http://www.NetBSD.ORG/ and http://www.NetBSD.ORG/Security/. Copyright 1998, The NetBSD Foundation, Inc. All Rights Reserved. $NetBSD: NetBSD-SA1998-005.txt,v 1.3 1998/11/20 04:06:27 mrg Exp $ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQCVAwUBNlTp7D5Ru2/4N2IFAQGVrAQApqIKBLZ+7xHpz7k1ZM5pD/WH66B5a1EI B6Oj8u8De14GApHSwzv69Trh8b5NfztiIXbTn1JKHPrTNDuWsHP/Vox6HZkJ6G/F Gf7Wb524zyeLZAARJB/z5G9NnsxESsckgldH+WHvcNrg/Osrt74EKaxr2tBh9+OT 9Hl6B2KWP2I= =7Yke -----END PGP SIGNATURE----- --------------End of forwarded message------------------------- --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 12:17:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12126 for freebsd-current-outgoing; Fri, 20 Nov 1998 12:17:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12106; Fri, 20 Nov 1998 12:17:05 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.47]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA16C2; Fri, 20 Nov 1998 21:16:36 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <001001be13fb$5a3fc400$8501a8c0@bobm> Date: Fri, 20 Nov 1998 21:21:23 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Bob McWilliams Subject: RE: Driver and system builds Cc: freebsd-doc@FreeBSD.ORG, FreeBSD Current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Nov-98 Bob McWilliams wrote: > Hello, I am Bob McWilliams the technical marketing person at Initio. We > would like to find out how to post links and information about getting our > public BSD code included in current and future BSD releases. I can be > reached at Initio form 8-5 Pacific time Mon - Fri. 408-577-1919 x5049 or by > e-mail bobm@initio.com Could ye elaborate on the posting links and information? If ye want to get the sources included it's quite easy, at least I think it is, mayhaps the `senior' developers want to provide the details? (Hence cc:-ing to CURRENT) http://www.initio.com/whichprd.htm <--- I applaud you for that URL... I think that once we get the drivers even FreeBSD (NetBSD, OpenBSD) specific, if they are not already --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 13:47:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23366 for freebsd-current-outgoing; Fri, 20 Nov 1998 13:47:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23361 for ; Fri, 20 Nov 1998 13:47:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id NAA00801 for ; Fri, 20 Nov 1998 13:47:18 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811202147.NAA00801@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: warning - setsockopt MRT_DEL_MFC: Operation?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Nov 1998 13:47:18 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nov 20 13:45:19 rah mrouted[788]: warning - steal_sources trying to delete (128.32.120.180 224.0.1.32): Operation not supported Nov 20 13:45:19 rah mrouted[788]: warning - setsockopt MRT_DEL_MFC: Operation not supported Nov 20 13:45:19 rah mrouted[788]: warning - steal_sources trying to delete (199.0.232.246 224.2.135.86): Operation not supported Nov 20 13:45:20 rah mrouted[788]: warning - setsockopt MRT_ADD_MFC: Operation not supported I am getting the above error messages when I run mrouted. I did compile the kernel with option MROUTING. Tnks, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 14:38:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29492 for freebsd-current-outgoing; Fri, 20 Nov 1998 14:38:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (pm3-47.ppp.wenet.net [206.15.85.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29487 for ; Fri, 20 Nov 1998 14:38:11 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id BAA12873; Fri, 20 Nov 1998 01:43:14 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Fri, 20 Nov 1998 01:43:13 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Mike Smith cc: current Subject: Re: New bootloader oddities In-Reply-To: <199811200920.BAA00658@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Nov 1998, Mike Smith wrote: > If it's printed the message, it's finished with the probe. It's likely > that it was looking for something else and either hung or you got > impatient before it timed out. Normal procedure as documented by > anyone that's ever written up the configuration process is to disable > everything that you don't have using userconfig; if you haven't tried > this, you should. Ehm. The output I showed was from an a.out kernel which works fine. The _ELF_ kernel, and the bootblocks don't detect anything. The _ELF_ kernel hangs after printing the initial probing for PnP devices message.. - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD http://www.freebsd.org/ | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 15:33:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07100 for freebsd-current-outgoing; Fri, 20 Nov 1998 15:33:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07092 for ; Fri, 20 Nov 1998 15:33:36 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id PAA04816 for ; Fri, 20 Nov 1998 15:33:06 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id PAA18803 for current@freebsd.org; Fri, 20 Nov 1998 15:33:06 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 20 Nov 1998 15:33:05 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@FreeBSD.ORG Subject: HEADS UP: Install new /etc/pam.conf file from /usr/src/etc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just committed a new file "src/etc/pam.conf", which controls the PAM authentication methods used by login and (some day) other such utilities. Users of FreeBSD-current should install this file into "/etc". Kerberos users should uncomment the entry for KerberosIV. See pam(8) for a description of the file's format. For those folks who haven't heard about it, PAM stands for Pluggable Authentication Modules. It is a flexible way to configure the kinds of authentication (passwd/NIS, S/Key, Kerberos, RADIUS, TACACS+) used in your system. Each authentication method is encapsulated in an application-independent PAM module, a shared object. Under control of the pam.conf file, the PAM library loads the selected modules, calls well-defined entry points in them, and gets back results indicating whether the user was successfully authenticated by each module. This means that entirely new authentication methods (say, KerberosV) can be introduced in the future, without recompiling or even relinking login or other such applications. Also, sysadmins can change or reorder the selection of authentication methods on their systems without recompiling or rebuilding anything. All it takes is an edit of "/etc/pam.conf". Later today, I'll be committing the changes to "/usr/bin/login" to make it use PAM. There is a fallback mechanism that serves as a safety net and transition aid. If login cannot find an "/etc/pam.conf" file, or if some other fatal PAM error occurs, it will fall back on passwd/NIS authentication. It will also log an error via syslog describing what problem it encountered. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 15:43:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA08400 for freebsd-current-outgoing; Fri, 20 Nov 1998 15:43:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from B1FF.nas.nasa.gov (b1ff.nas.nasa.gov [129.99.34.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA08394 for ; Fri, 20 Nov 1998 15:43:40 -0800 (PST) (envelope-from rone@B1FF.nas.nasa.gov) Received: (from rone@localhost) by B1FF.nas.nasa.gov (8.8.8/8.8.8) id PAA21556; Fri, 20 Nov 1998 15:43:06 -0800 (PST) (envelope-from rone) From: Ron Echeverri Message-Id: <199811202343.PAA21556@B1FF.nas.nasa.gov> Subject: Re: "pidentd" is broken In-Reply-To: <19981120171210.A4863@Denninger.Net> from Karl Denninger at "Nov 20, 1998 5:12:10 pm" To: karl@Denninger.Net (Karl Denninger) Date: Fri, 20 Nov 1998 15:43:06 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Denninger writes: > Just FYI. It was ok up to a week or so ago. No dice. It returns both bogus port numbers and "UNKNOWN-ERROR" to valid requests. Kernel from today, 3.0-CURRENT, system "make world"d today as well. Ah, you want the -current mailing list, then. rone -- Ron Echeverri Numerical Aerospace Simulation Facility DSS/Usenet Administrator NASA Ames Research Center Sterling Software Mountain View, CA x42771 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 18:31:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27158 for freebsd-current-outgoing; Fri, 20 Nov 1998 18:31:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27153 for ; Fri, 20 Nov 1998 18:31:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id SAA00465 for ; Fri, 20 Nov 1998 18:31:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811210231.SAA00465@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: warning - setsockopt MRT_DEL_MFC: Operation?? In-reply-to: Your message of "Fri, 20 Nov 1998 13:47:18 PST." <199811202147.NAA00801@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Nov 1998 18:31:14 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Someone forgot a "break" in ip_mroute.c: case MRT_ADD_MFC: case MRT_DEL_MFC: error = sooptcopyin(sopt, &mfc, sizeof mfc, sizeof mfc); if (error) { break; } if (sopt->sopt_name == MRT_ADD_MFC) error = add_mfc(&mfc); else error = del_mfc(&mfc); break; ^^^^^^^^^^^^ missing "break" which was causing the operation to return EOPNOTSUPP. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 19:14:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01121 for freebsd-current-outgoing; Fri, 20 Nov 1998 19:14:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01092 for ; Fri, 20 Nov 1998 19:13:58 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA05517; Fri, 20 Nov 1998 19:12:30 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma005512; Fri, 20 Nov 98 19:12:27 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA25314; Fri, 20 Nov 1998 19:12:26 -0800 (PST) From: Archie Cobbs Message-Id: <199811210312.TAA25314@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <19981120093817.K467@freebie.lemis.com> from Greg Lehey at "Nov 20, 98 09:38:17 am" To: grog@lemis.com, rnordier@nordier.com Date: Fri, 20 Nov 1998 19:12:26 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As promised, here are the patches to add [v]snprintf() to the kernel and fix a zillion occurrences of sprintf() and str[n]cpy()... ftp://ftp.whistle.com/pub/archie/misc/SNPRINTF.patch.gz There are 124 files affected.. so reviews are much appreciated! Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 20:07:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05360 for freebsd-current-outgoing; Fri, 20 Nov 1998 20:07:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05353 for ; Fri, 20 Nov 1998 20:07:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA20321; Fri, 20 Nov 1998 20:07:22 -0800 (PST) (envelope-from dillon) Date: Fri, 20 Nov 1998 20:07:22 -0800 (PST) From: Matthew Dillon Message-Id: <199811210407.UAA20321@apollo.backplane.com> To: Archie Cobbs Cc: grog@lemis.com, rnordier@nordier.com, freebsd-current@FreeBSD.ORG Subject: Re: snprintf() in the kernel References: <199811210312.TAA25314@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :As promised, here are the patches to add [v]snprintf() to the kernel :and fix a zillion occurrences of sprintf() and str[n]cpy()... : : ftp://ftp.whistle.com/pub/archie/misc/SNPRINTF.patch.gz : :There are 124 files affected.. so reviews are much appreciated! : :Thanks, :-Archie :___________________________________________________________________________ :Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com I'll take a pass through them. The very first one has a bug... not in the snprintf(), but in the size of the buffer: static char unk[8]; int i; ... sprintf(unk, "0x%x", op); ^^^^^^ looks like up to 11 characters to me. The buffer is only 8. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 20:18:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA06165 for freebsd-current-outgoing; Fri, 20 Nov 1998 20:18:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org ([192.195.231.211]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA06160 for ; Fri, 20 Nov 1998 20:18:19 -0800 (PST) (envelope-from garman@garman.dyn.ml.org) Message-Id: <199811210418.UAA06160@hub.freebsd.org> Received: (qmail 2946 invoked from smtpd); 21 Nov 1998 04:18:06 -0000 Received: from localhost.garman.net (HELO garman.dyn.ml.org) (127.0.0.1) by localhost.garman.net with SMTP; 21 Nov 1998 04:18:06 -0000 Date: Fri, 20 Nov 1998 23:18:05 -0500 (EST) From: garman@earthling.net Reply-To: garman@earthling.net Subject: Re: more dying daemons To: terbart@aye.net cc: current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Nov, Barrett Richardson wrote: > > Swap usage at 64% after only hour seems awfully high. I've seem similar > behaviour in the world of SCO. Folks just under the threshold of what > they can get out of their box with given swap/memory size with 3.2v4.2 > are having no problems. They upgrade to Open Server 5, put the same load > on it, and the box starts a slow downward spiral and finally becomes > unusable. They reboot it, and its ok for a couple of hours. > The 64% swap usage figure was from an uptime of two days, not an hour. I have however easily produced swap usages around 56-58% (synthetically, of course) within 10-20 minutes while testing some of the potential fixes posted here. i've never had a problem with insufficient swap before... > You can use vnconfig to test the beast without reslicing if you > have ample disk space. > yes, but isn't this just a workaround? I rarely (if ever) run out of memory and swap, and my usage usually stabilizes around 65% after a few days. i would expect a system to behave reasonably even in the face of memory shortages. corrupting running processes (when they fork?) is not a reasonable behavior. > If problems persist, entertain the idea that something you > are using has a mongo memory leak. > basically this is just my personal workstation box. whats running include netscape, tkrat (with huge mailboxes :/), windowmaker, and various other X apps. nothing particularly suspect (except perhaps for netscape :)) enjoy -- Jason Garman http://garman.dyn.ml.org/ Student, University of Maryland garman@earthling.net And now... did you know that: Whois: JAG145 "If you fart consistently for 6 years and 9 months, enough gas is produced to create the energy of an atomic bomb." -- 0xdeadbeef posting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 21:18:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA10405 for freebsd-current-outgoing; Fri, 20 Nov 1998 21:18:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA10390; Fri, 20 Nov 1998 21:18:55 -0800 (PST) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id NAA28586; Sat, 21 Nov 1998 13:18:26 +0800 (GMT) Date: Sat, 21 Nov 1998 13:18:26 +0800 (GMT) From: Michael Robinson Message-Id: <199811210518.NAA28586@public.bta.net.cn> To: syssgm@dtir.qld.gov.au Subject: Re: writev() to tcp Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stephen McKay writes: >On Tuesday, 17th November 1998, Michael Robinson wrote: >>If someone sent a PR, would this get fixed? (The Squid FAQ has a one-line >>patch to uipc_socket.c.) > >That patch went into -current on 1998/07/06 but was removed on 1998/07/18 >because various and sundry things broke. See revisions 1.41 and 1.42 >of sys/kern/uipc_socket.c. There was some inconclusive discussion of >the problem at the time, probably on freebsd-current. My own personal >experience of using this patch was also inconclusive. Some things got >better, but some things became worse and I didn't manage to prove that >the patch was to blame, or that it was innocent. Feel free to experiment! I installed that patch into 2.2.7-RELEASE, and have been experiencing exactly the problems that were discussed on freebsd-current in the "State of current..." thread of the time. So, it appears the patch is guilty as charged. Which brings us back to where we started. Squid and ORBit (at the very least) exhibit severe performance degradation with the current MLEN < write length < MINCLSIZE bug. There isn't an open PR (that I can find), and the Squid FAQ advocates a kernel patch that breaks X Windows (among other things). If someone who is familiar with the fundamental problem could explain it to me in more detail, along with some possible solutions, I could try to play with it. Otherwise I'll just open a PR, and hope someone else eventually fixes it. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 21:37:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11680 for freebsd-current-outgoing; Fri, 20 Nov 1998 21:37:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11670 for ; Fri, 20 Nov 1998 21:37:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA20822; Fri, 20 Nov 1998 21:37:21 -0800 (PST) (envelope-from dillon) Date: Fri, 20 Nov 1998 21:37:21 -0800 (PST) From: Matthew Dillon Message-Id: <199811210537.VAA20822@apollo.backplane.com> To: Archie Cobbs , grog@lemis.com, rnordier@nordier.com, freebsd-current@FreeBSD.ORG Subject: Re: snprintf() in the kernel References: <199811210312.TAA25314@bubba.whistle.com> <199811210407.UAA20321@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've gone through your diffs. I found what I believe to be one genuine bug, but read the notes and stuff below... you may have a problem with some of the strncpy()'s you converted to snprintf's. General comments: * found a few minor bugs. * noticed a number of 'scary uses' in original code were fixed, kudos! * noticed a few bugs in the original code were fixed, kudos! For example, a number of strncpy()'s assume zero-termination. strncpy() does not zero-terminate in the exact-length case. Notes: It should be noted that the FreeBSD strncpy() will zero-fill the destination. snprintf() does not. This may or may not matter. It didn't seem to be important in what I saw in my review but you should review the disklabel-related snprintf()'s. Also review zero-termination cases for disklabels... make sure disklabel isn't designed to allow a full-length string (without zero-termination) else your snprintf()'s have broke something. I noticed a number of strncpy()'s were using sizeof(the_buffer_name), which might have been on purpose! snprintf() will break that. -Matt alpha/alpha/db_disasm.c line 196, static char unk[8]; ... buffer is not big enough. Needs to be at least 11. The snprintf() prevents a possible overflow (a bug fixed!), but the buffer should probably be made larger anyway. cam/scsi/scsi_all.c line 1566, char holdstr[8] was totally broken anyway, it wasn't big enough (needs to be 10). Your patch removes it which is good. A second bug fixed! dev/buslogin/bt.c Boy, weren't we lucky that all BT model names were 4 characters! dev/dpt/dpt_control.c This doesn't look right, you forgot to remove the strncpy and replace it with the snprintf, but added the extra sizeof() argument as if you had. @@ -782,7 +783,8 @@ compat_softc.ha_npend = dpt->submitted_ccbs_coun t; compat_softc.ha_active_jobs = dpt->waiting_ccbs_ count; strncpy(compat_softc.ha_fw_version, - dpt->board_data.firmware, 4); + dpt->board_data.firmware, + sizeof(compat_softc.ha_fw_version)); compat_softc.ha_ccb = NULL; compat_softc.ha_cblist = NULL; i386/isa/mcd.c (Looks like you fixed a bug here... the strncpy was assuming zero termination) netatm/spans/spans_print.c (Hey, nice, you fixed another bug, at least if someone ever made saddr and daddr differently sized). - strncpy(daddr, spans_addr_print(&stind_p->stind_es_addr), - sizeof(daddr)); - strncpy(saddr, spans_addr_print(&stind_p->stind_sw_addr), - sizeof(daddr)); + snprintf(daddr, sizeof(daddr), + "%s", spans_addr_print(&stind_p->stind_es_addr)); + snprintf(saddr, sizeof(daddr), + "%s", spans_addr_print(&stind_p->stind_sw_addr)); printf("sw_epoch=0x%lx, es_addr=%s, sw_addr=0x%s", ... netatm/spans/spans_util.c: I'm not sure about these ntohl() calls. Some of the defines just macro the arguments through, others are routines, but historically ntohl() has operated on a 32 bit quantity so we should probably cast to ntohl() results to (long) in the s*printf() calls as well as do the sprintf()->snprintf() conversion. RCS file: /cvs/freebsd/src/sys/netatm/spans/spans_util.c,v retrieving revision 1.3 diff -u -r1.3 spans_util.c --- spans_util.c 1998/10/31 20:06:56 1.3 +++ spans_util.c 1998/11/21 03:03:09 @@ -441,7 +441,7 @@ /* * Print and return the string */ - sprintf(strbuff, "%lx.%lx", ntohl(u1.w), ntohl(u2.w)); + snprintf(strbuff, sizeof(strbuff), "%lx.%lx", ntohl(u1.w), ntohl(u2.w)); return(strbuff); } netinet/ip_divert.c: You might have to zero-fill unused space in sin_zero. I'm not sure. @@ -217,9 +216,9 @@ * this iface name will come along for the ride. * (see div_output for the other half of this.) */ - sprintf(name, "%s%d", - m->m_pkthdr.rcvif->if_name, m->m_pkthdr.rcvif->if_unit); - strncpy(divsrc.sin_zero, name, 7); + snprintf(divsrc.sin_zero, sizeof(divsrc.sin_zero), + "%s%d", m->m_pkthdr.rcvif->if_name, + m->m_pkthdr.rcvif->if_unit); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 22:15:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14169 for freebsd-current-outgoing; Fri, 20 Nov 1998 22:15:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14164 for ; Fri, 20 Nov 1998 22:15:07 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA24812; Sat, 21 Nov 1998 17:14:20 +1100 Date: Sat, 21 Nov 1998 17:14:20 +1100 From: Bruce Evans Message-Id: <199811210614.RAA24812@godzilla.zeta.org.au> To: archie@whistle.com, grog@lemis.com, rnordier@nordier.com Subject: Re: snprintf() in the kernel Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >As promised, here are the patches to add [v]snprintf() to the kernel >and fix a zillion occurrences of sprintf() and str[n]cpy()... > > ftp://ftp.whistle.com/pub/archie/misc/SNPRINTF.patch.gz It would have been easier to review if it were here: >[here] >There are 124 files affected.. so reviews are much appreciated! snprintf returns a value which is almost always ignored. Most of the strncpy -> snprintf changes are dubious, since strncpy is often used for character arrays that aren't strings. The changes for disk labels are certainly wrong. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 22:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14761 for freebsd-current-outgoing; Fri, 20 Nov 1998 22:22:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14756 for ; Fri, 20 Nov 1998 22:22:56 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA06372; Fri, 20 Nov 1998 22:21:03 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma006370; Fri, 20 Nov 98 22:20:43 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA25723; Fri, 20 Nov 1998 22:20:43 -0800 (PST) From: Archie Cobbs Message-Id: <199811210620.WAA25723@bubba.whistle.com> Subject: Re: snprintf() in the kernel In-Reply-To: <199811210537.VAA20822@apollo.backplane.com> from Matthew Dillon at "Nov 20, 98 09:37:21 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 20 Nov 1998 22:20:43 -0800 (PST) Cc: grog@lemis.com, rnordier@nordier.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > I've gone through your diffs. I found what I believe to be one genuine > bug, but read the notes and stuff below... you may have a problem with > some of the strncpy()'s you converted to snprintf's. Thanks very much! I didn't realize that the kernel strncpy() did a zero fill.. that makes the analysis more complicated. > dev/dpt/dpt_control.c > > This doesn't look right, you forgot to remove the strncpy and replace it > with the snprintf, but added the extra sizeof() argument as if you had. > > strncpy(compat_softc.ha_fw_version, > - dpt->board_data.firmware, 4); > + dpt->board_data.firmware, > + sizeof(compat_softc.ha_fw_version)); > compat_softc.ha_ccb = NULL; > compat_softc.ha_cblist = NULL; I actually left this one alone (sizeof(compat_softc.ha_fw_version) == 4) because it was impossible to determine whether this string is supposed to be nul-terminated or not .. the "ha_fw_version" field is not used anywhere in the kernel! So I don't know if it needs a nul or not. > netatm/spans/spans_util.c: > > I'm not sure about these ntohl() calls. Some of the defines just > macro the arguments through, others are routines, but historically > ntohl() has operated on a 32 bit quantity so we should probably > cast to ntohl() results to (long) in the s*printf() calls as well > as do the sprintf()->snprintf() conversion. Agreed.. it could matter on alpha hardware. > netinet/ip_divert.c: > > You might have to zero-fill unused space in sin_zero. I'm not sure. Hmm.. since Julian invented this hack I guess we can declare that "it doesn't have to be zero filled" :-) I'll work on adjusting for the concerns you pointed out.. Thanks, -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 22:33:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15477 for freebsd-current-outgoing; Fri, 20 Nov 1998 22:33:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15471 for ; Fri, 20 Nov 1998 22:33:41 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id XAA05877; Fri, 20 Nov 1998 23:25:51 -0700 (MST) Date: Fri, 20 Nov 1998 23:25:51 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811210625.XAA05877@narnia.plutotech.com> To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: snprintf() in the kernel X-Newsgroups: pluto.freebsd.current In-Reply-To: <199811210312.TAA25314@bubba.whistle.com> <199811210407.UAA20321@apollo.backplane.com> <199811210537.VAA20822@apollo.backplane.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199811210537.VAA20822@apollo.backplane.com> you wrote: > General comments: ... > * noticed a few bugs in the original code were fixed, kudos! For > example, a number of strncpy()'s assume zero-termination. strncpy() > does not zero-terminate in the exact-length case. Exactly. Many of the uses of strncpy removed from the CAM code fall into this category. > cam/scsi/scsi_all.c > > line 1566, char holdstr[8] was totally broken anyway, it wasn't big > enough (needs to be 10). Your patch removes it which is good. > A second bug fixed! Last I checked, an unsigned byte value represented in hex took 2 bytes. The space and the null terminator add 2 more bytes. That makes holdstr too big by 4 bytes. > dev/buslogin/bt.c > > Boy, weren't we lucky that all BT model names were 4 characters! Of course they are always 4 characters long. How do you think the programmer determined the correct amount of space to allocate for the name information in the first place? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 22:38:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA15852 for freebsd-current-outgoing; Fri, 20 Nov 1998 22:38:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA15846 for ; Fri, 20 Nov 1998 22:38:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA21040; Fri, 20 Nov 1998 22:38:16 -0800 (PST) (envelope-from dillon) Date: Fri, 20 Nov 1998 22:38:16 -0800 (PST) From: Matthew Dillon Message-Id: <199811210638.WAA21040@apollo.backplane.com> To: "Justin T. Gibbs" Cc: current@FreeBSD.ORG Subject: Re: snprintf() in the kernel References: <199811210625.XAA05877@narnia.plutotech.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ::> ::> Boy, weren't we lucky that all BT model names were 4 characters! :: ::Of course they are always 4 characters long. How do you think the programmer ::determined the correct amount of space to allocate for the name information ::in the first place? :: ::-- ::Justin Well, yes, but the obvious problem is that at some future point someone adds a 5-character model and, BEWM. In general, this is why we need either snprintf()'s or very well documented strncpy()'s. None of those strncpy()'s special 'expected' side effects were documented at all, which is bad. They need to be documented if they are going to remain in there. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 22:45:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16829 for freebsd-current-outgoing; Fri, 20 Nov 1998 22:45:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16824 for ; Fri, 20 Nov 1998 22:45:26 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id XAA21642; Fri, 20 Nov 1998 23:44:55 -0700 (MST) Message-Id: <199811210644.XAA21642@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon cc: "Justin T. Gibbs" , current@FreeBSD.ORG Subject: Re: snprintf() in the kernel In-reply-to: Your message of "Fri, 20 Nov 1998 22:38:16 PST." <199811210638.WAA21040@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Nov 1998 23:37:35 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >::> >::> Boy, weren't we lucky that all BT model names were 4 characters! >:: >::Of course they are always 4 characters long. How do you think the programme >r >::determined the correct amount of space to allocate for the name information >::in the first place? >:: >::-- >::Justin > > Well, yes, but the obvious problem is that at some future point someone > adds a 5-character model and, BEWM. Which can't happen for a product line no longer being developed. I'm not saying that the changes are bad, but most kernel developers do put some thought into their design and its implications. For this very reason, most of the changes offered are for code that already functions correctly. > In general, this is why we need either snprintf()'s or very well > documented strncpy()'s. None of those strncpy()'s special 'expected' > side effects were documented at all, which is bad. They need to be > documented if they are going to remain in there. man strncpy -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 20 22:56:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17450 for freebsd-current-outgoing; Fri, 20 Nov 1998 22:56:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17420 for ; Fri, 20 Nov 1998 22:55:59 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA26988; Sat, 21 Nov 1998 17:55:18 +1100 Date: Sat, 21 Nov 1998 17:55:18 +1100 From: Bruce Evans Message-Id: <199811210655.RAA26988@godzilla.zeta.org.au> To: archie@whistle.com, dillon@apollo.backplane.com, freebsd-current@FreeBSD.ORG, grog@lemis.com, rnordier@nordier.com Subject: Re: snprintf() in the kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Also review zero-termination cases for disklabels... make sure > disklabel isn't designed to allow a full-length string (without > zero-termination) else your snprintf()'s have broke something. disklabel is so designed. >alpha/alpha/db_disasm.c > > line 196, static char unk[8]; ... buffer is not big enough. Needs to be > at least 11. The snprintf() prevents a possible overflow (a bug fixed!), > but the buffer should probably be made larger anyway. Actually, it only needs to be 10 :-). It is only used to print a 26-bit unsigned bitfield value. >cam/scsi/scsi_all.c > > line 1566, char holdstr[8] was totally broken anyway, it wasn't big > enough (needs to be 10). Your patch removes it which is good. > A second bug fixed! No bug here. The value is a u_int8_t. >i386/isa/mcd.c > > (Looks like you fixed a bug here... the strncpy was assuming zero > termination) The bug was subtracting 1 from the size. >netatm/spans/spans_util.c: > > I'm not sure about these ntohl() calls. Some of the defines just > macro the arguments through, others are routines, but historically > ntohl() has operated on a 32 bit quantity so we should probably > cast to ntohl() results to (long) in the s*printf() calls as well > as do the sprintf()->snprintf() conversion. ntohl() must operate on a 32-bit quantitiy, but it should't return u_long unless u_long is 32 bits. ntohl() results should be cast to (u_long) (or (u_int32_t) if you can easiy use the format specifier for that). > >RCS file: /cvs/freebsd/src/sys/netatm/spans/spans_util.c,v >retrieving revision 1.3 >diff -u -r1.3 spans_util.c >--- spans_util.c 1998/10/31 20:06:56 1.3 >+++ spans_util.c 1998/11/21 03:03:09 >@@ -441,7 +441,7 @@ > /* > * Print and return the string > */ >- sprintf(strbuff, "%lx.%lx", ntohl(u1.w), ntohl(u2.w)); >+ snprintf(strbuff, sizeof(strbuff), "%lx.%lx", ntohl(u1.w), ntohl(u2.w)); > return(strbuff); > } The 80 character buffer is obviously big enough for sprintf if ntohl() returns a 32-bit quantity. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 00:11:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21753 for freebsd-current-outgoing; Sat, 21 Nov 1998 00:11:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA21748 for ; Sat, 21 Nov 1998 00:11:23 -0800 (PST) (envelope-from terbart@aye.net) Received: (qmail 29057 invoked by uid 3185); 21 Nov 1998 08:09:13 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 21 Nov 1998 08:09:13 -0000 Date: Sat, 21 Nov 1998 03:09:13 -0500 (EST) From: Barrett Richardson To: garman@earthling.net cc: current@FreeBSD.ORG Subject: Re: more dying daemons In-Reply-To: <199811210418.UAA06160@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 20 Nov 1998 garman@earthling.net wrote: > On 20 Nov, Barrett Richardson wrote: > > > > Swap usage at 64% after only hour seems awfully high. I've seem similar > > behaviour in the world of SCO. Folks just under the threshold of what > > they can get out of their box with given swap/memory size with 3.2v4.2 > > are having no problems. They upgrade to Open Server 5, put the same load > > on it, and the box starts a slow downward spiral and finally becomes > > unusable. They reboot it, and its ok for a couple of hours. > > > The 64% swap usage figure was from an uptime of two days, not an hour. > I have however easily produced swap usages around 56-58% (synthetically, > of course) within 10-20 minutes while testing some of the potential > fixes posted here. > > i've never had a problem with insufficient swap before... The resource requirements for -current may be a tad higher than for -stable. Like I mentioned earlier you may have been running just under the threshold with your previous configuration. > > > You can use vnconfig to test the beast without reslicing if you > > have ample disk space. > > > yes, but isn't this just a workaround? I rarely (if ever) run out of > memory and swap, and my usage usually stabilizes around 65% after a few > days. I still say 65% is high. I have never been able to get a box to run reliably for extended periods with swap usage above 50%. > > i would expect a system to behave reasonably even in the face of memory > shortages. corrupting running processes (when they fork?) is not a > reasonable behavior. There is a fairly recent thread about the low junk pointers in the archives. Might be some useful info there; ftp2.freebsd.org (or maybe ftp5, can't remember for sure) was afflicted with that problem for a day or so. > > > If problems persist, entertain the idea that something you > > are using has a mongo memory leak. > > > basically this is just my personal workstation box. whats > running include netscape, tkrat (with huge mailboxes :/), windowmaker, > and various other X apps. nothing particularly suspect (except perhaps > for netscape :)) > > enjoy > -- > Jason Garman http://garman.dyn.ml.org/ > Student, University of Maryland garman@earthling.net > And now... did you know that: Whois: JAG145 > "If you fart consistently for 6 years and 9 months, enough gas is > produced to create the energy of an atomic bomb." -- 0xdeadbeef posting > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 00:15:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA22067 for freebsd-current-outgoing; Sat, 21 Nov 1998 00:15:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dv.ru (home.dv.ru [195.98.33.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA22061 for ; Sat, 21 Nov 1998 00:15:15 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by home.dv.ru (8.9.1/8.9.1) with SMTP id LAA00655; Sat, 21 Nov 1998 11:14:10 +0300 (MSK) (envelope-from dv@dv.ru) X-Authentication-Warning: home.dv.ru: dv owned process doing -bs Date: Sat, 21 Nov 1998 11:14:10 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@localhost To: Brian Somers cc: current@FreeBSD.ORG Subject: more info about ppp's problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! There is additional info. PPP does correctly handle carrier lost, but it DOESN'T down link sometimes. (Not too often). There is output from show commands when it happens: PPP ON home> show modem Name: deflink State: open, no carrier Device: /dev/modem Link Type: auto Connect Count: 1 Physical outq: 0 Queued Packets: 0 Phone Number: 777777 Defaults: Device List: /dev/modem Characteristics: 57600bps, cs8, no parity, CTS/RTS on Connect time: 894 secs 169662 octets in, 91098 octets out overall 291 bytes/sec currently 0 bytes/sec peak 5928 bytes/sec on Sat Nov 21 10:53:02 1998 PPP ON home> show link Name: deflink State: open CHAP Encryption: MD5 Peer name: None requested Discriminator: Null Class Defaults: Phone List: 777777 Dial tries: 1, delay 3s/30s Reconnect tries: 50, delay 1s Callback requested: none Dial Script: ABORT BUSY ABORT NO\sCARRIER TIMEOUT 5 "" AT OK-AT-OK ATE0Q0S0=1 OK \dATDP\T TIMEOUT 40 CONNECT Login Script: TIMEOUT 120 ogin:--ogin: mylogin word: ****** string: 123456 CONNECT Hangup Script: PPP ON home> show bundle Phase Network Title: ppp Device: /dev/tun0 Interface: tun0 @ 57600bps Defaults: Label: pmdemand Auth name: Auto Load: Up after 0s of >= 0 packets Down after 0s of <= 0 packets not running with 0 packets queued Choked Timer: 120s Idle Timer: 300s (284s remaining) MTU: unspecified sendpipe: unspecified recvpipe: unspecified Sticky Routes: enabled ID check: enabled Loopback: enabled PasswdAuth: disabled Proxy: disabled Proxyall: disabled Throughput: enabled Utmp Logging: enabled Iface-Alias: disabled PPP ON home> PPP ON home> show iface tun0 (idx 2) has 1 address: 195.98.33.65/24 -> 195.98.32.83 PPP ON home> show timers IPCP throughput timer[0x8089994]: freq = 1.00s, next = 0.40s, state = running modem throughput timer[0x80a3040]: freq = 1.00s, next = 1.00s, state = running hdlc timer[0x80a5728]: freq = 60.00s, next = 32.40s, state = running idle timer[0x808afe0]: freq = 300.00s, next = 293.10s, state = running PPP ON home> show ipcp IPCP [Opened] His side: 195.98.32.83, 14 VJ slots without slot compression My side: 195.98.33.65, 16 VJ slots with slot compression Sticky routes: add default HISADDR Defaults: My Address: 10.0.0.1/0 (trigger with 0.0.0.0) VJ compression: enabled & accepted (16 slots with slot compression) His Address: 10.0.0.2/0 DNS: 0.0.0.0, 0.0.0.0, enabled & denied NetBIOS NS: 0.0.0.0, 0.0.0.0 Connect time: 959 secs 185774 octets in, 85372 octets out overall 282 bytes/sec currently 0 bytes/sec peak 5891 bytes/sec on Sat Nov 21 10:53:02 1998 There is a parts of my config file: default: delete! default set log Phase Chat LCP IPCP CCP tun command +debug set server +3000 ***** set device /dev/modem set speed 57600 set reconnect 1 50 set timeout 300 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATE0Q0S0=1 OK \\dATDP\\T TIMEOUT 40 CONNECT" pmdemand: delete! default set server +3000 ***** set phone 777777 set login "TIMEOUT 120 ogin:--ogin: mylogin word: ****** string: 123456 CONNECT" set log +debug set timeout 300 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns Dmitry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 01:29:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA26254 for freebsd-current-outgoing; Sat, 21 Nov 1998 01:29:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles343.castles.com [208.214.167.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA26249 for ; Sat, 21 Nov 1998 01:29:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id VAA00400; Fri, 20 Nov 1998 21:16:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811210516.VAA00400@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Robert Nordier cc: gallatin@cs.duke.edu (Andrew Gallatin), freebsd-current@FreeBSD.ORG, adrian@ubergeeks.com Subject: Re: /boot/loader & comconsole In-reply-to: Your message of "Sat, 19 Nov 1998 11:02:00 +0200." <199811190902.LAA03790@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Nov 1998 21:16:47 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks for the feedback, and let us know how you go. If necessary, I > can do some patches to get boot loader using the boot blocks serial > routines, which may be a good idea anyway. I've discussed this off and on with a couple of people, and I agree that the various boot stages should use the same methods to talk to the serial port. Given that the low-level model is easier to use (not to mention probably more compact) I'm all in favour of it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 04:43:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09897 for freebsd-current-outgoing; Sat, 21 Nov 1998 04:43:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailer.tydfam.machida.tokyo.jp (ns.tydfam.machida.tokyo.jp [210.161.209.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09889 for ; Sat, 21 Nov 1998 04:43:11 -0800 (PST) (envelope-from ken@tydfam.machida.tokyo.jp) Received: from localhost (ns1.tydfam.machida.tokyo.jp [210.161.209.138]) by mailer.tydfam.machida.tokyo.jp (8.9.1/3.7W10/03/98) with ESMTP id VAA24686 for ; Sat, 21 Nov 1998 21:43:07 +0900 (JST) To: current@FreeBSD.ORG Subject: kbdcontrol w/ 3.0-current X-Mailer: Mew version 1.92.4 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981121214306B.ken@ns1.tydfam.machida.tokyo.jp> Date: Sat, 21 Nov 1998 21:43:06 +0900 From: Takeshi Yamada X-Dispatcher: imput version 980905(IM100) Lines: 11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My Nov. 20th cvsup'd "make world" caused $: {12} kbdcontrol -d kbdcontrol: getting keymap: Inappropriate ioctl for device ===== Could anyone fix this? I cannot change my keymap to Japanese one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 07:00:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16998 for freebsd-current-outgoing; Sat, 21 Nov 1998 07:00:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16809 for ; Sat, 21 Nov 1998 07:00:32 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (woof.lan.Awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id PAA22230; Sat, 21 Nov 1998 15:00:00 GMT (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id NAA01689; Sat, 21 Nov 1998 13:53:22 GMT (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199811211353.NAA01689@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Dmitry Valdov cc: Brian Somers , current@FreeBSD.ORG Subject: Re: more info about ppp's problem In-reply-to: Your message of "Sat, 21 Nov 1998 11:14:10 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Nov 1998 13:53:22 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi! > > There is additional info. PPP does correctly handle carrier lost, but it > DOESN'T down link sometimes. (Not too often). There is output from show > commands when it happens: > > PPP ON home> show modem > Name: deflink > State: open, no carrier > Device: /dev/modem [.....] > PPP ON home> show timers > IPCP throughput timer[0x8089994]: freq = 1.00s, next = 0.40s, state = > running > modem throughput timer[0x80a3040]: freq = 1.00s, next = 1.00s, state = > running > hdlc timer[0x80a5728]: freq = 60.00s, next = 32.40s, state = running > idle timer[0x808afe0]: freq = 300.00s, next = 293.10s, state = running [.....] As you can see, there's no ``modem CD'' timer running. The only way this can happen is if carrier wasn't present when your login script completed. You should see a message in your log file saying deflink: /dev/modem doesn't support CD The only thing I can think may be happening is that your modem is not reporting CD correctly, or is reporting it correctly, but line noise is causing it to ``fluctuate''. There's a setting on most modems (S10 maybe?) that determines how long carrier must be lost before reporting it - you could try increasing this to something like 2 seconds. If you've been seeing frequent line drops, this may help that too (if CD is there after the login script, ppp may drop the link because of line noise because it sees the carrier loss). > Dmitry. -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 07:44:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20347 for freebsd-current-outgoing; Sat, 21 Nov 1998 07:44:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20326 for ; Sat, 21 Nov 1998 07:44:18 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id QAA16177; Sat, 21 Nov 1998 16:43:46 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id QAA23684; Sat, 21 Nov 1998 16:43:45 +0100 (MET) Message-ID: <19981121164344.E17306@follo.net> Date: Sat, 21 Nov 1998 16:43:44 +0100 From: Eivind Eklund To: Barrett Richardson , garman@earthling.net Cc: current@FreeBSD.ORG Subject: Re: more dying daemons References: <199811210418.UAA06160@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Barrett Richardson on Sat, Nov 21, 1998 at 03:09:13AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 21, 1998 at 03:09:13AM -0500, Barrett Richardson wrote: > > > On Fri, 20 Nov 1998 garman@earthling.net wrote: > > > On 20 Nov, Barrett Richardson wrote: > > > > > > Swap usage at 64% after only hour seems awfully high. I've seem similar > > > behaviour in the world of SCO. Folks just under the threshold of what > > > they can get out of their box with given swap/memory size with 3.2v4.2 > > > are having no problems. They upgrade to Open Server 5, put the same load > > > on it, and the box starts a slow downward spiral and finally becomes > > > unusable. They reboot it, and its ok for a couple of hours. > > > > > The 64% swap usage figure was from an uptime of two days, not an hour. > > I have however easily produced swap usages around 56-58% (synthetically, > > of course) within 10-20 minutes while testing some of the potential > > fixes posted here. > > > > i've never had a problem with insufficient swap before... > > The resource requirements for -current may be a tad higher than > for -stable. Like I mentioned earlier you may have been running > just under the threshold with your previous configuration. The bug in question is "new" (23rd february, most likely), and is not visible in -stable. It is a serious bug. Saying that his swap usage is 'too high' is not going to help us solve it; the system is supposed to be stable no matter what. We can't take 3.0 to be -STABLE until this bug and the clock bug is solved. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 08:01:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21266 for freebsd-current-outgoing; Sat, 21 Nov 1998 08:01:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21261 for ; Sat, 21 Nov 1998 08:01:20 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id QAA07974; Sat, 21 Nov 1998 16:55:20 +0100 (CET) To: Eivind Eklund cc: Barrett Richardson , garman@earthling.net, current@FreeBSD.ORG Subject: Re: more dying daemons In-reply-to: Your message of "Sat, 21 Nov 1998 16:43:44 +0100." <19981121164344.E17306@follo.net> Date: Sat, 21 Nov 1998 16:55:20 +0100 Message-ID: <7972.911663720@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >We can't take 3.0 to be -STABLE until >this bug and the clock bug is solved. If by "the clock bug" you mean the "calcru negative..." it has been nailed. Many thanks to msmith, wosch & wpaul for help in tracking it down. It is as predicted caused by hardclock() interrupts being disabled for far too long. This seems to happen on some specific types of hardware, the PLIP code for the parallel port being the most readily available. I'm currently running my torture tests on some patches which reduces the rate at which we rotate the timecounter structures, this helps a lot, and a kernel option will provide tweak-room for specific bad hardware. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 08:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26824 for freebsd-current-outgoing; Sat, 21 Nov 1998 08:55:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26819 for ; Sat, 21 Nov 1998 08:55:49 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA21545; Sun, 22 Nov 1998 03:54:46 +1100 Date: Sun, 22 Nov 1998 03:54:46 +1100 From: Bruce Evans Message-Id: <199811211654.DAA21545@godzilla.zeta.org.au> To: eivind@yes.no, phk@critter.freebsd.dk Subject: Re: more dying daemons Cc: current@FreeBSD.ORG, garman@earthling.net, terbart@aye.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >If by "the clock bug" you mean the "calcru negative..." it has been >nailed. Many thanks to msmith, wosch & wpaul for help in tracking >it down. > >It is as predicted caused by hardclock() interrupts being disabled >for far too long. This seems to happen on some specific types of >hardware, the PLIP code for the parallel port being the most readily >available. Erm, it is caused by _non_-hardclock() interrupts being disabled for for too long. This is normal for non-slow hardware connected through a slow interface (some IDE confirguations, ISA ethernet) and for buggy software like PLIP. The bug is inhibited by hardclock interrupts being disabled for far too long, since the timecounters normally don't rotate unless hardclock() is called. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 09:19:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29036 for freebsd-current-outgoing; Sat, 21 Nov 1998 09:19:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29031 for ; Sat, 21 Nov 1998 09:19:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA08298; Sat, 21 Nov 1998 18:16:23 +0100 (CET) To: Bruce Evans cc: eivind@yes.no, current@FreeBSD.ORG, garman@earthling.net, terbart@aye.net Subject: Re: more dying daemons In-reply-to: Your message of "Sun, 22 Nov 1998 03:54:46 +1100." <199811211654.DAA21545@godzilla.zeta.org.au> Date: Sat, 21 Nov 1998 18:16:21 +0100 Message-ID: <8296.911668581@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199811211654.DAA21545@godzilla.zeta.org.au>, Bruce Evans writes: >>If by "the clock bug" you mean the "calcru negative..." it has been >>nailed. Many thanks to msmith, wosch & wpaul for help in tracking >>it down. >> >>It is as predicted caused by hardclock() interrupts being disabled >>for far too long. This seems to happen on some specific types of >>hardware, the PLIP code for the parallel port being the most readily >>available. > >Erm, it is caused by _non_-hardclock() interrupts being disabled for >for too long. No, it is caused by hardclock being called with much smaller than 1/hz in between. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 09:28:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00355 for freebsd-current-outgoing; Sat, 21 Nov 1998 09:28:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rain.futuresouth.com (rain.futuresouth.com [198.79.79.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00345 for ; Sat, 21 Nov 1998 09:28:20 -0800 (PST) (envelope-from stormy@rain.futuresouth.com) Received: (from stormy@localhost) by rain.futuresouth.com (8.9.1/8.9.1) id LAA20511 for current@FreeBSD.ORG; Sat, 21 Nov 1998 11:29:40 -0600 (CST) (envelope-from stormy) Message-ID: <19981121112940.A17369@futuresouth.com> Date: Sat, 21 Nov 1998 11:29:40 -0600 From: Stormy Henderson To: current@FreeBSD.ORG Subject: Re: kbdcontrol w/ 3.0-current Mail-Followup-To: current@FreeBSD.ORG References: <19981121214306B.ken@ns1.tydfam.machida.tokyo.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981121214306B.ken@ns1.tydfam.machida.tokyo.jp>; from Takeshi Yamada on Sat, Nov 21, 1998 at 09:43:06PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A happy camper (Takeshi Yamada, ken@tydfam.machida.tokyo.jp) once wrote... > My Nov. 20th cvsup'd "make world" caused > $: {12} kbdcontrol -d > kbdcontrol: getting keymap: Inappropriate ioctl for device This happens with my Nov 18th SNAP too. Be happy... -- http://www.futuresouth.com/~stormy/signature.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 09:35:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA00991 for freebsd-current-outgoing; Sat, 21 Nov 1998 09:35:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (43-sweet.camalott.com [208.239.153.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA00687 for ; Sat, 21 Nov 1998 09:33:32 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id LAA27207; Sat, 21 Nov 1998 11:29:40 -0600 (CST) (envelope-from joelh) To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: Install new /etc/pam.conf file from /usr/src/etc References: From: Joel Ray Holveck Date: 21 Nov 1998 11:29:27 -0600 In-Reply-To: John Polstra's message of "Fri, 20 Nov 1998 15:33:05 -0800 (PST)" Message-ID: <86ogq1ymx4.fsf@detlev.UUCP> Lines: 20 X-Mailer: Gnus v5.5/Emacs 20.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For those folks who haven't heard about it, PAM stands for Pluggable > Authentication Modules. It is a flexible way to configure the kinds > of authentication (passwd/NIS, S/Key, Kerberos, RADIUS, TACACS+) used > in your system. Each authentication method is encapsulated in an [snip] This is something I've been wanting for a long while. Do you have a URL where I can get an API and other such info? I've got some ideas that I want to add in. Are we going to move S/Key, Kerberos, etc. out of login, ftpd, etc? Happy hacking, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 10:41:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07946 for freebsd-current-outgoing; Sat, 21 Nov 1998 10:41:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07939 for ; Sat, 21 Nov 1998 10:41:30 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA24741; Sat, 21 Nov 1998 10:40:48 -0800 (PST) (envelope-from dillon) Date: Sat, 21 Nov 1998 10:40:48 -0800 (PST) From: Matthew Dillon Message-Id: <199811211840.KAA24741@apollo.backplane.com> To: Eivind Eklund Cc: Barrett Richardson , garman@earthling.net, current@FreeBSD.ORG Subject: Re: more dying daemons References: <199811210418.UAA06160@hub.freebsd.org> <19981121164344.E17306@follo.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The bug in question is "new" (23rd february, most likely), and is not :visible in -stable. It is a serious bug. Saying that his swap usage :is 'too high' is not going to help us solve it; the system is supposed :to be stable no matter what. We can't take 3.0 to be -STABLE until :this bug and the clock bug is solved. : :Eivind. : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message We need to find a way to reproduce the problem. I'm running serveral -current systems, one very heavily (nntp1.ba.best.com), and swap utilization is normal. Is the original person who reported the problem using MFS mounts by any chance? -- I'm happy the clock cpu-resource problem has been fixed, that was starting to get annoying. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 10:41:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08180 for freebsd-current-outgoing; Sat, 21 Nov 1998 10:41:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08174 for ; Sat, 21 Nov 1998 10:41:47 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id KAA10167; Sat, 21 Nov 1998 10:41:11 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA26331; Sat, 21 Nov 1998 10:40:58 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <86ogq1ymx4.fsf@detlev.UUCP> Date: Sat, 21 Nov 1998 10:40:58 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Joel Ray Holveck Subject: Re: HEADS UP: Install new /etc/pam.conf file from /usr/src/etc Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Nov-98 Joel Ray Holveck wrote: >> For those folks who haven't heard about it, PAM stands for Pluggable >> Authentication Modules. It is a flexible way to configure the kinds >> of authentication (passwd/NIS, S/Key, Kerberos, RADIUS, TACACS+) used >> in your system. Each authentication method is encapsulated in an > [snip] > > This is something I've been wanting for a long while. Do you have a > URL where I can get an API and other such info? There are some documents in "src/contrib/libpam/doc". See also . > Are we going to move S/Key, Kerberos, etc. out of login, ftpd, etc? Already done for login. The others will come as I find time to convert them. --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 11:01:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10036 for freebsd-current-outgoing; Sat, 21 Nov 1998 11:01:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phantasm.thekeep.org (PHANTASM.CC.CMU.EDU [128.2.35.108]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA10030 for ; Sat, 21 Nov 1998 11:01:36 -0800 (PST) (envelope-from dar@thekeep.org) Received: (qmail 30676 invoked by uid 100); 21 Nov 1998 19:01:04 -0000 Message-ID: <19981121140103.A84228@thekeep.org> Date: Sat, 21 Nov 1998 14:01:03 -0500 From: Dan Root To: freebsd-current@FreeBSD.ORG Subject: Memory usage question Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a machine that I recently upgraded from a -current built around the end of August to the most recent -current. For the most part everything seems fairly happy: CAM, softupdates, etc. However I've been having the 'dying daemons' problem. For the most part I've been working around it, but I just dropped another 128 Megs of RAM (for a total of 256M) into the machine to help prevent the problem from occuring. Needless to say, 2 hours after doing make world, installing a new kernel and rebooted (under moderately heavy load), I've just touched swap. With 155M of memory marked as 'inactive' according to top. It strikes me as a little odd, but why on earth would things be swapping out if there's 155M of inactive memory? And 8 megs of cache and 8 more megs of buffers (again, all according to top). This strikes me as overly agressive swapping. Along the same lines, why is this memory sitting in the inactive pool rather than being used for caching or buffering? (Or am I misunderstanding the meaning of these headings?) Is there some CONFIG, rc.conf, or sysctl options I have inadvertantly forgetten to set or tweak? output from top: last pid: 13182; load averages: 1.00, 1.13, 1.14 13:45:16 84 processes: 4 running, 79 sleeping, 1 zombie CPU states: 16.3% user, 0.0% nice, 33.7% system, 1.5% interrupt, 48.6% idle Mem: 56M Active, 155M Inact, 32M Wired, 8380k Cache, 8344k Buf, 784K Free Swap: 64M Total, 320K Used, 64M Free output from vmstat -s: 1471838 cpu context switches 2492270 device interrupts 831953 software interrupts 5341605 traps 11534741 system calls 0 swap pager pageins 0 swap pager pages paged in 5 swap pager pageouts 5 swap pager pages paged out 1840 vnode pager pageins 8805 vnode pager pages paged in 1 vnode pager pageouts 1 vnode pager pages paged out 58 page daemon wakeups 93774 pages examined by the page daemon 977 pages reactivated 1731236 copy-on-write faults 274744 copy-on-write optimized faults 2559046 zero fill pages zeroed 207564 zero fill pages prezeroed 8 intransit blocking page faults 5219033 total VM faults taken 5231071 pages freed 53 pages freed by daemon 124964 pages freed by exiting processes 12642 pages active 40336 pages inactive 2004 pages in VM cache 8032 pages wired down 965 pages free 4096 bytes per page 2748624 total name lookups cache hits (80% pos + 12% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% And of course, the following was syslogged: swap_pager: suggest more swap space: 511 MB If anyone would like more information, I'd be happy to provide the output of sysctl -a, my CONFIG file, hardware listings, or anything else that might explain what's going on here. -DaR -- Dan Root - dar@thekeep.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 11:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10749 for freebsd-current-outgoing; Sat, 21 Nov 1998 11:07:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10741 for ; Sat, 21 Nov 1998 11:07:04 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id UAA17722; Sat, 21 Nov 1998 20:06:31 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id UAA24383; Sat, 21 Nov 1998 20:06:31 +0100 (MET) Message-ID: <19981121200631.G23705@follo.net> Date: Sat, 21 Nov 1998 20:06:31 +0100 From: Eivind Eklund To: Matthew Dillon Cc: Barrett Richardson , garman@earthling.net, current@FreeBSD.ORG Subject: Re: more dying daemons References: <199811210418.UAA06160@hub.freebsd.org> <19981121164344.E17306@follo.net> <199811211840.KAA24741@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199811211840.KAA24741@apollo.backplane.com>; from Matthew Dillon on Sat, Nov 21, 1998 at 10:40:48AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 21, 1998 at 10:40:48AM -0800, Matthew Dillon wrote: > >> The bug in question is "new" (23rd february, most likely), and is not >> visible in -stable. It is a serious bug. Saying that his swap usage >> is 'too high' is not going to help us solve it; the system is supposed >> to be stable no matter what. We can't take 3.0 to be -STABLE until >> this bug and the clock bug is solved. >> >> Eivind. > > We need to find a way to reproduce the problem. I'm running serveral > -current systems, one very heavily (nntp1.ba.best.com), and swap > utilization is normal. > > Is the original person who reported the problem using MFS mounts by any > chance? I have the problem. I don't use MFS mounts. It is also extremely difficult to reproduce here (comes when my workstation has been up for weeks, usually). The only common factor I know of so far (and I'm not sure it is common) is that we all run FreeBSD :-); also, all I have asked run X and Netscape. No hardware common in common. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 11:19:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11731 for freebsd-current-outgoing; Sat, 21 Nov 1998 11:19:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from float.dyn.ml.org (cs802463-a.gvcl1.bc.wave.home.com [24.64.194.119]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11726 for ; Sat, 21 Nov 1998 11:19:30 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Received: from float.dyn.ml.org (localhost [127.0.0.1]) by float.dyn.ml.org (8.9.1/8.9.1) with ESMTP id LAA00884 for ; Sat, 21 Nov 1998 11:18:57 -0800 (PST) (envelope-from jake@float.dyn.ml.org) Message-Id: <199811211918.LAA00884@float.dyn.ml.org> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: kernel make failure in smbus In-reply-to: Your message of "Wed, 18 Nov 1998 18:53:20 EST." <36535DF0.B9E7EA1B@spawnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Nov 1998 11:18:57 -0800 From: Jake Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ../../dev/smbus/smbus.c:85: `bus_generic_connect_intr' undeclared here (not in a function) > > ../../dev/smbus/smbus.c:85: initializer element for `smbus_methods[8].func' is not constant > > *** Error code 1 > > > > Stop. > > Confirmed still broken on Wednesday, wondering if anyone has looked into > it yet :/ And as of this morning, Saturday. Any progress? Is there a work around that still allows the bktr driver to function? I'd like to be able to build kernels, and watch TV. I haven't rebuilt my kernel since the proc changes, so ps et al are broken for me also. I'm holding off building the pam stuff as that will probably wreak more havoc on my out of date kernel. oh well, I guess that's -current for you. Thanks, I hope somebody is looking into it, and I wish I had the time and knowledge to do so. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 12:09:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15686 for freebsd-current-outgoing; Sat, 21 Nov 1998 12:09:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15674 for ; Sat, 21 Nov 1998 12:09:34 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id MAA00422; Sat, 21 Nov 1998 12:08:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811212008.MAA00422@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jake cc: current@FreeBSD.ORG Subject: Re: kernel make failure in smbus In-reply-to: Your message of "Sat, 21 Nov 1998 11:18:57 PST." <199811211918.LAA00884@float.dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Nov 1998 12:08:48 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried rebuilding the kernel and got the same result so I am currently doing a make world from a fresh cvsup. We can also hack the bktr driver to make smb support an option. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 12:27:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17456 for freebsd-current-outgoing; Sat, 21 Nov 1998 12:27:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sivka.carrier.kiev.ua (sivka.carrier.kiev.ua [193.193.193.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17446 for ; Sat, 21 Nov 1998 12:27:07 -0800 (PST) (envelope-from archer@grape.carrier.kiev.ua) Received: Received: from kozlik.carrier.kiev.ua (kozlik.carrier.kiev.ua [193.193.193.111]) by sivka.carrier.kiev.ua (8.9.1a/8.9.1) with ESMTP id WAA19307; Sat, 21 Nov 1998 22:26:25 +0200 (EET) (envelope-from archer@grape.carrier.kiev.ua) Received: (from uucp@localhost) by kozlik.carrier.kiev.ua (8.9.0/8.9.0/8.Who.Cares) with UUCP id WAA00861; Sat, 21 Nov 1998 22:23:38 +0200 (EET) (envelope-from archer@grape.carrier.kiev.ua) Received: (from archer@localhost) by grape.carrier.kiev.ua (8.9.1/8.9.1) id WAA23191; Sat, 21 Nov 1998 22:07:03 +0200 (EET) (envelope-from archer) Date: Sat, 21 Nov 1998 22:07:03 +0200 (EET) From: Alexander Litvin Message-Id: <199811212007.WAA23191@grape.carrier.kiev.ua> To: Damon Hopkins Cc: current@FreeBSD.ORG Subject: Re: Random rebooting X-Newsgroups: grape.freebsd.current In-Reply-To: <199811180210.TAA21262@usr01.primenet.com> <3652DC31.9A1754FE@rtci.com> Organization: Lucky Grape User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <3652DC31.9A1754FE@rtci.com> you wrote: DH> This sounds like what is happening to me. This machine is a AMD 486-133 DH> w/ 24 MB RAM no funky drivers or anything.. it has NEVER rebooted like DH> this before.. I don't know about the heavy network load I did some huge DH> file transfers yesterday on our lan and had no ill effects. Well, well, DH> well, what to do. Don't know if this is related, but my box frose several times. It happened when I tried to stress it with 'make buildworld' with sufficiently large '-j#'. Well, it didn't freese in fact, just stopped like if it had been blocked in some interrupt handler. Consoles switched OK, Ctl+T showed status of running processes OK, Ctl+D in shell caused exit (without any further activity), Ctl+Alt+Esc dropped to DDB ok, etc. Manual panic in DDB caused page fault. As a random guess I disabled loading of screen saver module from /boot/boot.conf, and it seemes to cure the problem. If anybody interested, I can send a dump from DDB panic. DH> -- DH> [-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=-] DH> [ Damon Hopkins mailto: dhopkins@rtci.com ] DH> [ Software Developer http://totally.schizo.com ] DH> [ Research Triangle Consultants, Inc. http://www.rtci.com ] DH> [ -- In search of the elusive 50 sided triangle. -- ] DH> [-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=-] --- If today is the first day of the rest of your life, what the hell was yesterday? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 17:46:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14373 for freebsd-current-outgoing; Sat, 21 Nov 1998 17:46:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14366 for ; Sat, 21 Nov 1998 17:46:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id RAA03548; Sat, 21 Nov 1998 17:45:29 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199811220145.RAA03548@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jake cc: current@FreeBSD.ORG Subject: Re: kernel make failure in smbus In-reply-to: Your message of "Sat, 21 Nov 1998 11:18:57 PST." <199811211918.LAA00884@float.dyn.ml.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Nov 1998 17:45:28 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Post on the multimedia mailing list and request a patch to disable smb support in bktr it should not be difficult to generate since the code to talk to the I2C interface is still in the driver. I isolated the problem to : /sys/sys/bus.h and the recently commit : 1.7 Sat Nov 14 21:58:41 1998 UTC by wollman CVS Tags: HEAD Diffs to 1.6 My changes to the new device interface: - Interface wth the new resource manager. - Allow for multiple drivers implementing a single devclass. - Remove ordering dependencies between header files. - Style cleanup. - Add DEVICE_SUSPEND and DEVICE_RESUME methods. - Move to a single-phase interrupt setup scheme. Kernel builds on the Alpha are brken until Doug gets a chance to incorporate these changes on that side. ----------------- Amancio > > > ../../dev/smbus/smbus.c:85: `bus_generic_connect_intr' undeclared here (not in a function) > > > ../../dev/smbus/smbus.c:85: initializer element for `smbus_methods[8].func' is not constant > > > *** Error code 1 > > > > > > Stop. > > > > Confirmed still broken on Wednesday, wondering if anyone has looked into > > it yet :/ > > And as of this morning, Saturday. > > Any progress? Is there a work around that still allows the bktr driver > to function? > > I'd like to be able to build kernels, and watch TV. > > I haven't rebuilt my kernel since the proc changes, so ps et al > are broken for me also. I'm holding off building the pam stuff as > that will probably wreak more havoc on my out of date kernel. > oh well, I guess that's -current for you. > > Thanks, I hope somebody is looking into it, and I wish > I had the time and knowledge to do so. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 17:51:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14619 for freebsd-current-outgoing; Sat, 21 Nov 1998 17:51:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bachue.usc.unal.edu.co (bachue.usc.unal.edu.co [168.176.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14606 for ; Sat, 21 Nov 1998 17:51:25 -0800 (PST) (envelope-from pfgiffun@bachue.usc.unal.edu.co) Received: from bachue.usc.unal.edu.co ([168.176.3.31]) by bachue.usc.unal.edu.co (Netscape Messaging Server 3.0) with ESMTP id AAA7675 for ; Sat, 21 Nov 1998 20:53:31 +0500 Message-ID: <36576E54.33B41A1B@bachue.usc.unal.edu.co> Date: Sat, 21 Nov 1998 20:52:20 -0500 From: "Pedro F. Giffuni" Organization: U. Nacional de Colombia X-Mailer: Mozilla 4.05 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: More on AWK Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know if there was a final decision in the gawk-->nawk replacement, but I found some more information about Lucent's AWK on this URL: http://www.lucent.com/ssg/html/awk.html Pedro. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 18:55:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20570 for freebsd-current-outgoing; Sat, 21 Nov 1998 18:55:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailer.tydfam.machida.tokyo.jp (ns.tydfam.machida.tokyo.jp [210.161.209.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20556 for ; Sat, 21 Nov 1998 18:55:37 -0800 (PST) (envelope-from ken@tydfam.machida.tokyo.jp) Received: from localhost (ns1.tydfam.machida.tokyo.jp [210.161.209.138]) by mailer.tydfam.machida.tokyo.jp (8.9.1/3.7W10/03/98) with ESMTP id LAA26497; Sun, 22 Nov 1998 11:55:30 +0900 (JST) To: current@FreeBSD.ORG Cc: stormy@futuresouth.com Subject: Re: kbdcontrol w/ 3.0-current In-Reply-To: Your message of "Sat, 21 Nov 1998 11:29:40 -0600" <19981121112940.A17369@futuresouth.com> References: <19981121112940.A17369@futuresouth.com> X-Mailer: Mew version 1.92.4 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981122115529M.ken@ns1.tydfam.machida.tokyo.jp> Date: Sun, 22 Nov 1998 11:55:29 +0900 From: Takeshi Yamada X-Dispatcher: imput version 980905(IM100) Lines: 12 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To make clearer the problem, $: {2} kbdcontrol < /dev/ttyv0 -l /usr/share/syscons/keymaps/us.iso.kbd kbdcontrol: setting keymap: Inappropriate ioctl for device $: {3} kbdcontrol < /dev/ttyv0 -l /usr/share/syscons/keymaps/jp.106x.kbd kbdcontrol: setting keymap: Inappropriate ioctl for device $: {4} kbdcontrol < /dev/ttyv0 -r fast $: {5} -d, -r works, but -l .... didn't as shown above. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 19:31:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23225 for freebsd-current-outgoing; Sat, 21 Nov 1998 19:31:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from drama.navinet.net (drama.navinet.net [206.25.93.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23217 for ; Sat, 21 Nov 1998 19:31:56 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from root@localhost) by drama.navinet.net (8.9.1a/8.9.1) id WAA17164 for freebsd-current@freebsd.org; Sat, 21 Nov 1998 22:31:24 -0500 (EST) Message-ID: <19981121223124.A17127@navinet.net> Date: Sat, 21 Nov 1998 22:31:24 -0500 From: Baby Jane Hudson To: freebsd-current@FreeBSD.ORG Subject: IPFilter 3.2.10 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI, Darren Reed has released 3.2.10. Will these changes be merged into the primary 3.0 tree? (if they haven't already). Also, is there a FAQ about using IPFilter on FreeBSD (as opposed to IPFW). From: Darren Reed Message-Id: <199811220318.OAA10214@avalon.reed.wattle.id.au> Subject: IP Filter 3.2.10 To: ipfilter@coombs.anu.edu.au Date: Sun, 22 Nov 1998 14:18:05 +1100 (EST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-ipfilter@coombs.anu.edu.au X-UIDL: 850ed2fcc0c8476ed77dae4471b55055 Greetings, Finally, after some very worthwhile testing of IP Filter by a number of people, it's time to stamp out another release. No changes to the code have been made since 3.2.10beta9, but a cleanup of the examples (rules/*) shipped with the package has been done so that they all, at least, will be accepted as valid input. I'm quite confident that this is easily the most stable release for Solaris 2.*, if not for the other platforms as well. >From some of the panic's I've seen, I've reason to believe that the changes to use read-write locks where possible will be a performance win - especially for those with multi-cpu boxes. *touch wood* I will be introducing some new features to the NAT code for the next release (3.2.11) but would like to address the documentation issue as well. I'm sure everyone (except me ;) knows something that they would like to see explained further, so please let me know where I can expand and improve on the documentation. Relevant files and information can be found at: ftp://coombs.anu.edu.au/pub/net/ip-filter/ip_fil3.2.10.tar.gz ftp://coombs.anu.edu.au/pub/net/ip-filter/patch-3.2.10.gz http://coombs.anu.edu.au/ipfilter Darren p.s. all those who keep talking about patches they have to send me, please take the time to run up the diffs and send them :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 20:28:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26823 for freebsd-current-outgoing; Sat, 21 Nov 1998 20:28:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26818 for ; Sat, 21 Nov 1998 20:28:05 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id PAA22732; Sun, 22 Nov 1998 15:27:18 +1100 Date: Sun, 22 Nov 1998 15:27:18 +1100 From: Bruce Evans Message-Id: <199811220427.PAA22732@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.freebsd.dk Subject: Re: more dying daemons Cc: current@FreeBSD.ORG, eivind@yes.no, garman@earthling.net, terbart@aye.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>It is as predicted caused by hardclock() interrupts being disabled >>>for far too long. This seems to happen on some specific types of >>>hardware, the PLIP code for the parallel port being the most readily >>>available. >> >>Erm, it is caused by _non_-hardclock() interrupts being disabled for >>for too long. > >No, it is caused by hardclock being called with much smaller than >1/hz in between. Not normally. The normal failure mode is: [running at spl0()] tc = timecounter; use part of tc [hardware, non-hardclock interrupt] run in interrupt mode [hardclock interrupt] change timecounter on return, check if we can handle pending interrupts; perhaps we can, but we can't run softclock [perhaps another type of hardware interrupt] run some more in interrupt mode [hardclock interrupt] change timecounter, corrupting tc if NTIMECOUNTER = 2 ... finally finish hardware interrupt processing handle pending interrupts, including softclock [possibly more hardware interrupts] [possibly more hardclock interrupts] finally finish interrupt processing use another, now inconsistent part of tc This can easily happen without anything being broken. It just takes a transient high interrupt load. Hardclock can only be called soon after the previous call if something is broken. E.g., masking hardclock using splhigh() for (N - epsilon)/hz seconds can cause 2 (not N) hardclock calls separated by about epsilon/hz seconds. Since the number of calls is limited to 2, this bug can be stopped from corrupting the timecounter by using NTIMECOUNTER = 3. However, this form of the bug is unstable -- it is a small step from running the buggy interrupt handler and hardclock for 1/hz seconds to running in interrupt mode for 2/hz seconds. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 21:55:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03828 for freebsd-current-outgoing; Sat, 21 Nov 1998 21:55:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcpsj.pfcs.com (harlan.fred.net [205.252.219.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03810 for ; Sat, 21 Nov 1998 21:55:37 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sun, 22 Nov 1998 00:54:59 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sat, 21 Nov 1998 21:50:13 -0800 (PST) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sun, 22 Nov 1998 00:50:12 -0500 (EST) X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: objcopy in /usr/libexec/aout/objcopy? X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Nov 1998 00:50:12 -0500 Message-ID: <1710.911713812@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just upgraded a month or two old -current to a -current (as of yesterday). I got /etc/updated and rebuilt the kernel, too. I thought it would be a good idea to also upgrade /stand/sysinstall, and in doing so the make died because /boot was empty. I went in to /usr/src/sys/ boot/i386 and tried a make there, which died as follows: objcopy -S -O binary boot1.out boot1 objcopy: could not exec aout/objcopy in /usr/libexec: No such file or directory Sure enough, while there are a number of files in /usr/libexec/aout/, objcopy is not one of them. What did I miss? H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 22:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08267 for freebsd-current-outgoing; Sat, 21 Nov 1998 22:40:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08262 for ; Sat, 21 Nov 1998 22:40:25 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id RAA00219; Sun, 22 Nov 1998 17:44:01 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811220644.RAA00219@cimlogic.com.au> Subject: Re: objcopy in /usr/libexec/aout/objcopy? In-Reply-To: <1710.911713812@brown.pfcs.com> from Harlan Stenn at "Nov 22, 98 00:50:12 am" To: Harlan.Stenn@pfcs.com (Harlan Stenn) Date: Sun, 22 Nov 1998 17:44:01 +1100 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Harlan Stenn wrote: > I just upgraded a month or two old -current to a -current (as of yesterday). > > I got /etc/updated and rebuilt the kernel, too. > > I thought it would be a good idea to also upgrade /stand/sysinstall, and in > doing so the make died because /boot was empty. I went in to /usr/src/sys/ > boot/i386 and tried a make there, which died as follows: > > objcopy -S -O binary boot1.out boot1 > objcopy: could not exec aout/objcopy in /usr/libexec: No such file or directory > > Sure enough, while there are a number of files in /usr/libexec/aout/, > objcopy is not one of them. > > What did I miss? The correct build procedure: either `make world' or `make buildworld' followed by `make installworld'. Please don't try to be "clever". -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 22:43:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08681 for freebsd-current-outgoing; Sat, 21 Nov 1998 22:43:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cassiopeia.hkstar.com (cassiopeia.hkstar.com [202.82.3.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08569 for ; Sat, 21 Nov 1998 22:43:05 -0800 (PST) (envelope-from c5666305@b1.hkstar.com) Received: from b1.hkstar.com (b1.hkstar.com [202.82.0.87]) by cassiopeia.hkstar.com (8.9.1/8.9.1) with ESMTP id OAA01710 for ; Sun, 22 Nov 1998 14:42:28 +0800 (HKT) Received: (from c5666305@localhost) by b1.hkstar.com (8.8.8/8.8.8) id OAA14251 for freebsd-current@freebsd.org; Sun, 22 Nov 1998 14:44:55 +0800 (HKT) From: Chan Yiu Wah Message-Id: <199811220644.OAA14251@b1.hkstar.com> Subject: how to solve open tagging...64 To: freebsd-current@FreeBSD.ORG Date: Sun, 22 Nov 1998 14:44:55 +0800 (HKT) X-Mailer: ELM [version 2.5 PL0b1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I recenlty upgrade my system upto src-cur.3627.gz and found that the system report open tagging ... 64. Is it harmful to the system and how to solve it. I do think it had been talking about but I missed it (sorry). cheers Clarence To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 21 23:17:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA10894 for freebsd-current-outgoing; Sat, 21 Nov 1998 23:17:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles211.castles.com [208.214.165.211]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA10889 for ; Sat, 21 Nov 1998 23:17:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA09566; Sat, 21 Nov 1998 23:15:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811220715.XAA09566@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Zepeda cc: Mike Smith , current Subject: Re: New bootloader oddities In-reply-to: Your message of "Fri, 20 Nov 1998 01:43:13 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Nov 1998 23:15:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, 20 Nov 1998, Mike Smith wrote: > > > If it's printed the message, it's finished with the probe. It's likely > > that it was looking for something else and either hung or you got > > impatient before it timed out. Normal procedure as documented by > > anyone that's ever written up the configuration process is to disable > > everything that you don't have using userconfig; if you haven't tried > > this, you should. > > Ehm. The output I showed was from an a.out kernel which works fine. The > _ELF_ kernel, and the bootblocks don't detect anything. The _ELF_ kernel > hangs after printing the initial probing for PnP devices message.. When you say the bootblocks "don't detect anything", what do you mean? Does 'pnpscan -v' in the bootloader show anything? It sounds like your hardware may be getting upset. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message