From owner-freebsd-stable Sun Dec 13 14:18:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15681 for freebsd-stable-outgoing; Sun, 13 Dec 1998 14:18:28 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gaboon.imcinternet.net (gaboon.nai.net [192.150.121.225]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15674 for ; Sun, 13 Dec 1998 14:18:25 -0800 (PST) (envelope-from asv@gaboon.imcinternet.net) Received: (from asv@localhost) by gaboon.imcinternet.net (8.8.8/8.7.3) id RAA00770 for freebsd-stable@freebsd.org; Sun, 13 Dec 1998 17:20:01 -0500 (EST) From: Stan Voket Message-Id: <199812132220.RAA00770@gaboon.imcinternet.net> Subject: 2.2.8.stable crash, help To: freebsd-stable@FreeBSD.ORG Date: Sun, 13 Dec 1998 17:20:01 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My 2.2.8 stable system has crashed a couple of times today. Last sup this A.M. /var/log yields: Dec 13 16:14:12 europa /kernel: Dec 13 16:14:12 europa /kernel: Fatal trap 12: page fault while in kernel mode Dec 13 16:14:12 europa /kernel: fault virtual address = 0x32b2 Dec 13 16:14:12 europa /kernel: fault code = supervisor read, page not present Dec 13 16:14:12 europa /kernel: instruction pointer = 0x8:0xf01336c6 Dec 13 16:14:12 europa /kernel: stack pointer = 0x10:0xefbfff3c Dec 13 16:14:12 europa /kernel: frame pointer = 0x10:0xf253d300 Dec 13 16:14:12 europa /kernel: code segment = base 0x0, limit 0xffff f, type 0x1b Dec 13 16:14:12 europa /kernel: = DPL 0, pres 1, def32 1, gran 1 Dec 13 16:14:12 europa /kernel: processor eflags = interrupt enabled, res ume, IOPL = 3 Dec 13 16:14:12 europa /kernel: current process = 2 (pagedaemon) Dec 13 16:14:12 europa /kernel: interrupt mask = Dec 13 16:14:12 europa /kernel: panic: page fault Dec 13 16:14:12 europa /kernel: Dec 13 16:14:12 europa /kernel: syncing disks... 7 7 done Any help will be appreciated! Thanks, Stan -- - Stan Voket, asv@gaboon.imcinternet.net - http://gaboon.imcinternet.net - "If you think you can, or you can't; you are _always_ right!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 13 16:04:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00350 for freebsd-stable-outgoing; Sun, 13 Dec 1998 16:04:20 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA00345 for ; Sun, 13 Dec 1998 16:04:17 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zpLUb-0000nY-00; Sun, 13 Dec 1998 16:04:06 -0800 Date: Sun, 13 Dec 1998 16:04:03 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Stan Voket cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.8.stable crash, help In-Reply-To: <199812132220.RAA00770@gaboon.imcinternet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Dec 1998, Stan Voket wrote: > Dec 13 16:14:12 europa /kernel: > Dec 13 16:14:12 europa /kernel: Fatal trap 12: page fault while in > kernel mode > Dec 13 16:14:12 europa /kernel: fault virtual address = 0x32b2 > Dec 13 16:14:12 europa /kernel: fault code = supervisor > read, page > not present Probably bad hardware, most likely memory. If you have ECC or parity memory (and a proper motherboard), it would tell you. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 13 18:14:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13487 for freebsd-stable-outgoing; Sun, 13 Dec 1998 18:14:43 -0800 (PST) (envelope-from owner-freebsd-stable@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 SAA13482 for ; Sun, 13 Dec 1998 18:14:41 -0800 (PST) (envelope-from nrahlstr@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id UAA02484 for ; Sun, 13 Dec 1998 20:14:29 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma002461; Sun, 13 Dec 98 20:14:04 -0600 Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id UAA17551 for freebsd-stable@freebsd.org; Sun, 13 Dec 1998 20:14:03 -0600 (CST) Message-ID: <19981213201402.A17534@winternet.com> Date: Sun, 13 Dec 1998 20:14:02 -0600 From: Nathan Ahlstrom To: freebsd-stable@FreeBSD.ORG Subject: etc.i386/rc.i386 never run Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On -stable cvsup'ed today. /usr/src/etc also merged into /etc today. It appears that /etc/rc sources rc.${arch}, but no rc.i386 exists. Does this mean that I should copy the files from etc.i386/* to /etc? Is that what is intended by this? or is this a bug? and should /etc/rc source etc.${arch}/rc.${arch}? Thanks. Nathan -- Nathan Ahlstrom nrahlstr@winternet.com Run FreeBSD: http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 13 22:26:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05456 for freebsd-stable-outgoing; Sun, 13 Dec 1998 22:26:28 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05220 for ; Sun, 13 Dec 1998 22:25:57 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA07771 for ; Mon, 14 Dec 1998 07:25:50 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18317 for ; Mon, 14 Dec 1998 07:25:49 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA08513 for freebsd-stable@FreeBSD.org; Mon, 14 Dec 1998 06:55:19 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:55:19 +0100 (CET) From: List User Message-Id: <199812140555.GAA08513@doorway.home.lan> To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.stable Path: root From: Nathan Ahlstrom Subject: etc.i386/rc.i386 never run Content-Type: text/plain; charset=us-ascii Received: (from nrahlstr@localhost) by tundra.winternet.com (8.8.7/8.8.4) id UAA17551 for freebsd-stable@freebsd.org; Sun, 13 Dec 1998 20:14:03 -0600 (CST) To: freebsd-stable Sender: owner-freebsd-stable@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <19981213201402.A17534@winternet.com> X-Mailer: Mutt 0.93.2i Delivered-To: vmailer-stable@freebsd.org X-Uidl: 528988f885674ae0906d797ff1eb73e9 X-Loop: FreeBSD.ORG Mime-Version: 1.0 Date: Mon, 14 Dec 1998 02:14:02 GMT On -stable cvsup'ed today. /usr/src/etc also merged into /etc today. It appears that /etc/rc sources rc.${arch}, but no rc.i386 exists. Does this mean that I should copy the files from etc.i386/* to /etc? Is that what is intended by this? or is this a bug? and should /etc/rc source etc.${arch}/rc.${arch}? Thanks. Nathan -- Nathan Ahlstrom nrahlstr@winternet.com Run FreeBSD: http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 13 22:26:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05598 for freebsd-stable-outgoing; Sun, 13 Dec 1998 22:26:45 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05290 for ; Sun, 13 Dec 1998 22:26:03 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA07856 for ; Mon, 14 Dec 1998 07:25:57 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA18337 for ; Mon, 14 Dec 1998 07:25:56 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA07346 for freebsd-stable@FreeBSD.org; Mon, 14 Dec 1998 06:54:28 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:54:28 +0100 (CET) From: List User Message-Id: <199812140554.GAA07346@doorway.home.lan> To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.stable Path: root From: Tom Subject: Re: 2.2.8.stable crash, help Content-Type: TEXT/PLAIN; charset=US-ASCII Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zpLUb-0000nY-00; Sun, 13 Dec 1998 16:04:06 -0800 To: Stan Voket Sender: owner-freebsd-stable@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: Delivered-To: vmailer-stable@freebsd.org X-Uidl: 2e53bfe86d26ec6ba3518554f9e03f34 X-Loop: FreeBSD.ORG Mime-Version: 1.0 X-Sender: tom@shell.uniserve.ca In-Reply-To: <199812132220.RAA00770@gaboon.imcinternet.net> Cc: freebsd-stable Date: Mon, 14 Dec 1998 00:04:03 GMT On Sun, 13 Dec 1998, Stan Voket wrote: > Dec 13 16:14:12 europa /kernel: > Dec 13 16:14:12 europa /kernel: Fatal trap 12: page fault while in > kernel mode > Dec 13 16:14:12 europa /kernel: fault virtual address = 0x32b2 > Dec 13 16:14:12 europa /kernel: fault code = supervisor > read, page > not present Probably bad hardware, most likely memory. If you have ECC or parity memory (and a proper motherboard), it would tell you. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 13 22:40:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10035 for freebsd-stable-outgoing; Sun, 13 Dec 1998 22:40:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netrinsics.com ([210.74.180.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09999 for ; Sun, 13 Dec 1998 22:40:13 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id OAA00472 for freebsd-stable@freebsd.org; Mon, 14 Dec 1998 14:37:09 GMT (envelope-from robinson) Date: Mon, 14 Dec 1998 14:37:09 GMT From: Michael Robinson Message-Id: <199812141437.OAA00472@netrinsics.com> To: freebsd-stable@FreeBSD.ORG Subject: MLEN < write length < MINCLSIZE "bug" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I previously wrote: >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. Well, no one explained it to me, but I played with it anyway. I've come to the following conclusions: 1. This isn't a bug. It's a performance tradeoff of memory efficiency (allocating an mbuf cluster) versus protocol efficiency (sending two packets). 2. MINCLSIZE is an arbitrary value. It only serves to set the threshold for the above performance tradeoff. 3. For certain applications which are latency-sensitive and send many packets in the MLEN < len < MINCLSIZE range over TCP (such as SQUID and IIOP), the current threshold setting is completely inappropriate. However, for other applications (such as large FTP servers), reducing MINCLSIZE would be completely inappropriate. 4. One solution is to make MINCLSIZE a kernel config option. This is ugly, but simple to implement and relatively non-intrusive. 5. Another solution is to add a socket option, and modify kern/uipc_socket.c something like this: - if (resid >= MINCLSIZE) { + if ((resid >= MINCLSIZE) || + ((resid > MLEN) && (so->so_options & SO_NOSPLIT))) { MCLGET(m, M_WAIT); if ((m->m_flags & M_EXT) == 0) goto nopages; mlen = MCLBYTES; len = min(min(mlen, resid), space); } else { With a socket option, applications that wanted low latency (at the expense of more memory usage) could specify that on a per-socket basis. This is less ugly, but requires extensive changes to documentation, header files, and application software. 6. My current solution is just to fix it in sys/mbuf.h: #define MINCLSIZE (MHLEN + 1) /* smallest amount to put in cluster */ This is an ugly solution for general use, but it works well enough for me. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 13 22:54:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA06232 for freebsd-stable-outgoing; Sun, 13 Dec 1998 22:28:14 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05912 for ; Sun, 13 Dec 1998 22:27:17 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id HAA08728 for ; Mon, 14 Dec 1998 07:27:06 +0100 (CET) Received: from doorway.home.lan (t6o1p59.telia.com [195.67.241.119]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id HAA19283 for ; Mon, 14 Dec 1998 07:27:04 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id GAA06363 for freebsd-stable@FreeBSD.org; Mon, 14 Dec 1998 06:53:40 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 06:53:40 +0100 (CET) From: List User Message-Id: <199812140553.GAA06363@doorway.home.lan> To: freebsd-stable@FreeBSD.org Sender: owner-freebsd-stable@FreeBSD.org Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.stable Path: root From: Stan Voket Subject: 2.2.8.stable crash, help Content-Type: text/plain; charset=US-ASCII Received: (from asv@localhost) by gaboon.imcinternet.net (8.8.8/8.7.3) id RAA00770 for freebsd-stable@freebsd.org; Sun, 13 Dec 1998 17:20:01 -0500 (EST) To: freebsd-stable Sender: owner-freebsd-stable@FreeBSD.ORG Content-Transfer-Encoding: 7bit Organization: Private News Host Precedence: bulk Message-ID: <199812132220.RAA00770@gaboon.imcinternet.net> X-Mailer: ELM [version 2.4ME+ PL28 (25)] Delivered-To: vmailer-stable@freebsd.org X-Uidl: 9e517d96302c83ce071896b1cbbf8c06 X-Loop: FreeBSD.ORG Mime-Version: 1.0 Date: Sun, 13 Dec 1998 22:20:01 GMT My 2.2.8 stable system has crashed a couple of times today. Last sup this A.M. /var/log yields: Dec 13 16:14:12 europa /kernel: Dec 13 16:14:12 europa /kernel: Fatal trap 12: page fault while in kernel mode Dec 13 16:14:12 europa /kernel: fault virtual address = 0x32b2 Dec 13 16:14:12 europa /kernel: fault code = supervisor read, page not present Dec 13 16:14:12 europa /kernel: instruction pointer = 0x8:0xf01336c6 Dec 13 16:14:12 europa /kernel: stack pointer = 0x10:0xefbfff3c Dec 13 16:14:12 europa /kernel: frame pointer = 0x10:0xf253d300 Dec 13 16:14:12 europa /kernel: code segment = base 0x0, limit 0xffff f, type 0x1b Dec 13 16:14:12 europa /kernel: = DPL 0, pres 1, def32 1, gran 1 Dec 13 16:14:12 europa /kernel: processor eflags = interrupt enabled, res ume, IOPL = 3 Dec 13 16:14:12 europa /kernel: current process = 2 (pagedaemon) Dec 13 16:14:12 europa /kernel: interrupt mask = Dec 13 16:14:12 europa /kernel: panic: page fault Dec 13 16:14:12 europa /kernel: Dec 13 16:14:12 europa /kernel: syncing disks... 7 7 done Any help will be appreciated! Thanks, Stan -- - Stan Voket, asv@gaboon.imcinternet.net - http://gaboon.imcinternet.net - "If you think you can, or you can't; you are _always_ right!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 13 23:11:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14653 for freebsd-stable-outgoing; Sun, 13 Dec 1998 23:11:53 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14643 for ; Sun, 13 Dec 1998 23:11:50 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.054 #1) id 0zpSA9-0003rT-00; Mon, 14 Dec 1998 09:11:25 +0200 From: Sheldon Hearn To: Nathan Ahlstrom cc: freebsd-stable@FreeBSD.ORG Subject: Re: etc.i386/rc.i386 never run In-reply-to: Your message of "Sun, 13 Dec 1998 20:14:02 CST." <19981213201402.A17534@winternet.com> Date: Mon, 14 Dec 1998 09:11:25 +0200 Message-ID: <14846.913619485@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Dec 1998 20:14:02 CST, Nathan Ahlstrom wrote: > It appears that /etc/rc sources rc.${arch}, but no rc.i386 exists. > > Does this mean that I should copy the files from etc.i386/* to /etc? > Is that what is intended by this? Hi Nathan, You are right about rc sourcing rc.${arch} and also right about rc.${arch} needing to be in /etc . However, I wouldn't recommend "copying the files from etc.i386/* to /etc". Rather, check out ports/sysutils/mergemaster. It does a remarkably good job of merging changes to the source etc/ files with your installed /etc files. Good luck, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 13 23:12:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14807 for freebsd-stable-outgoing; Sun, 13 Dec 1998 23:12:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from noc.datagrid.com (noc-gw.datagrid.com [209.100.40.110]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14800 for ; Sun, 13 Dec 1998 23:12:28 -0800 (PST) (envelope-from bsd@noc.datagrid.com) Received: (qmail 15847 invoked by uid 1119); 14 Dec 1998 09:13:19 -0000 Date: Mon, 14 Dec 1998 09:13:19 +0000 (GMT) From: bsd To: freebsd-stable@FreeBSD.ORG Subject: subscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 01:11:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29409 for freebsd-stable-outgoing; Mon, 14 Dec 1998 01:11:11 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA29392 for ; Mon, 14 Dec 1998 01:11:08 -0800 (PST) (envelope-from dom@phmit.demon.co.uk) Received: from admin [10.100.1.20] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zpU37-0001CS-00; Mon, 14 Dec 1998 09:12:17 +0000 Received: from dom by admin with local (Exim 1.92 #1) id 0zpU5f-00025A-00; Mon, 14 Dec 1998 09:14:55 +0000 To: "Mark W. Krentel" cc: freebsd-stable@FreeBSD.ORG Subject: Mergeing /etc (was: Re: file modes in CVS repository) X-Mailer: nmh v0.26 X-Colour: Green Organization: Palmer & Harvey McLane In-reply-to: "Mark W. Krentel"'s message of "Sat, 12 Dec 1998 21:49:46 EST" <199812130249.VAA10945@dreamscape.com> Date: Mon, 14 Dec 1998 09:14:54 +0000 From: Dominic Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 12 December 1998, "Mark W. Krentel" proclaimed: > I see. I had been merging /etc with /usr/src/etc by hand, but I'm > pleased to learn that it's easier and more organized than I had > thought. And indeed, Nik Clayton's tutorial, "Upgrading FreeBSD from > source", explains the procedure. (I'm blushing.) You may find the "mergemaster" port very useful in this respect. It automates the mergeing of /usr/src/etc with /etc. It's in /usr/ports/sysutils/mergemaster. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator ``Those who do not understand Unix are condemned to reinvent it, poorly.'' -- Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 01:25:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00970 for freebsd-stable-outgoing; Mon, 14 Dec 1998 01:25:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00878 for ; Mon, 14 Dec 1998 01:25:21 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id KAA24349 for ; Mon, 14 Dec 1998 10:25:16 +0100 (CET) Received: from doorway.home.lan (t6o1p48.telia.com [195.67.241.108]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id KAA10732 for ; Mon, 14 Dec 1998 10:25:13 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id JAA11950 for freebsd-stable@FreeBSD.org; Mon, 14 Dec 1998 09:29:44 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 09:29:44 +0100 (CET) From: List User Message-Id: <199812140829.JAA11950@doorway.home.lan> To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.stable Path: root From: bsd Subject: subscribe Content-Type: TEXT/PLAIN; charset=US-ASCII Received: (qmail 15847 invoked by uid 1119); 14 Dec 1998 09:13:19 -0000 To: freebsd-stable Sender: owner-freebsd-stable@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: Delivered-To: vmailer-stable@freebsd.org X-Uidl: 2df88c412051ba1b75aaa0941f0aa45e X-Loop: FreeBSD.ORG Mime-Version: 1.0 Date: Mon, 14 Dec 1998 09:13:19 GMT subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 01:25:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01115 for freebsd-stable-outgoing; Mon, 14 Dec 1998 01:25:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01065 for ; Mon, 14 Dec 1998 01:25:33 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id KAA24491 for ; Mon, 14 Dec 1998 10:25:25 +0100 (CET) Received: from doorway.home.lan (t6o1p48.telia.com [195.67.241.108]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id KAA10768 for ; Mon, 14 Dec 1998 10:25:24 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id JAA11926 for freebsd-stable@FreeBSD.org; Mon, 14 Dec 1998 09:29:42 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 09:29:42 +0100 (CET) From: List User Message-Id: <199812140829.JAA11926@doorway.home.lan> To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.stable Path: root From: Sheldon Hearn Subject: Re: etc.i386/rc.i386 never run Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.054 #1) id 0zpSA9-0003rT-00; Mon, 14 Dec 1998 09:11:25 +0200 To: Nathan Ahlstrom Sender: owner-freebsd-stable@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <14846.913619485@axl.noc.iafrica.com> Delivered-To: vmailer-stable@freebsd.org X-Uidl: 6b5546f758abbe2afcd8449007b14936 X-Loop: FreeBSD.ORG In-Reply-To: Your message of "Sun, 13 Dec 1998 20:14:02 CST." <19981213201402.A17534@winternet.com> Cc: freebsd-stable Date: Mon, 14 Dec 1998 07:11:25 GMT On Sun, 13 Dec 1998 20:14:02 CST, Nathan Ahlstrom wrote: > It appears that /etc/rc sources rc.${arch}, but no rc.i386 exists. > > Does this mean that I should copy the files from etc.i386/* to /etc? > Is that what is intended by this? Hi Nathan, You are right about rc sourcing rc.${arch} and also right about rc.${arch} needing to be in /etc . However, I wouldn't recommend "copying the files from etc.i386/* to /etc". Rather, check out ports/sysutils/mergemaster. It does a remarkably good job of merging changes to the source etc/ files with your installed /etc files. Good luck, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 01:26:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA01339 for freebsd-stable-outgoing; Mon, 14 Dec 1998 01:26:09 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mailb.telia.com (mailb.telia.com [194.22.194.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA01236 for ; Mon, 14 Dec 1998 01:25:55 -0800 (PST) (envelope-from listuser@netspace.net.au) Received: from d1o1.telia.com (root@d1o1.telia.com [195.67.240.241]) by mailb.telia.com (8.8.8/8.8.8) with ESMTP id KAA24771 for ; Mon, 14 Dec 1998 10:25:45 +0100 (CET) Received: from doorway.home.lan (t6o1p48.telia.com [195.67.241.108]) by d1o1.telia.com (8.8.8/8.8.5) with ESMTP id KAA10849 for ; Mon, 14 Dec 1998 10:25:42 +0100 (CET) Received: (from listuser@localhost) by doorway.home.lan (8.8.8/8.8.7) id JAA10763 for freebsd-stable@FreeBSD.org; Mon, 14 Dec 1998 09:28:30 +0100 (CET) (envelope-from listuser) Date: Mon, 14 Dec 1998 09:28:30 +0100 (CET) From: List User Message-Id: <199812140828.JAA10763@doorway.home.lan> To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Newsgroups: freebsd.stable Path: root From: Michael Robinson Subject: MLEN < write length < MINCLSIZE "bug" Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id OAA00472 for freebsd-stable@freebsd.org; Mon, 14 Dec 1998 14:37:09 GMT (envelope-from robinson) To: freebsd-stable Sender: owner-freebsd-stable@FreeBSD.ORG Organization: Private News Host Precedence: bulk Message-ID: <199812141437.OAA00472@netrinsics.com> Delivered-To: vmailer-stable@freebsd.org X-Uidl: 3fc5e9bf08bf023b8c6c90456e2c301d X-Loop: FreeBSD.ORG Date: Mon, 14 Dec 1998 14:37:09 GMT I previously wrote: >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. Well, no one explained it to me, but I played with it anyway. I've come to the following conclusions: 1. This isn't a bug. It's a performance tradeoff of memory efficiency (allocating an mbuf cluster) versus protocol efficiency (sending two packets). 2. MINCLSIZE is an arbitrary value. It only serves to set the threshold for the above performance tradeoff. 3. For certain applications which are latency-sensitive and send many packets in the MLEN < len < MINCLSIZE range over TCP (such as SQUID and IIOP), the current threshold setting is completely inappropriate. However, for other applications (such as large FTP servers), reducing MINCLSIZE would be completely inappropriate. 4. One solution is to make MINCLSIZE a kernel config option. This is ugly, but simple to implement and relatively non-intrusive. 5. Another solution is to add a socket option, and modify kern/uipc_socket.c something like this: - if (resid >= MINCLSIZE) { + if ((resid >= MINCLSIZE) || + ((resid > MLEN) && (so->so_options & SO_NOSPLIT))) { MCLGET(m, M_WAIT); if ((m->m_flags & M_EXT) == 0) goto nopages; mlen = MCLBYTES; len = min(min(mlen, resid), space); } else { With a socket option, applications that wanted low latency (at the expense of more memory usage) could specify that on a per-socket basis. This is less ugly, but requires extensive changes to documentation, header files, and application software. 6. My current solution is just to fix it in sys/mbuf.h: #define MINCLSIZE (MHLEN + 1) /* smallest amount to put in cluster */ This is an ugly solution for general use, but it works well enough for me. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 07:29:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02926 for freebsd-stable-outgoing; Mon, 14 Dec 1998 07:29:14 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02920; Mon, 14 Dec 1998 07:29:12 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id KAA25933; Mon, 14 Dec 1998 10:29:08 -0500 (EST) Date: Mon, 14 Dec 1998 10:29:08 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-scsi@FreeBSD.ORG cc: freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, FWIW, I got the same message today, but the machine didn't lock up. Any ideas? Anyone? I'm cc-ing stable this time in hopes of finding someone running cam under -stable... Here's the messages: Dec 12 03:44:18 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 31 Dec 13 02:01:04 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 2 Dec 14 02:01:21 shell /kernel: (da0:ahc0:0:0:0): tagged openings now 30 Dec 14 10:07:42 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 14 10:07:45 shell /kernel: SEQADDR == 0x8 Dec 14 10:07:45 shell /kernel: SSTAT1 == 0xa Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b Dec 14 10:07:45 shell /kernel: ahc0: Bus Device Reset Sent. 1 SCBs aborted Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." On Fri, 11 Dec 1998, spork wrote: > Hi, > > I'm about to put two new machines in production, and they're both "core" > machines; main dns/auth/mail and a shell machine. Currently the machines > we use in this capacity are 2.1.7.1, and it's been very stable. > > Now the new machines share a RAID array hung off of a CMD CRD-5440. I > patched our usual build (980825 -stable) with the July CAM patchkit, as > the existing AHC driver couldn't detect any LUNs beyond the first one. > > All has been well so far, I've tried to stress the machines as much as > possible by running some disk benchmarks over and over, but yesterday one > locked up (console frozen) with the following messages being the last > thing on the console: > > Dec 10 18:13:15 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Dec 10 18:13:18 shell /kernel: SEQADDR == 0xa > Dec 10 18:13:18 shell /kernel: SSTAT1 == 0xb > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b > Dec 10 18:13:18 shell /kernel: ahc0: Bus Device Reset Sent. 2 SCBs aborted > > I had to give it a hard reset at this point. > > So my questions are: Is this a known issue? Does it point to a possible > hardware problem? Will there be a newer cam patchkit for -stable? > > I don't think it's a cabling issue, as this is the first I've seen of any > anomolies with the scsi subsystem, and the only cabling in question here > is a high quality 2' external UW scsi cable from the back of this machine > to the RAID array. The other machine that uses the other host port on the > RAID array remained functional during this glitch... > > Any ideas? I was very comfortable with CAM before, but now I'm a little > nervous about moving this into production. Would it be better to try and > back out of the patches and use the ahc driver? Let me know if there's > any other info needed. > > Following are the boot messages... > > Thanks, > > Charles > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1992-1998 FreeBSD Inc. > Dec 10 19:27:32 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > Dec 10 19:27:32 shell /kernel: The Regents of the University of California. All rights reserved. > Dec 10 19:27:32 shell /kernel: > Dec 10 19:27:32 shell /kernel: FreeBSD 2.2.7-19980825-SNAP #0: Thu Dec 10 12:02:45 EST 1998 > Dec 10 19:27:32 shell /kernel: spork@shell.inch.com:/usr/src/sys/compile/SHELL > Dec 10 19:27:32 shell /kernel: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) > Dec 10 19:27:32 shell /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 > Dec 10 19:27:32 shell /kernel: Features=0x183f9ff,,MMX,> > Dec 10 19:27:32 shell /kernel: real memory = 268435456 (262144K bytes) > Dec 10 19:27:32 shell /kernel: avail memory = 261144576 (255024K bytes) > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 0: > Dec 10 19:27:32 shell /kernel: chip0 rev 2 on pci0:0:0 > Dec 10 19:27:32 shell /kernel: chip1 rev 2 on pci0:1:0 > Dec 10 19:27:32 shell /kernel: chip2 rev 2 on pci0:4:0 > Dec 10 19:27:32 shell /kernel: chip3 rev 1 on pci0:4:1 > Dec 10 19:27:32 shell /kernel: chip4 rev 1 int d irq 12 on pci0:4:2 > Dec 10 19:27:32 shell /kernel: chip5 rev 2 on pci0:4:3 > Dec 10 19:27:32 shell /kernel: fxp0 Dec 10 19:27:32 shell /kernel: ro 10/100B Ethernet> rev 5 int a irq 10 on pci0:7:0 > Dec 10 19:27:32 shell /kernel: fxp0: Ethernet address 00:e0:18:90:36:4d > Dec 10 19:27:32 shell /kernel: ahc0 rev 1 int a irq 12 on pci0:9:0 > Dec 10 19:27:32 shell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > Dec 10 19:27:32 shell /kernel: fxp1 rev 5 int a irq 10 on pci0:10:0 > Dec 10 19:27:32 shell /kernel: fxp1: Ethernet address 00:a0:c9:e7:ac:7d > Dec 10 19:27:32 shell /kernel: vga0 rev 211 int a irq 11 on pci0:11:0 > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 1: > Dec 10 19:27:32 shell /kernel: Probing for devices on the ISA bus: > Dec 10 19:27:32 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > Dec 10 19:27:32 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > Dec 10 19:27:32 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > Dec 10 19:27:32 shell /kernel: sio0: type 16550A > Dec 10 19:27:32 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > Dec 10 19:27:32 shell /kernel: sio1: type 16550A > Dec 10 19:27:32 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > Dec 10 19:27:32 shell /kernel: lpt0: Interrupt-driven port > Dec 10 19:27:32 shell /kernel: lp0: TCP/IP capable interface > Dec 10 19:27:32 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > Dec 10 19:27:32 shell /kernel: fdc0: FIFO enabled, 8 bytes threshold > Dec 10 19:27:32 shell /kernel: fd0: 1.44MB 3.5in > Dec 10 19:27:32 shell /kernel: npx0 flags 0x1 on motherboard > Dec 10 19:27:32 shell /kernel: npx0: INT 16 interface > Dec 10 19:27:32 shell /kernel: IP packet filtering initialized, divert enabled, logging limited to 200 packets/entry > Dec 10 19:27:32 shell /kernel: da0 at ahc0 bus 0 target 0 lun 0 > Dec 10 19:27:32 shell /kernel: da0: Fixed Direct Access SCSI2 device > Dec 10 19:27:32 shell /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > Dec 10 19:27:32 shell /kernel: da0: 6999MB (14335872 512 byte sectors: 64H 32S/T 6999C) > Dec 10 19:27:32 shell /kernel: da1 at ahc0 bus 0 target 0 lun 1 > Dec 10 19:27:32 shell /kernel: da1: Fixed Direct Access SCSI2 device > Dec 10 19:27:32 shell /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > Dec 10 19:27:32 shell /kernel: da1: 10431MB (21362688 512 byte sectors: 64H 32S/T 10431C) > Dec 10 19:27:32 shell /kernel: WARNING: / was not properly dismounted. > Dec 10 19:27:32 shell /kernel: nfs server 10.0.0.1:/var/mail: not responding > Dec 10 19:27:32 shell savecore: no core dump > > --- > Charles Sprickman > spork@super-g.com > --- > "...there's no idea that's so good you can't > ruin it with a few well-placed idiots." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 08:07:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07028 for freebsd-stable-outgoing; Mon, 14 Dec 1998 08:07:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [130.126.8.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07021 for ; Mon, 14 Dec 1998 08:07:24 -0800 (PST) (envelope-from igor@alecto.physics.uiuc.edu) Received: (from igor@localhost) by alecto.physics.uiuc.edu (8.9.0/8.9.0) id KAA25672; Mon, 14 Dec 1998 10:07:13 -0600 (CST) From: Igor Roshchin Message-Id: <199812141607.KAA25672@alecto.physics.uiuc.edu> Subject: Re: CAM and -stable In-Reply-To: from "spork" at "Dec 14, 1998 10:29: 8 am" To: spork@super-g.com (spork) Date: Mon, 14 Dec 1998 10:07:13 -0600 (CST) Cc: stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Charles, This particular picture is very similar, and almost identical (the messages in your first e-mail ) to what I had on one machine which is running 2.1-stable (after 2.1.7.1) The hardware was : Adaptec 2940UW + Megadrive tower with a 4.x GB HDD (I believe from Western Digital, or may be Seagate) + Quantum (850MB) internal SCSI drive. We decided that the problem was caused by the bad coincidence of the Adaptec 2940+non-perfect driver in 2.1-stable for it + QUANTUM HDD. In my case it was also giving such messages, sometimes hanging, sometimes not - I think depending on whether there was another job waiting for the disk or not. When we had to remove the Megadrive tower, and install another internal SCSI disk, then the problem started to be more severe: At almost any intensive disk usage (like "weekly" script, where we rotate and analyze our web and ftp logs)- it hangs, now without writing anything in the syslog, but just on the console. I doubt this helps, but .. If you'd solve your problem, would you please, let me know what was the reason, and how you solved it ? Thanks, Igor > Hi, > > FWIW, I got the same message today, but the machine didn't lock up. Any > ideas? Anyone? I'm cc-ing stable this time in hopes of finding someone > running cam under -stable... > > Here's the messages: > > Dec 12 03:44:18 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 31 > Dec 13 02:01:04 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 2 > Dec 14 02:01:21 shell /kernel: (da0:ahc0:0:0:0): tagged openings now 30 > Dec 14 10:07:42 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out > while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Dec 14 10:07:45 shell /kernel: SEQADDR == 0x8 > Dec 14 10:07:45 shell /kernel: SSTAT1 == 0xa > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message > Sent > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, > status = 34b > Dec 14 10:07:45 shell /kernel: ahc0: Bus Device Reset Sent. 1 SCBs aborted > > Charles > > --- > Charles Sprickman > spork@super-g.com > --- > "...there's no idea that's so good you can't > ruin it with a few well-placed idiots." > > On Fri, 11 Dec 1998, spork wrote: > > > Hi, > > > > I'm about to put two new machines in production, and they're both "core" > > machines; main dns/auth/mail and a shell machine. Currently the machines > > we use in this capacity are 2.1.7.1, and it's been very stable. > > > > Now the new machines share a RAID array hung off of a CMD CRD-5440. I > > patched our usual build (980825 -stable) with the July CAM patchkit, as > > the existing AHC driver couldn't detect any LUNs beyond the first one. > > > > All has been well so far, I've tried to stress the machines as much as > > possible by running some disk benchmarks over and over, but yesterday one > > locked up (console frozen) with the following messages being the last > > thing on the console: > > > > Dec 10 18:13:15 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > > Dec 10 18:13:18 shell /kernel: SEQADDR == 0xa > > Dec 10 18:13:18 shell /kernel: SSTAT1 == 0xb > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b > > Dec 10 18:13:18 shell /kernel: ahc0: Bus Device Reset Sent. 2 SCBs aborted > > > > I had to give it a hard reset at this point. > > > > So my questions are: Is this a known issue? Does it point to a possible > > hardware problem? Will there be a newer cam patchkit for -stable? > > > > I don't think it's a cabling issue, as this is the first I've seen of any > > anomolies with the scsi subsystem, and the only cabling in question here > > is a high quality 2' external UW scsi cable from the back of this machine > > to the RAID array. The other machine that uses the other host port on the > > RAID array remained functional during this glitch... > > > > Any ideas? I was very comfortable with CAM before, but now I'm a little > > nervous about moving this into production. Would it be better to try and > > back out of the patches and use the ahc driver? Let me know if there's > > any other info needed. > > > > Following are the boot messages... > > > > Thanks, > > > > Charles > > > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1992-1998 FreeBSD Inc. > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > > Dec 10 19:27:32 shell /kernel: The Regents of the University of California. All rights reserved. > > Dec 10 19:27:32 shell /kernel: > > Dec 10 19:27:32 shell /kernel: FreeBSD 2.2.7-19980825-SNAP #0: Thu Dec 10 12:02:45 EST 1998 > > Dec 10 19:27:32 shell /kernel: spork@shell.inch.com:/usr/src/sys/compile/SHELL > > Dec 10 19:27:32 shell /kernel: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) > > Dec 10 19:27:32 shell /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 > > Dec 10 19:27:32 shell /kernel: Features=0x183f9ff,,MMX,> > > Dec 10 19:27:32 shell /kernel: real memory = 268435456 (262144K bytes) > > Dec 10 19:27:32 shell /kernel: avail memory = 261144576 (255024K bytes) > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 0: > > Dec 10 19:27:32 shell /kernel: chip0 rev 2 on pci0:0:0 > > Dec 10 19:27:32 shell /kernel: chip1 rev 2 on pci0:1:0 > > Dec 10 19:27:32 shell /kernel: chip2 rev 2 on pci0:4:0 > > Dec 10 19:27:32 shell /kernel: chip3 rev 1 on pci0:4:1 > > Dec 10 19:27:32 shell /kernel: chip4 rev 1 int d irq 12 on pci0:4:2 > > Dec 10 19:27:32 shell /kernel: chip5 rev 2 on pci0:4:3 > > Dec 10 19:27:32 shell /kernel: fxp0 > Dec 10 19:27:32 shell /kernel: ro 10/100B Ethernet> rev 5 int a irq 10 on pci0:7:0 > > Dec 10 19:27:32 shell /kernel: fxp0: Ethernet address 00:e0:18:90:36:4d > > Dec 10 19:27:32 shell /kernel: ahc0 rev 1 int a irq 12 on pci0:9:0 > > Dec 10 19:27:32 shell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > Dec 10 19:27:32 shell /kernel: fxp1 rev 5 int a irq 10 on pci0:10:0 > > Dec 10 19:27:32 shell /kernel: fxp1: Ethernet address 00:a0:c9:e7:ac:7d > > Dec 10 19:27:32 shell /kernel: vga0 rev 211 int a irq 11 on pci0:11:0 > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 1: > > Dec 10 19:27:32 shell /kernel: Probing for devices on the ISA bus: > > Dec 10 19:27:32 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > > Dec 10 19:27:32 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > > Dec 10 19:27:32 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > > Dec 10 19:27:32 shell /kernel: sio0: type 16550A > > Dec 10 19:27:32 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > > Dec 10 19:27:32 shell /kernel: sio1: type 16550A > > Dec 10 19:27:32 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > > Dec 10 19:27:32 shell /kernel: lpt0: Interrupt-driven port > > Dec 10 19:27:32 shell /kernel: lp0: TCP/IP capable interface > > Dec 10 19:27:32 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > Dec 10 19:27:32 shell /kernel: fdc0: FIFO enabled, 8 bytes threshold > > Dec 10 19:27:32 shell /kernel: fd0: 1.44MB 3.5in > > Dec 10 19:27:32 shell /kernel: npx0 flags 0x1 on motherboard > > Dec 10 19:27:32 shell /kernel: npx0: INT 16 interface > > Dec 10 19:27:32 shell /kernel: IP packet filtering initialized, divert enabled, logging limited to 200 packets/entry > > Dec 10 19:27:32 shell /kernel: da0 at ahc0 bus 0 target 0 lun 0 > > Dec 10 19:27:32 shell /kernel: da0: Fixed Direct Access SCSI2 device > > Dec 10 19:27:32 shell /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > Dec 10 19:27:32 shell /kernel: da0: 6999MB (14335872 512 byte sectors: 64H 32S/T 6999C) > > Dec 10 19:27:32 shell /kernel: da1 at ahc0 bus 0 target 0 lun 1 > > Dec 10 19:27:32 shell /kernel: da1: Fixed Direct Access SCSI2 device > > Dec 10 19:27:32 shell /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > Dec 10 19:27:32 shell /kernel: da1: 10431MB (21362688 512 byte sectors: 64H 32S/T 10431C) > > Dec 10 19:27:32 shell /kernel: WARNING: / was not properly dismounted. > > Dec 10 19:27:32 shell /kernel: nfs server 10.0.0.1:/var/mail: not responding > > Dec 10 19:27:32 shell savecore: no core dump > > > > --- > > Charles Sprickman > > spork@super-g.com > > --- > > "...there's no idea that's so good you can't > > ruin it with a few well-placed idiots." > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 08:57:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11703 for freebsd-stable-outgoing; Mon, 14 Dec 1998 08:57:47 -0800 (PST) (envelope-from owner-freebsd-stable@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 IAA11698; Mon, 14 Dec 1998 08:57:44 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id JAA54340; Mon, 14 Dec 1998 09:57:27 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812141657.JAA54340@panzer.plutotech.com> Subject: Re: CAM and -stable In-Reply-To: from spork at "Dec 14, 98 10:29:08 am" To: spork@super-g.com (spork) Date: Mon, 14 Dec 1998 09:57:27 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG spork wrote... [ sorry for not responding to your previous message. I thought Justin would respond, but evidently he never got around to it. ] > FWIW, I got the same message today, but the machine didn't lock up. Any > ideas? Anyone? I'm cc-ing stable this time in hopes of finding someone > running cam under -stable... > > Here's the messages: > > Dec 12 03:44:18 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 31 > Dec 13 02:01:04 shell /kernel: (da1:ahc0:0:0:1): tagged openings now 2 > Dec 14 02:01:21 shell /kernel: (da0:ahc0:0:0:0): tagged openings now 30 > Dec 14 10:07:42 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out > while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Dec 14 10:07:45 shell /kernel: SEQADDR == 0x8 > Dec 14 10:07:45 shell /kernel: SSTAT1 == 0xa > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message > Sent > Dec 14 10:07:45 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, > status = 34b > Dec 14 10:07:45 shell /kernel: ahc0: Bus Device Reset Sent. 1 SCBs aborted The 'timed out while idle' messages basically mean that a command timed out while we were waiting for it to complete, and there was nothing else going on at the time. I think it generally takes around 10 seconds for that to happen. (It may actually be 60 now...) Generally, it's a sign that the device has gone "out to lunch", and we have to whap it over the head with a BDR to get it to wake up. Another example of a device with that sort of problem is the Quantum Atlas II. (especially firmware revisions earlier than LYK8) Earlier firmware revisions of that drive will go "out to lunch" when there is a lot of bus traffic, You also have another problem, which wasn't evident in your earlier mail. The tagged openings on one of your RAID partitions have gone down to 2. This is a prime example of why it's a good idea to print out the number of tagged openings by default. (Take note all you whiners out there who've been complaining about it.) That indicates that the device keeps sending queue full until we reduce the number of tagged openings to the lowest possible value (2). I would suggest looking in the CMD docs, and try to figure out if they say how many simultaneous transactions the device can handle. Take that number, divide it by 2 (you've got two partitions on the device), and make that the maximum number of tags in a quirk entry in the transport layer. Make the minimum number of tags something slightly less than that. If they don't say how many tags the thing can handle, a good measurement is something in the neighborhood of the first 'reduced tags' number you get. I'm not sure whether the above messages are all of the tagged openings messages, but if they are, you might assume that the thing can handle around 32 tags total. Divided by 2, that's 16. So you could try setting the maximum for each lun to 16, and the minimum to 10 or so. Generally, the system will recover all right from the 'timed out while idle' problem. After we hit the device with a BDR, all the CCBs that have already been sent to the device are aborted, and we requeue them all. > On Fri, 11 Dec 1998, spork wrote: > > > Hi, > > > > I'm about to put two new machines in production, and they're both "core" > > machines; main dns/auth/mail and a shell machine. Currently the machines > > we use in this capacity are 2.1.7.1, and it's been very stable. > > > > Now the new machines share a RAID array hung off of a CMD CRD-5440. I > > patched our usual build (980825 -stable) with the July CAM patchkit, as > > the existing AHC driver couldn't detect any LUNs beyond the first one. > > > > All has been well so far, I've tried to stress the machines as much as > > possible by running some disk benchmarks over and over, but yesterday one > > locked up (console frozen) with the following messages being the last > > thing on the console: > > > > Dec 10 18:13:15 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > > Dec 10 18:13:18 shell /kernel: SEQADDR == 0xa > > Dec 10 18:13:18 shell /kernel: SSTAT1 == 0xb > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b > > Dec 10 18:13:18 shell /kernel: ahc0: Bus Device Reset Sent. 2 SCBs aborted > > > > I had to give it a hard reset at this point. > > > > So my questions are: Is this a known issue? Does it point to a possible > > hardware problem? Will there be a newer cam patchkit for -stable? > > > > I don't think it's a cabling issue, as this is the first I've seen of any > > anomolies with the scsi subsystem, and the only cabling in question here > > is a high quality 2' external UW scsi cable from the back of this machine > > to the RAID array. The other machine that uses the other host port on the > > RAID array remained functional during this glitch... > > > > Any ideas? I was very comfortable with CAM before, but now I'm a little > > nervous about moving this into production. Would it be better to try and > > back out of the patches and use the ahc driver? Let me know if there's > > any other info needed. > > > > Following are the boot messages... > > > > Thanks, > > > > Charles > > > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1992-1998 FreeBSD Inc. > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > > Dec 10 19:27:32 shell /kernel: The Regents of the University of California. All rights reserved. > > Dec 10 19:27:32 shell /kernel: > > Dec 10 19:27:32 shell /kernel: FreeBSD 2.2.7-19980825-SNAP #0: Thu Dec 10 12:02:45 EST 1998 > > Dec 10 19:27:32 shell /kernel: spork@shell.inch.com:/usr/src/sys/compile/SHELL > > Dec 10 19:27:32 shell /kernel: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) > > Dec 10 19:27:32 shell /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 > > Dec 10 19:27:32 shell /kernel: Features=0x183f9ff,,MMX,> > > Dec 10 19:27:32 shell /kernel: real memory = 268435456 (262144K bytes) > > Dec 10 19:27:32 shell /kernel: avail memory = 261144576 (255024K bytes) > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 0: > > Dec 10 19:27:32 shell /kernel: chip0 rev 2 on pci0:0:0 > > Dec 10 19:27:32 shell /kernel: chip1 rev 2 on pci0:1:0 > > Dec 10 19:27:32 shell /kernel: chip2 rev 2 on pci0:4:0 > > Dec 10 19:27:32 shell /kernel: chip3 rev 1 on pci0:4:1 > > Dec 10 19:27:32 shell /kernel: chip4 rev 1 int d irq 12 on pci0:4:2 > > Dec 10 19:27:32 shell /kernel: chip5 rev 2 on pci0:4:3 > > Dec 10 19:27:32 shell /kernel: fxp0 > Dec 10 19:27:32 shell /kernel: ro 10/100B Ethernet> rev 5 int a irq 10 on pci0:7:0 > > Dec 10 19:27:32 shell /kernel: fxp0: Ethernet address 00:e0:18:90:36:4d > > Dec 10 19:27:32 shell /kernel: ahc0 rev 1 int a irq 12 on pci0:9:0 > > Dec 10 19:27:32 shell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > Dec 10 19:27:32 shell /kernel: fxp1 rev 5 int a irq 10 on pci0:10:0 > > Dec 10 19:27:32 shell /kernel: fxp1: Ethernet address 00:a0:c9:e7:ac:7d > > Dec 10 19:27:32 shell /kernel: vga0 rev 211 int a irq 11 on pci0:11:0 > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 1: > > Dec 10 19:27:32 shell /kernel: Probing for devices on the ISA bus: > > Dec 10 19:27:32 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > > Dec 10 19:27:32 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > > Dec 10 19:27:32 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > > Dec 10 19:27:32 shell /kernel: sio0: type 16550A > > Dec 10 19:27:32 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > > Dec 10 19:27:32 shell /kernel: sio1: type 16550A > > Dec 10 19:27:32 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > > Dec 10 19:27:32 shell /kernel: lpt0: Interrupt-driven port > > Dec 10 19:27:32 shell /kernel: lp0: TCP/IP capable interface > > Dec 10 19:27:32 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > Dec 10 19:27:32 shell /kernel: fdc0: FIFO enabled, 8 bytes threshold > > Dec 10 19:27:32 shell /kernel: fd0: 1.44MB 3.5in > > Dec 10 19:27:32 shell /kernel: npx0 flags 0x1 on motherboard > > Dec 10 19:27:32 shell /kernel: npx0: INT 16 interface > > Dec 10 19:27:32 shell /kernel: IP packet filtering initialized, divert enabled, logging limited to 200 packets/entry > > Dec 10 19:27:32 shell /kernel: da0 at ahc0 bus 0 target 0 lun 0 > > Dec 10 19:27:32 shell /kernel: da0: Fixed Direct Access SCSI2 device > > Dec 10 19:27:32 shell /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > Dec 10 19:27:32 shell /kernel: da0: 6999MB (14335872 512 byte sectors: 64H 32S/T 6999C) > > Dec 10 19:27:32 shell /kernel: da1 at ahc0 bus 0 target 0 lun 1 > > Dec 10 19:27:32 shell /kernel: da1: Fixed Direct Access SCSI2 device > > Dec 10 19:27:32 shell /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > Dec 10 19:27:32 shell /kernel: da1: 10431MB (21362688 512 byte sectors: 64H 32S/T 10431C) > > Dec 10 19:27:32 shell /kernel: WARNING: / was not properly dismounted. > > Dec 10 19:27:32 shell /kernel: nfs server 10.0.0.1:/var/mail: not responding > > Dec 10 19:27:32 shell savecore: no core dump > > > > --- > > Charles Sprickman > > spork@super-g.com > > --- > > "...there's no idea that's so good you can't > > ruin it with a few well-placed idiots." > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 09:03:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12352 for freebsd-stable-outgoing; Mon, 14 Dec 1998 09:03:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.2.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12347 for ; Mon, 14 Dec 1998 09:03:25 -0800 (PST) (envelope-from marc@acadiau.ca) Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.103]) by garlic.acadiau.ca (8.8.5/8.8.5) with ESMTP id MAA26454; Mon, 14 Dec 1998 12:55:18 -0400 (AST) Date: Mon, 14 Dec 1998 12:54:59 -0400 (AST) From: "Marc G. Fournier" To: Igor Roshchin cc: spork , stable@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: <199812141607.KAA25672@alecto.physics.uiuc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 14 Dec 1998, Igor Roshchin wrote: > Hi, Charles, > > This particular picture is very similar, and almost identical (the > messages in your first e-mail ) > to what I had on one machine which is running 2.1-stable > (after 2.1.7.1) > The hardware was : Adaptec 2940UW + Megadrive tower with a 4.x GB HDD > (I believe from Western Digital, or may be Seagate) > + Quantum (850MB) internal SCSI drive. > > We decided that the problem was caused by the bad coincidence of the > Adaptec 2940+non-perfect driver in 2.1-stable for it + QUANTUM HDD. I have to ask...what is a 'bad coincidence'? Marc G. Fournier marc.fournier@acadiau.ca Systems Administrator, Acadia University "These are my opinions, which are not necessarily shared by my employer" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 09:43:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16632 for freebsd-stable-outgoing; Mon, 14 Dec 1998 09:43:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16625; Mon, 14 Dec 1998 09:43:51 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id MAA10160; Mon, 14 Dec 1998 12:43:11 -0500 (EST) Date: Mon, 14 Dec 1998 12:43:11 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: <199812141657.JAA54340@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 14 Dec 1998, Kenneth D. Merry wrote: > spork wrote... > > [ sorry for not responding to your previous message. I thought Justin > would respond, but evidently he never got around to it. ] No problem, I was a little nervous, that's all... > Generally, it's a sign that the device has gone "out to lunch", and we have > to whap it over the head with a BDR to get it to wake up. Are you aware of anyone else running a CMD controller? I know wcarchive is using the Mylex box. I hope I've made a good choice... > You also have another problem, which wasn't evident in your earlier mail. > The tagged openings on one of your RAID partitions have gone down to 2. > That indicates that the device keeps sending queue full until we reduce the > number of tagged openings to the lowest possible value (2). I would > suggest looking in the CMD docs, and try to figure out if they say how many > simultaneous transactions the device can handle. Take that number, divide > it by 2 (you've got two partitions on the device), and make that the > maximum number of tags in a quirk entry in the transport layer. Make the > minimum number of tags something slightly less than that. How and where do I set the number of tags? The docs (http://www.cmd.com/storage/products/docs/datasheet/crd5440.cfm) say that the unit can queue 64 commands. There are two hosts on this controller in our installation. I'm no scsi genius, are 'tags' and 'queued commands' the same thing? > Generally, the system will recover all right from the 'timed out while > idle' problem. After we hit the device with a BDR, all the CCBs that have > already been sent to the device are aborted, and we requeue them all. Yep, it's only froze up completely once. Is your feeling that if I adjust it to use less tags this should go away? I checked the CMD website, and there is one more firmware update, but it doesn't address any serious issues. And one last thing, will there ever be a newer patchkit for CAM under stable? My timing is horrible, I need to put these machines in production in the next week or so, so I can't really go to 3.x right now... In 6 months or so, sure, but these will probably remain at 2.2 for quite some time. Are there major changes from what I'm running in the 3.x tree? Thanks very much, Charles ps- if anyone feels the crosspost to -stable and -scsi is unneeded, feel free to remove the less appropriate list... > > > On Fri, 11 Dec 1998, spork wrote: > > > > > Hi, > > > > > > I'm about to put two new machines in production, and they're both "core" > > > machines; main dns/auth/mail and a shell machine. Currently the machines > > > we use in this capacity are 2.1.7.1, and it's been very stable. > > > > > > Now the new machines share a RAID array hung off of a CMD CRD-5440. I > > > patched our usual build (980825 -stable) with the July CAM patchkit, as > > > the existing AHC driver couldn't detect any LUNs beyond the first one. > > > > > > All has been well so far, I've tried to stress the machines as much as > > > possible by running some disk benchmarks over and over, but yesterday one > > > locked up (console frozen) with the following messages being the last > > > thing on the console: > > > > > > Dec 10 18:13:15 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > > > Dec 10 18:13:18 shell /kernel: SEQADDR == 0xa > > > Dec 10 18:13:18 shell /kernel: SSTAT1 == 0xb > > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent > > > Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b > > > Dec 10 18:13:18 shell /kernel: ahc0: Bus Device Reset Sent. 2 SCBs aborted > > > > > > I had to give it a hard reset at this point. > > > > > > So my questions are: Is this a known issue? Does it point to a possible > > > hardware problem? Will there be a newer cam patchkit for -stable? > > > > > > I don't think it's a cabling issue, as this is the first I've seen of any > > > anomolies with the scsi subsystem, and the only cabling in question here > > > is a high quality 2' external UW scsi cable from the back of this machine > > > to the RAID array. The other machine that uses the other host port on the > > > RAID array remained functional during this glitch... > > > > > > Any ideas? I was very comfortable with CAM before, but now I'm a little > > > nervous about moving this into production. Would it be better to try and > > > back out of the patches and use the ahc driver? Let me know if there's > > > any other info needed. > > > > > > Following are the boot messages... > > > > > > Thanks, > > > > > > Charles > > > > > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1992-1998 FreeBSD Inc. > > > Dec 10 19:27:32 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 > > > Dec 10 19:27:32 shell /kernel: The Regents of the University of California. All rights reserved. > > > Dec 10 19:27:32 shell /kernel: > > > Dec 10 19:27:32 shell /kernel: FreeBSD 2.2.7-19980825-SNAP #0: Thu Dec 10 12:02:45 EST 1998 > > > Dec 10 19:27:32 shell /kernel: spork@shell.inch.com:/usr/src/sys/compile/SHELL > > > Dec 10 19:27:32 shell /kernel: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) > > > Dec 10 19:27:32 shell /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 > > > Dec 10 19:27:32 shell /kernel: Features=0x183f9ff,,MMX,> > > > Dec 10 19:27:32 shell /kernel: real memory = 268435456 (262144K bytes) > > > Dec 10 19:27:32 shell /kernel: avail memory = 261144576 (255024K bytes) > > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 0: > > > Dec 10 19:27:32 shell /kernel: chip0 rev 2 on pci0:0:0 > > > Dec 10 19:27:32 shell /kernel: chip1 rev 2 on pci0:1:0 > > > Dec 10 19:27:32 shell /kernel: chip2 rev 2 on pci0:4:0 > > > Dec 10 19:27:32 shell /kernel: chip3 rev 1 on pci0:4:1 > > > Dec 10 19:27:32 shell /kernel: chip4 rev 1 int d irq 12 on pci0:4:2 > > > Dec 10 19:27:32 shell /kernel: chip5 rev 2 on pci0:4:3 > > > Dec 10 19:27:32 shell /kernel: fxp0 > > Dec 10 19:27:32 shell /kernel: ro 10/100B Ethernet> rev 5 int a irq 10 on pci0:7:0 > > > Dec 10 19:27:32 shell /kernel: fxp0: Ethernet address 00:e0:18:90:36:4d > > > Dec 10 19:27:32 shell /kernel: ahc0 rev 1 int a irq 12 on pci0:9:0 > > > Dec 10 19:27:32 shell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > > Dec 10 19:27:32 shell /kernel: fxp1 rev 5 int a irq 10 on pci0:10:0 > > > Dec 10 19:27:32 shell /kernel: fxp1: Ethernet address 00:a0:c9:e7:ac:7d > > > Dec 10 19:27:32 shell /kernel: vga0 rev 211 int a irq 11 on pci0:11:0 > > > Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 1: > > > Dec 10 19:27:32 shell /kernel: Probing for devices on the ISA bus: > > > Dec 10 19:27:32 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > > > Dec 10 19:27:32 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> > > > Dec 10 19:27:32 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa > > > Dec 10 19:27:32 shell /kernel: sio0: type 16550A > > > Dec 10 19:27:32 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > > > Dec 10 19:27:32 shell /kernel: sio1: type 16550A > > > Dec 10 19:27:32 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa > > > Dec 10 19:27:32 shell /kernel: lpt0: Interrupt-driven port > > > Dec 10 19:27:32 shell /kernel: lp0: TCP/IP capable interface > > > Dec 10 19:27:32 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > > > Dec 10 19:27:32 shell /kernel: fdc0: FIFO enabled, 8 bytes threshold > > > Dec 10 19:27:32 shell /kernel: fd0: 1.44MB 3.5in > > > Dec 10 19:27:32 shell /kernel: npx0 flags 0x1 on motherboard > > > Dec 10 19:27:32 shell /kernel: npx0: INT 16 interface > > > Dec 10 19:27:32 shell /kernel: IP packet filtering initialized, divert enabled, logging limited to 200 packets/entry > > > Dec 10 19:27:32 shell /kernel: da0 at ahc0 bus 0 target 0 lun 0 > > > Dec 10 19:27:32 shell /kernel: da0: Fixed Direct Access SCSI2 device > > > Dec 10 19:27:32 shell /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > > Dec 10 19:27:32 shell /kernel: da0: 6999MB (14335872 512 byte sectors: 64H 32S/T 6999C) > > > Dec 10 19:27:32 shell /kernel: da1 at ahc0 bus 0 target 0 lun 1 > > > Dec 10 19:27:32 shell /kernel: da1: Fixed Direct Access SCSI2 device > > > Dec 10 19:27:32 shell /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > > > Dec 10 19:27:32 shell /kernel: da1: 10431MB (21362688 512 byte sectors: 64H 32S/T 10431C) > > > Dec 10 19:27:32 shell /kernel: WARNING: / was not properly dismounted. > > > Dec 10 19:27:32 shell /kernel: nfs server 10.0.0.1:/var/mail: not responding > > > Dec 10 19:27:32 shell savecore: no core dump > > > > > > --- > > > Charles Sprickman > > > spork@super-g.com > > > --- > > > "...there's no idea that's so good you can't > > > ruin it with a few well-placed idiots." > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 09:53:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17843 for freebsd-stable-outgoing; Mon, 14 Dec 1998 09:53:38 -0800 (PST) (envelope-from owner-freebsd-stable@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 JAA17837; Mon, 14 Dec 1998 09:53:34 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA54713; Mon, 14 Dec 1998 10:53:10 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812141753.KAA54713@panzer.plutotech.com> Subject: Re: CAM and -stable In-Reply-To: from spork at "Dec 14, 98 12:43:11 pm" To: spork@super-g.com (spork) Date: Mon, 14 Dec 1998 10:53:10 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG spork wrote... > On Mon, 14 Dec 1998, Kenneth D. Merry wrote: > > > spork wrote... > > > > [ sorry for not responding to your previous message. I thought Justin > > would respond, but evidently he never got around to it. ] > > No problem, I was a little nervous, that's all... > > > Generally, it's a sign that the device has gone "out to lunch", and we have > > to whap it over the head with a BDR to get it to wake up. > > Are you aware of anyone else running a CMD controller? I know wcarchive > is using the Mylex box. I hope I've made a good choice... I believe Karl Denninger is using a CMD controller on one of his machines, with CAM. You'd have to ask him for details, though. > > You also have another problem, which wasn't evident in your earlier mail. > > The tagged openings on one of your RAID partitions have gone down to 2. > > That indicates that the device keeps sending queue full until we reduce the > > number of tagged openings to the lowest possible value (2). I would > > suggest looking in the CMD docs, and try to figure out if they say how many > > simultaneous transactions the device can handle. Take that number, divide > > it by 2 (you've got two partitions on the device), and make that the > > maximum number of tags in a quirk entry in the transport layer. Make the > > minimum number of tags something slightly less than that. > > How and where do I set the number of tags? The docs > (http://www.cmd.com/storage/products/docs/datasheet/crd5440.cfm) say that > the unit can queue 64 commands. There are two hosts on this controller in > our installation. I'm no scsi genius, are 'tags' and 'queued commands' > the same thing? Yes, they are. > > Generally, the system will recover all right from the 'timed out while > > idle' problem. After we hit the device with a BDR, all the CCBs that have > > already been sent to the device are aborted, and we requeue them all. > > Yep, it's only froze up completely once. Is your feeling that if I adjust > it to use less tags this should go away? I checked the CMD website, and > there is one more firmware update, but it doesn't address any serious > issues. It might very well go away. The only way to find out is to try it. Since it can supposedly handle 64 commands, you might try setting the maximum in the quirk entry to 32, to divide the load evenly. You could set the minimum to 24 or so. > And one last thing, will there ever be a newer patchkit for CAM under > stable? My timing is horrible, I need to put these machines in production > in the next week or so, so I can't really go to 3.x right now... In 6 > months or so, sure, but these will probably remain at 2.2 for quite some > time. Are there major changes from what I'm running in the 3.x tree? Yes, there will be a new -stable patchkit. At least that's been the plan. Justin makes the snapshots, and I'm not sure what his plans are. I can tell you, however, that unless it gets made this week (unlikely), it won't happen until January. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 10:37:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23322 for freebsd-stable-outgoing; Mon, 14 Dec 1998 10:37:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23317 for ; Mon, 14 Dec 1998 10:37:33 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id KAA26875; Mon, 14 Dec 1998 10:37:24 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id KAA10523; Mon, 14 Dec 1998 10:37:24 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id LAA29697; Mon, 14 Dec 1998 11:37:23 -0700 Message-ID: <36755AE3.FB91BC8E@softweyr.com> Date: Mon, 14 Dec 1998 11:37:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: High speed serial on -STABLE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone using the 16C650 support in sio.c on -STABLE, or any other recent 2.2.x? I have a FreeBSD dialup server that I'm adding ISDN support to, and need to buy a fast(er) serial card to support an extern T/A. Thanks in advance for your help. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 10:55:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25768 for freebsd-stable-outgoing; Mon, 14 Dec 1998 10:55:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [130.126.8.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25762 for ; Mon, 14 Dec 1998 10:55:11 -0800 (PST) (envelope-from igor@alecto.physics.uiuc.edu) Received: (from igor@localhost) by alecto.physics.uiuc.edu (8.9.0/8.9.0) id MAA03819; Mon, 14 Dec 1998 12:53:51 -0600 (CST) From: Igor Roshchin Message-Id: <199812141853.MAA03819@alecto.physics.uiuc.edu> Subject: Re: CAM and -stable In-Reply-To: from "Marc G. Fournier" at "Dec 14, 1998 12:54:59 pm" To: marc.fournier@acadiau.ca (Marc G. Fournier) Date: Mon, 14 Dec 1998 12:53:51 -0600 (CST) Cc: stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 14 Dec 1998, Igor Roshchin wrote: > > > Hi, Charles, > > > > This particular picture is very similar, and almost identical (the > > messages in your first e-mail ) > > to what I had on one machine which is running 2.1-stable > > (after 2.1.7.1) > > The hardware was : Adaptec 2940UW + Megadrive tower with a 4.x GB HDD > > (I believe from Western Digital, or may be Seagate) > > + Quantum (850MB) internal SCSI drive. > > > > We decided that the problem was caused by the bad coincidence of the > > Adaptec 2940+non-perfect driver in 2.1-stable for it + QUANTUM HDD. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > I have to ask...what is a 'bad coincidence'? > Mark, It's mentioned there. Sorry for the vague statement. By coincidence I ment that we had two problems at a time: AHC driver in 2.1-stable and Quantum HDD which had some problems, which is known for be problematic. Igor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 15:09:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27484 for freebsd-stable-outgoing; Mon, 14 Dec 1998 15:09:47 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ns2.inch.com (oscar.inch.com [207.240.140.102]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27467; Mon, 14 Dec 1998 15:09:43 -0800 (PST) (envelope-from spork@super-g.com) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by ns2.inch.com (8.8.8/8.8.5) with ESMTP id SAA23466; Mon, 14 Dec 1998 18:09:39 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id SAA12259; Mon, 14 Dec 1998 18:08:33 -0500 (EST) Date: Mon, 14 Dec 1998 18:08:33 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: <199812141753.KAA54713@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I'm just going to bug you one more time with two questions: Where can I find more docs for cam? Like cam(3) or something? How can I adjust things so that only a certain amount of tags are used (like we've been discussing)? I assume it has something to do with "quirk entries", but I'm not sure where that type of thing gets defined... Thanks again, Charles --- Charles Sprickman spork@super-g.com On Mon, 14 Dec 1998, Kenneth D. Merry wrote: > It might very well go away. The only way to find out is to try it. Since > it can supposedly handle 64 commands, you might try setting the maximum in > the quirk entry to 32, to divide the load evenly. You could set the > minimum to 24 or so. > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 15:21:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29030 for freebsd-stable-outgoing; Mon, 14 Dec 1998 15:21:38 -0800 (PST) (envelope-from owner-freebsd-stable@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 PAA29024; Mon, 14 Dec 1998 15:21:36 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA56332; Mon, 14 Dec 1998 16:21:27 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812142321.QAA56332@panzer.plutotech.com> Subject: Re: CAM and -stable In-Reply-To: from spork at "Dec 14, 98 06:08:33 pm" To: spork@super-g.com (spork) Date: Mon, 14 Dec 1998 16:21:27 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG spork wrote... > OK, I'm just going to bug you one more time with two questions: > > Where can I find more docs for cam? Like cam(3) or something? There are lots of man pages. It just depends on what you want documentation on. Most of the controller drivers have man pages (like ahc(4), dpt(4)). All of the peripheral drivers have man pages (like da(4), pass(4)). If you want generic kernel configuration information, see scsi(4). (a.k.a. cam(4)) cam(3) certainly exists, but it's probably not what you're looking for. (Unless you're writing a userland SCSI pass-through program) Oops, I just realized that you're using -stable. Most of those man pages aren't available in -stable. In any case, the quirk entry stuff you want to do isn't documented anywhere, so the docs from -current wouldn't help. > How can I adjust things so that only a certain amount of tags are used > (like we've been discussing)? I assume it has something to do with > "quirk entries", but I'm not sure where that type of thing gets defined... Oh, I should have been a little more clear there. Go into sys/cam/cam_xpt.c, and look around near the top of the file. You'll see a quirk table with entries like this: { /* Reports QUEUE FULL for temporary resource shortages */ { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP39100*", "*" }, /*quirks*/0, /*mintags*/24, /*maxtags*/32 }, And, as far as numbers go, I'd suggest that you use exactly the numbers that we use for the Atlas II, above. They'll apply to both luns of your RAID controller, so the available tag openings will be evenly split between the two. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 15:56:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03500 for freebsd-stable-outgoing; Mon, 14 Dec 1998 15:56:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03494; Mon, 14 Dec 1998 15:56:39 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id SAA17264; Mon, 14 Dec 1998 18:56:03 -0500 (EST) Date: Mon, 14 Dec 1998 18:56:03 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: <199812142321.QAA56332@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Ken, This is your day. I'm giving the following a spin. I'm not much into C, but I think I got all the fields right: > /* Added to fix CRD-5440's lack of tags */ > { T_DIRECT, SIP_MEDIA_FIXED, "CMD TECH", "CRD-5440*", "*"}, > /*quirks*/0, /*mintags*/22, /*maxtags*/30 > }, > { Thanks again, I appreciate your help with this... Charles --- Charles Sprickman spork@super-g.com On Mon, 14 Dec 1998, Kenneth D. Merry wrote: > Oh, I should have been a little more clear there. Go into > sys/cam/cam_xpt.c, and look around near the top of the file. You'll see a > quirk table with entries like this: > > { > /* Reports QUEUE FULL for temporary resource shortages */ > { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP39100*", "*" }, > /*quirks*/0, /*mintags*/24, /*maxtags*/32 > }, > > And, as far as numbers go, I'd suggest that you use exactly the numbers > that we use for the Atlas II, above. They'll apply to both luns of your > RAID controller, so the available tag openings will be evenly split between > the two. > > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 17:10:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13497 for freebsd-stable-outgoing; Mon, 14 Dec 1998 17:10:46 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13489 for ; Mon, 14 Dec 1998 17:10:43 -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 DAA00525; Mon, 14 Dec 1998 03:21:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812141121.DAA00525@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mian Nawaz Sharif cc: stable@FreeBSD.ORG Subject: Re: hardware upgrade gone awry In-reply-to: Your message of "Tue, 08 Dec 1998 04:56:14 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 03:21:31 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > i just upgraded from a 100 mhz intel to an amd k6-2 350 3d processor and > tyan S1590 m/board. along with that, i also got a new hard drive. my > kernel is probably around 2-3 weeks old. now my problem: > > earlier, my freebsd hard drive was wd1. since it wasn't the master drive, > i was using a floppy disk to get to the boot prompt, and then entering > wd(1,a)kernel to boot it up, and it worked fine. > > now, i seem to be having a major problem with it for some reason. when i > type in the same command at the boot prompt, i start loading up the > kernel, and then i get this: > > changing root devicee to wd1s1a > changing root device to wd1a > error 6: panic: can not mount root (2) > > and then the system reboots. > > during this time, i dont see wd1 show up in the 'dmesg' stuff that scrolls > by as the kernel looks for various devices, but i can get the / partitions > listing by typing `wd(1,a)?` at the boot prompt. > > my question: > is there some way that i can fix the problem, and if not that, access my > drive and move some stuff off it onto a dos fat32 partition on the other > drive, so i can just do a clean install? You've connected your second drive as the master on the second bus; it's drive 1 (of 0,1) to the BIOS, but drive 2 (of 0,2) to FreeBSD. You can either move the drive back to the first bus (quicker), or boot with '1:wd(2,a)kernel -s', mount /dev/wd2s1a on / (and other filesystems from there if you need them), update your /etc/fstab file to refer to 'wd2' rather than 'wd1', then put the boot string you used above in /boot.config. -- \\ 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-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 18:49:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27568 for freebsd-stable-outgoing; Mon, 14 Dec 1998 18:49:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27563 for ; Mon, 14 Dec 1998 18:49:07 -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 SAA02006; Mon, 14 Dec 1998 18:47:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812150247.SAA02006@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Robinson cc: freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Mon, 14 Dec 1998 14:37:09 GMT." <199812141437.OAA00472@netrinsics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 18:47:04 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I previously wrote: > >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. > > Well, no one explained it to me, but I played with it anyway. I've come to > the following conclusions: > > 1. This isn't a bug. It's a performance tradeoff of memory efficiency > (allocating an mbuf cluster) versus protocol efficiency (sending > two packets). > > 2. MINCLSIZE is an arbitrary value. It only serves to set the threshold > for the above performance tradeoff. > > 3. For certain applications which are latency-sensitive and send many > packets in the MLEN < len < MINCLSIZE range over TCP (such as SQUID > and IIOP), the current threshold setting is completely inappropriate. > However, for other applications (such as large FTP servers), reducing > MINCLSIZE would be completely inappropriate. > > 4. One solution is to make MINCLSIZE a kernel config option. This is ugly, > but simple to implement and relatively non-intrusive. It should be a sysctl variable, not a kernel option, in this case. But that's certainly the simplest way to go. Want to implement this? > 5. Another solution is to add a socket option, and modify kern/uipc_socket.c > something like this: > > - if (resid >= MINCLSIZE) { > + if ((resid >= MINCLSIZE) || > + ((resid > MLEN) && (so->so_options & SO_NOSPLIT))) { > MCLGET(m, M_WAIT); > if ((m->m_flags & M_EXT) == 0) > goto nopages; > mlen = MCLBYTES; > len = min(min(mlen, resid), space); > } else { > > With a socket option, applications that wanted low latency (at the > expense of more memory usage) could specify that on a per-socket basis. > This is less ugly, but requires extensive changes to documentation, > header files, and application software. Do you think you could come up with a heuristic that would be able to detect when the current behaviour was losing, reliably? If so, you could use this to switch the option... -- \\ 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-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 20:34:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07406 for freebsd-stable-outgoing; Mon, 14 Dec 1998 20:34:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netrinsics.com ([210.74.176.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07401 for ; Mon, 14 Dec 1998 20:34:06 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id MAA06983; Tue, 15 Dec 1998 12:27:57 GMT (envelope-from robinson) Date: Tue, 15 Dec 1998 12:27:57 GMT From: Michael Robinson Message-Id: <199812151227.MAA06983@netrinsics.com> To: mike@smith.net.au, robinson@netrinsics.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <199812150247.SAA02006@dingo.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: >> 4. One solution is to make MINCLSIZE a kernel config option. This is ugly, >> but simple to implement and relatively non-intrusive. > >It should be a sysctl variable, not a kernel option, in this case. But >that's certainly the simplest way to go. Want to implement this? Will do. Will patches against the 2.2.7-RELEASE CVS repository be acceptable? If there hasn't been too much drift, they should easily merge into -STABLE, and maybe even -CURRENT. >> With a socket option, applications that wanted low latency (at the >> expense of more memory usage) could specify that on a per-socket basis. >> This is less ugly, but requires extensive changes to documentation, >> header files, and application software. > >Do you think you could come up with a heuristic that would be able to >detect when the current behaviour was losing, reliably? If so, you >could use this to switch the option... By adding one or two bookkeeping fields to the socket structure it would be possible to implement such an heuristic. However, there are three reasons I don't think that is such a good idea: 1. Protocol inefficiencies from sending multiple packets are, by their nature, protocol dependent. Ergo, we would want different heuristics for different families (LOCAL, INET, ISO, etc.) and types (STREAM, DGRAM, etc.) of socket. Which gets really ugly really fast. 2. There is no method to determine how much any given application cares about protocol inefficiencies on any given socket. The heuristic would be making perhaps unwarranted assumptions about what performance characteristics were desireable in a particular instance. Which is how we got into this mess in the first place. 3. It would be non-trivial extra code in a pretty performance-sensitive part of the kernel (the innermost loop of sosend). For these reasons, I think a socket option makes more sense than trying to resolve the problem automagically in the kernel. Perhaps a more tractable solution would be a system-wide heuristic, such as is used with filesystem tuning. I.e., if there are mbuf clusters to burn, burn 'em, baby. Otherwise, send multiple packets. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 20:40:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08264 for freebsd-stable-outgoing; Mon, 14 Dec 1998 20:40:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (goldfish.pht.co.jp [210.171.55.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08238 for ; Mon, 14 Dec 1998 20:40: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 UAA02728; Mon, 14 Dec 1998 20:37:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812150437.UAA02728@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Michael Robinson cc: mike@smith.net.au, freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Tue, 15 Dec 1998 12:27:57 GMT." <199812151227.MAA06983@netrinsics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 1998 20:36:54 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > >> 4. One solution is to make MINCLSIZE a kernel config option. This is ugly, > >> but simple to implement and relatively non-intrusive. > > > >It should be a sysctl variable, not a kernel option, in this case. But > >that's certainly the simplest way to go. Want to implement this? > > Will do. Will patches against the 2.2.7-RELEASE CVS repository be acceptable? > If there hasn't been too much drift, they should easily merge into -STABLE, > and maybe even -CURRENT. I'd really prefer diffs against -current; that's where this would be committed. > >Do you think you could come up with a heuristic that would be able to > >detect when the current behaviour was losing, reliably? If so, you > >could use this to switch the option... > > By adding one or two bookkeeping fields to the socket structure it would be > possible to implement such an heuristic. However, there are three reasons I > don't think that is such a good idea: ... > For these reasons, I think a socket option makes more sense than trying to > resolve the problem automagically in the kernel. That makes sense. > Perhaps a more tractable solution would be a system-wide heuristic, such as > is used with filesystem tuning. I.e., if there are mbuf clusters to burn, > burn 'em, baby. Otherwise, send multiple packets. That's *definitely* a better idea, and not much harder than the sysctl. Again, diffs against -current would be good, but anything'd be a start... -- \\ 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-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 21:44:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14488 for freebsd-stable-outgoing; Mon, 14 Dec 1998 21:44:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netrinsics.com ([210.74.175.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14479; Mon, 14 Dec 1998 21:44:12 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id NAA07127; Tue, 15 Dec 1998 13:40:42 GMT (envelope-from robinson) Date: Tue, 15 Dec 1998 13:40:42 GMT From: Michael Robinson Message-Id: <199812151340.NAA07127@netrinsics.com> To: fenner@parc.xerox.com, robinson@netrinsics.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <98Dec14.205241pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fenner writes: >In message <199812141437.OAA00472@netrinsics.com> you write: >> 1. This isn't a bug. It's a performance tradeoff of memory efficiency >> (allocating an mbuf cluster) versus protocol efficiency (sending >> two packets). > >I still think it's a bug; that's why I wrote the (buggy) patch referred >to in the Squid FAQ. See my discussion at >http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/uipc_socket.c#rev1.41 >(and in particular, the paragraph labelled "The real fix"...) Well, I've explained the problem, and given a fix (reduce MINCLSIZE to MHLEN+1). You can try my fix, and if it causes any problems for you (other than causing your Squid server to run out of mbuf clusters), then I'll go back to the drawing board. Your "real fix" (accumulate an mbuf chain until it exceeded the "requested transfer size") seems unlikely to fix the problem for Squid and IIOP, because the problem is that writes which are bigger than one mbuf, but smaller than two, don't get sent atomically and immediately (causing protocol latency). Your discussion overlooks the fact that these are client-server protocols that are going to write a request on a socket and then wait for a response. "Accumulating mbufs" until they exceed the TCP MSS is a recipe for deadlock. In such a situation, the only acceptable "requested transfer size" is the length of the write itself, and my fix implements that. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 21:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15748 for freebsd-stable-outgoing; Mon, 14 Dec 1998 21:52:09 -0800 (PST) (envelope-from owner-freebsd-stable@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 VAA15732; Mon, 14 Dec 1998 21:52:07 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from mango.parc.xerox.com ([13.1.102.232]) by alpha.xerox.com with SMTP id <55377(4)>; Mon, 14 Dec 1998 21:52:01 PST Received: (from fenner@localhost) by mango.parc.xerox.com (8.8.8/8.8.8) id VAA17801; Mon, 14 Dec 1998 21:52:00 -0800 (PST) (envelope-from fenner) Date: Mon, 14 Dec 1998 21:52:00 PST From: Bill Fenner Message-Id: <199812150552.VAA17801@mango.parc.xerox.com> To: fenner@parc.xerox.com, robinson@netrinsics.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <199812151340.NAA07127@netrinsics.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You misunderstand. The fix is to accumulate mbufs in a chain until either a) The protocol gets all of the data that it wanted, or b) All of the data that the user has provided has been copied into mbufs. (b) is what sosend() used to do. The URL referenced (the one with "vanj88" in it) describes why sosend() was changed to use only a single mbuf at a time, but this performance problem was not envisioned at the time. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 14 23:32:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25396 for freebsd-stable-outgoing; Mon, 14 Dec 1998 23:32:11 -0800 (PST) (envelope-from owner-freebsd-stable@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 XAA25376; Mon, 14 Dec 1998 23:32:09 -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 <55452(1)>; Mon, 14 Dec 1998 23:32:03 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Mon, 14 Dec 1998 22:19:11 -0800 To: Michael Robinson cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Tue, 15 Dec 98 05:40:42 PST." <199812151340.NAA07127@netrinsics.com> Date: Mon, 14 Dec 1998 22:17:03 PST From: Bill Fenner Message-Id: <98Dec14.221911pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hm. After looking into this a little further, I discovered that I've been running a slightly modified version of my original patch on my home 2.2.6 machine (running X and everything) for about 5 months and haven't noticed any of the problems that people were reporting. Would you mind trying this patch? Bill --- uipc_socket.c.orig Tue Jun 30 23:03:30 1998 +++ uipc_socket.c Sat Jul 18 12:32:26 1998 @@ -340,6 +340,7 @@ register long space, len, resid; int clen = 0, error, s, dontroute, mlen; int atomic = sosendallatonce(so) || top; + int small = 0; if (uio) resid = uio->uio_resid; @@ -443,6 +444,7 @@ mlen = MCLBYTES; len = min(min(mlen, resid), space); } else { + small = 1; nopages: len = min(min(mlen, resid), space); /* @@ -466,7 +468,7 @@ top->m_flags |= M_EOR; break; } - } while (space > 0 && atomic); + } while (space > 0 && (atomic || small)); if (dontroute) so->so_options |= SO_DONTROUTE; s = splnet(); /* XXX */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 15 00:06:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29181 for freebsd-stable-outgoing; Tue, 15 Dec 1998 00:06:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netrinsics.com ([210.74.179.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29162; Tue, 15 Dec 1998 00:06:17 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id QAA07493; Tue, 15 Dec 1998 16:03:03 GMT (envelope-from robinson) Date: Tue, 15 Dec 1998 16:03:03 GMT From: Michael Robinson Message-Id: <199812151603.QAA07493@netrinsics.com> To: fenner@parc.xerox.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <98Dec14.221911pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fenner writes: >Hm. After looking into this a little further, I discovered that I've >been running a slightly modified version of my original patch on my >home 2.2.6 machine (running X and everything) for about 5 months and >haven't noticed any of the problems that people were reporting. > >Would you mind trying this patch? I'll do that and get back to you. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 15 03:46:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16432 for freebsd-stable-outgoing; Tue, 15 Dec 1998 03:46:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netrinsics.com ([210.74.178.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16427; Tue, 15 Dec 1998 03:46:31 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id PAA07456; Tue, 15 Dec 1998 15:55:17 GMT (envelope-from robinson) Date: Tue, 15 Dec 1998 15:55:17 GMT From: Michael Robinson Message-Id: <199812151555.PAA07456@netrinsics.com> To: fenner@parc.xerox.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <199812150552.VAA17801@mango.parc.xerox.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fenner writes: >You misunderstand. The fix is to accumulate mbufs in a chain until either >a) The protocol gets all of the data that it wanted, or >b) All of the data that the user has provided has been copied into mbufs. > >(b) is what sosend() used to do. The URL referenced (the one with >"vanj88" in it) describes why sosend() was changed to use only a single >mbuf at a time, but this performance problem was not envisioned at >the time. Ok, I misunderstood. But I still disagree it's a bug. Or, more precisely, it would be a bug if the socket API and the TCP protocol were seen as one inseparable entity, which is not the case. There does not seem to me to be anything inherently broken at the socket abstraction layer with the practice of writing one "write" out to a streaming protocol in multiple packets. Nor does there seem to be anything inherently broken at the TCP abstraction layer with buffering streamed input until an ACK is received. Together, these performance optimizations at different levels of abstraction can interact badly, under a particular set of circumstances, but is that really a bug, per se? Having read the Van Jacobson argument for parallelism, though, I have to wonder how that relates to the current implementation of sosend in FreeBSD. It seems that we only get the "parallelism" if the write length is more than one mbuf and less than two. A write of two mbufs plus one byte is copied into a cluster, which gives you all the non-parallelism of the original "chain mbufs" solution, and all the memory inefficiency of cluster allocation. Is there any documentation on why MINCLSIZE is currently set to the value it is? -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 15 08:57:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19362 for freebsd-stable-outgoing; Tue, 15 Dec 1998 08:57:32 -0800 (PST) (envelope-from owner-freebsd-stable@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 IAA19346; Tue, 15 Dec 1998 08:57:31 -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 <55530(5)>; Tue, 15 Dec 1998 08:57:24 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177535>; Tue, 15 Dec 1998 08:57:14 -0800 To: Michael Robinson cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Tue, 15 Dec 98 07:55:17 PST." <199812151555.PAA07456@netrinsics.com> Date: Tue, 15 Dec 1998 08:42:29 PST From: Bill Fenner Message-Id: <98Dec15.085714pst.177535@crevenia.parc.xerox.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812151555.PAA07456@netrinsics.com> you write: >Together, these performance optimizations at different >levels of abstraction can interact badly, under a particular set of >circumstances, but is that really a bug, per se? Ok, it's a performance problem, which was introduced by a performance enhancement. Therefore, it's a bug in the original enhancement. =) >It seems that we only get the "parallelism" if the write length is more >than one mbuf and less than two. You get it also if it's more than the length of a cluster (and particularly multiples of the length of a cluster, e.g. a 64k write). >Is there any documentation on why MINCLSIZE is currently set to the value it >is? Not that I know of, but I can't say for sure that there's not something in the 4.4 daemon book. You know what the main tradeoff is of reducing MINCLSIZE (and there are some subtle ones too - set your socket buffer to 64k and start writing in 120-byte chunks and see when the socket buffer fills up). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 15 09:38:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25471 for freebsd-stable-outgoing; Tue, 15 Dec 1998 09:38:20 -0800 (PST) (envelope-from owner-freebsd-stable@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 JAA25465 for ; Tue, 15 Dec 1998 09:38:17 -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 JAA05237; Tue, 15 Dec 1998 09:38:12 -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 JAA16465; Tue, 15 Dec 1998 09:38:11 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 15 Dec 1998 09:38:11 -0800 (PST) Message-Id: <199812151738.JAA16465@vashon.polstra.com> To: krentel@dreamscape.com Subject: Re: file modes in CVS repository Newsgroups: polstra.freebsd.stable In-Reply-To: <199812130249.VAA10945@dreamscape.com> Organization: Polstra & Co., Seattle, WA Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199812130249.VAA10945@dreamscape.com>, Mark W. Krentel wrote: > > So, is that the policy in the repository that none of the ,v files > need special permission because something else will set them before > they're used? The policy, if there is one, is two-fold. Committers should take care to set the permissions right before they first import a script. Makefiles must be written to ensure that things will still work if the permissions are wrong in the repository. 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-stable" in the body of the message From owner-freebsd-stable Tue Dec 15 09:42:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA26104 for freebsd-stable-outgoing; Tue, 15 Dec 1998 09:42:48 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netrinsics.com ([202.99.61.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA26086; Tue, 15 Dec 1998 09:42:37 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: (from robinson@localhost) by netrinsics.com (8.8.8/8.8.7) id BAA02158; Wed, 16 Dec 1998 01:39:17 GMT (envelope-from robinson) Date: Wed, 16 Dec 1998 01:39:17 GMT From: Michael Robinson Message-Id: <199812160139.BAA02158@netrinsics.com> To: fenner@parc.xerox.com Subject: Re: MLEN < write length < MINCLSIZE "bug" Cc: freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG In-Reply-To: <98Dec15.085714pst.177535@crevenia.parc.xerox.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fenner writes: >>Is there any documentation on why MINCLSIZE is currently set to the value it >>is? > >Not that I know of, but I can't say for sure that there's not something >in the 4.4 daemon book. You know what the main tradeoff is of reducing >MINCLSIZE (and there are some subtle ones too - set your socket buffer >to 64k and start writing in 120-byte chunks and see when the socket >buffer fills up). Well, I just discovered another interesting effect of the smaller MINCLSIZE. After exhaustive testing with the standard X benchmarking utility (xmame), I've discovered a significant performance improvement for graphics- intensive X applications. -Michael Robinson P.S. It may be a while before I get around to testing your "short" patch ;-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 15 10:04:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28850 for freebsd-stable-outgoing; Tue, 15 Dec 1998 10:04:03 -0800 (PST) (envelope-from owner-freebsd-stable@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 KAA28831; Tue, 15 Dec 1998 10:04:01 -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 <55775(1)>; Tue, 15 Dec 1998 10:03:55 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Tue, 15 Dec 1998 10:03:38 -0800 To: Michael Robinson cc: fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-reply-to: Your message of "Tue, 15 Dec 98 17:39:17 PST." <199812160139.BAA02158@netrinsics.com> Date: Tue, 15 Dec 1998 10:03:36 PST From: Bill Fenner Message-Id: <98Dec15.100338pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812160139.BAA02158@netrinsics.com> you write: >After exhaustive testing with the standard X benchmarking utility (xmame), >I've discovered a significant performance improvement for graphics- >intensive X applications. I'm not surprised -- since the "atomic" patch confused X, it was clear that X was in this range of small writes. I think that X sets TCP_NODELAY so it shouldn't be subject to the extra round trip in this case, but it still ends up being less packets. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 15 16:27:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22634 for freebsd-stable-outgoing; Tue, 15 Dec 1998 16:27:21 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22626 for ; Tue, 15 Dec 1998 16:27:19 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id TAA22764; Tue, 15 Dec 1998 19:26:58 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: John Polstra cc: krentel@dreamscape.com, stable@FreeBSD.ORG From: "Gary Palmer" Subject: Re: file modes in CVS repository In-reply-to: Your message of "Tue, 15 Dec 1998 09:38:11 PST." <199812151738.JAA16465@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 15 Dec 1998 19:26:57 -0500 Message-ID: <22760.913768017@gjp.erols.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote in message ID <199812151738.JAA16465@vashon.polstra.com>: > The policy, if there is one, is two-fold. Committers should take > care to set the permissions right before they first import a script. > Makefiles must be written to ensure that things will still work if > the permissions are wrong in the repository. I think the FreeBSD project also cheats to a certain extent that we have clean-up scripts that run periodically out of cron and run a find across the repository and ``tidy up'' any bogus permissions. I dunno if they are still in place, but they were the last time I looked (many moons ago) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 15 16:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23177 for freebsd-stable-outgoing; Tue, 15 Dec 1998 16:31:10 -0800 (PST) (envelope-from owner-freebsd-stable@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 QAA23163; Tue, 15 Dec 1998 16:31:05 -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 QAA07325; Tue, 15 Dec 1998 16:30:56 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id QAA17827; Tue, 15 Dec 1998 16:30:55 -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: <22760.913768017@gjp.erols.com> Date: Tue, 15 Dec 1998 16:30:54 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Gary Palmer Subject: Re: file modes in CVS repository Cc: stable@FreeBSD.ORG, krentel@dreamscape.com Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> The policy, if there is one, is two-fold. Committers should take >> care to set the permissions right before they first import a >> script. Makefiles must be written to ensure that things will still >> work if the permissions are wrong in the repository. > > I think the FreeBSD project also cheats to a certain extent that we > have clean-up scripts that run periodically out of cron and run a > find across the repository and ``tidy up'' any bogus permissions. I > dunno if they are still in place, but they were the last time I > looked (many moons ago) That's true, but I think you're missing some context. The original question concerned shell scripts, and whether the execute bits should be set in the repository files. The clean-up script doesn't mess with that. It just makes sure all the files are readable by everybody. 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-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 03:00:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23911 for freebsd-stable-outgoing; Wed, 16 Dec 1998 03:00:56 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from buffy.tpgi.com.au (buffy.tpgi.com.au [203.12.160.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23905 for ; Wed, 16 Dec 1998 03:00:53 -0800 (PST) (envelope-from eirvine@tpgi.com.au) Received: (from smtpd@localhost) by buffy.tpgi.com.au (8.8.7/8.8.7) id WAA29946 for ; Wed, 16 Dec 1998 22:04:03 +1100 Received: from tar-ppp-162.tpgi.com.au(203.26.26.162), claiming to be "tpgi.com.au" via SMTP by buffy.tpgi.com.au, id smtpda29857; Wed Dec 16 22:03:57 1998 Message-ID: <36779309.95D27CCD@tpgi.com.au> Date: Wed, 16 Dec 1998 22:01:29 +1100 From: Eddie Irvine X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: "stable@FreeBSD.ORG" Subject: wd devices >9Gb in size. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, freeBSD is going so well I got a second hard disk. It was advertised as 10 Gb. I had a fool round with it this morning and fdisk is giving me error messages I don't understand yet. Anyhow, I recall something about FreeBSD STABLE not coping with HDD bigger than 8 Gb. Is this still the case? I have the 3.0 disks, but I wanted to put off the full upgrade 'till I'd initialised this second HDD and made a backup to it. More detailed error messages can follow... (Not at work right now!) TIA Eddie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 03:15:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25580 for freebsd-stable-outgoing; Wed, 16 Dec 1998 03:15:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netshell.vicosa.com.br (netshell.vicosa.com.br [200.236.148.170]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA25575 for ; Wed, 16 Dec 1998 03:15:35 -0800 (PST) (envelope-from grios@netshell.vicosa.com.br) Received: (qmail 3293 invoked by uid 1070); 16 Dec 1998 11:25:05 -0000 Date: Wed, 16 Dec 1998 09:25:05 -0200 (EDT) From: Gustavo Vieira Goncalves Coelho Rios To: Eddie Irvine cc: "stable@FreeBSD.ORG" Subject: Re: wd devices >9Gb in size. In-Reply-To: <36779309.95D27CCD@tpgi.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where can i get a compatible hardware list to FreeBSD stabe? thanks. --- I use UNIX because reboots are for hardware upgrades. You use windowze because the guy on TV told you to ... ----- Gustavo Rios ----- On Wed, 16 Dec 1998, Eddie Irvine wrote: > Hi all, > > freeBSD is going so well I got a second hard disk. It was advertised > as 10 Gb. I had a fool round with it this morning and fdisk is giving > me error messages I don't understand yet. Anyhow, I recall something > about FreeBSD STABLE not coping with HDD bigger than 8 Gb. > > Is this still the case? I have the 3.0 disks, but I wanted to put off > the full upgrade 'till I'd initialised this second HDD and made a > backup to it. > > More detailed error messages can follow... (Not at work right now!) > > TIA > Eddie. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 03:22:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA26147 for freebsd-stable-outgoing; Wed, 16 Dec 1998 03:22:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cinnamon.michvhf.com (cinnamon.michvhf.com [209.57.60.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA26142 for ; Wed, 16 Dec 1998 03:22:10 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 29049 invoked from network); 16 Dec 1998 11:21:52 -0000 Received: from cinnamon.michvhf.com (209.57.60.10) by cinnamon.michvhf.com with SMTP; 16 Dec 1998 11:21:52 -0000 Date: Wed, 16 Dec 1998 06:21:51 -0500 (EST) From: Vince Vielhaber To: Eddie Irvine cc: "stable@FreeBSD.ORG" Subject: Re: wd devices >9Gb in size. In-Reply-To: <36779309.95D27CCD@tpgi.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Dec 1998, Eddie Irvine wrote: > freeBSD is going so well I got a second hard disk. It was advertised > as 10 Gb. I had a fool round with it this morning and fdisk is giving > me error messages I don't understand yet. Anyhow, I recall something > about FreeBSD STABLE not coping with HDD bigger than 8 Gb. > > Is this still the case? I have the 3.0 disks, but I wanted to put off > the full upgrade 'till I'd initialised this second HDD and made a > backup to it. IIRC, This was supposed to be fixed in 2.2.8 so stable should be ok. I know it's not fixed in 2.2.7. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 04:10:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA02742 for freebsd-stable-outgoing; Wed, 16 Dec 1998 04:10:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vega.pfts.com (vega.pfts.com [193.193.196.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA02734 for ; Wed, 16 Dec 1998 04:10:08 -0800 (PST) (envelope-from max@vega.pfts.com) Received: from vega.pfts.com (big_brother [192.168.1.1]) by vega.pfts.com (8.9.1/8.8.8) with ESMTP id OAA19647; Wed, 16 Dec 1998 14:12:54 +0200 (EET) (envelope-from max@vega.pfts.com) Message-ID: <3677A297.67D271EA@vega.pfts.com> Date: Wed, 16 Dec 1998 14:07:52 +0200 From: Maxim Sobolev X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: Gustavo Vieira Goncalves Coelho Rios CC: Eddie Irvine , "stable@FreeBSD.ORG" Subject: Re: wd devices >9Gb in size. References: Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check FreeBSD handbook and FreeBSD faq on www.freebsd.org to get it. Max Gustavo Vieira Goncalves Coelho Rios wrote: > Where can i get a compatible hardware list to FreeBSD stabe? > thanks. > > --- > I use UNIX because reboots are for hardware upgrades. > You use windowze because the guy on TV told you to ... > ----- Gustavo Rios ----- > > On Wed, 16 Dec 1998, Eddie Irvine wrote: > > > Hi all, > > > > freeBSD is going so well I got a second hard disk. It was advertised > > as 10 Gb. I had a fool round with it this morning and fdisk is giving > > me error messages I don't understand yet. Anyhow, I recall something > > about FreeBSD STABLE not coping with HDD bigger than 8 Gb. > > > > Is this still the case? I have the 3.0 disks, but I wanted to put off > > the full upgrade 'till I'd initialised this second HDD and made a > > backup to it. > > > > More detailed error messages can follow... (Not at work right now!) > > > > TIA > > Eddie. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 04:46:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA07710 for freebsd-stable-outgoing; Wed, 16 Dec 1998 04:46:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ibm.net. (slip166-72-224-31.pa.us.ibm.net [166.72.224.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA07704 for ; Wed, 16 Dec 1998 04:46:34 -0800 (PST) (envelope-from placej@ibm.net) Received: (from placej@localhost) by ibm.net. (8.8.8/8.8.8) id HAA00695; Wed, 16 Dec 1998 07:45:45 -0500 (EST) (envelope-from placej) Message-ID: <19981216074545.A687@ka3tis.com> Date: Wed, 16 Dec 1998 07:45:45 -0500 From: "John C. Place" To: Eddie Irvine , "stable@FreeBSD.ORG" Subject: Re: wd devices >9Gb in size. Reply-To: "John C. Place" Mail-Followup-To: Eddie Irvine , "stable@FreeBSD.ORG" References: <36779309.95D27CCD@tpgi.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <36779309.95D27CCD@tpgi.com.au>; from Eddie Irvine on Wed, Dec 16, 1998 at 10:01:29PM +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 16, 1998 at 10:01:29PM +1100, Eddie Irvine wrote: > freeBSD is going so well I got a second hard disk. It was advertised > as 10 Gb. I had a fool round with it this morning and fdisk is giving > me error messages I don't understand yet. Anyhow, I recall something > about FreeBSD STABLE not coping with HDD bigger than 8 Gb. > Check the release notes at: http://www.freebsd.org/releases/2.2.8R/notes.html Good Luck John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 05:00:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09280 for freebsd-stable-outgoing; Wed, 16 Dec 1998 05:00:46 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA09270 for ; Wed, 16 Dec 1998 05:00:37 -0800 (PST) (envelope-from root@ice.cold.org) Received: (from root@localhost) by ice.cold.org (8.8.8/8.8.5) id GAA11758; Wed, 16 Dec 1998 06:00:28 -0700 (MST) Date: Wed, 16 Dec 1998 06:00:28 -0700 (MST) Message-Id: <199812161300.GAA11758@ice.cold.org> Subject: ERRATA NOTICE: FreeBSD 2.2.8-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 2.2.8-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.8-RELEASE/ERRATA.TXT The last update was sent: Mon Nov 30 00:14:08 1998 This update is sent: Wed Dec 16 06:00:27 1998 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: o /usr/sbin/sysctl is an invalid link. Fix: sysctl(8) has actually moved to /sbin/sysctl. Simply remove /usr/sbin/sysctl as it was included accidently in the bin distribution and is not necessary. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 06:27:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA19757 for freebsd-stable-outgoing; Wed, 16 Dec 1998 06:27:14 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA19726; Wed, 16 Dec 1998 06:26:57 -0800 (PST) (envelope-from fanf@demon.net) Received: by server.noc.demon.net; id OAA02221; Wed, 16 Dec 1998 14:26:48 GMT Received: from fanf.noc.demon.net(195.11.55.83) by inside.noc.demon.net via smap (3.2) id xma002206; Wed, 16 Dec 98 14:26:35 GMT Received: from fanf by fanf.noc.demon.net with local (Exim 1.73 #2) id 0zqHzA-0000Le-00; Wed, 16 Dec 1998 14:31:32 +0000 To: robinson@netrinsics.com, fenner@parc.xerox.com, freebsd-net@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG From: Tony Finch Subject: Re: MLEN < write length < MINCLSIZE "bug" Newsgroups: chiark.mail.freebsd.net In-Reply-To: Organization: Deliberate Obfuscation To Amuse Tony References: <199812151555.PAA07456@netrinsics.com> Message-Id: Date: Wed, 16 Dec 1998 14:31:32 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fenner wrote: >In message <199812151555.PAA07456@netrinsics.com> you write: >> >>Is there any documentation on why MINCLSIZE is currently set to the value it >>is? > >Not that I know of, but I can't say for sure that there's not something >in the 4.4 daemon book. Having read this bit of the red demon book recently (although I can't find the precise reference again at the moment), ISTR that the heuristic is that since allocating an mbuf with a cluster takes two allocations, MINCLSIZE is just bigger than two mbufs. Tony. -- f.a.n.finch**waster dot@dotat.at fanf@demon.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 07:45:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA29308 for freebsd-stable-outgoing; Wed, 16 Dec 1998 07:45:55 -0800 (PST) (envelope-from owner-freebsd-stable@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 HAA29289; Wed, 16 Dec 1998 07:45:51 -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 QAA13332; Wed, 16 Dec 1998 16:45:19 +0100 (CET) (envelope-from des) To: spork Cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: CAM and -stable References: From: Dag-Erling Smorgrav Date: 16 Dec 1998 16:45:18 +0100 In-Reply-To: spork's message of "Mon, 14 Dec 1998 18:56:03 -0500 (EST)" Message-ID: Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG spork writes: > > /* Added to fix CRD-5440's lack of tags */ It's not lack of tags that's the problem (64 is pretty good), but the fact that the firmware (incorrectly) reports that it's out of queue slots when things get busy. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 16:45:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10597 for freebsd-stable-outgoing; Wed, 16 Dec 1998 16:45:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from netshell.vicosa.com.br (netshell.vicosa.com.br [200.236.148.170]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA10587 for ; Wed, 16 Dec 1998 16:45:20 -0800 (PST) (envelope-from grios@netshell.vicosa.com.br) Received: (qmail 9139 invoked by uid 1070); 17 Dec 1998 00:55:15 -0000 Date: Wed, 16 Dec 1998 22:55:15 -0200 (EDT) From: Gustavo Vieira Goncalves Coelho Rios To: FreeBSD Stable , FreeBSD Subject: original make that came with 2.2.7 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hy everybody. I recentily installed FreeBSD 2.2.7. So make util were installed too. But as the original make that came with BSD 2.2.7 did not support "make -C "i decide to install GNU Make 3.77, so the hell came to me. Everything were working well, until the moment that i need to compile my kernel. with this new make (GNU Make 3.77) i cannot compile my kernel, what's is going on? Is not there any pattern on make development? My error mesg with GNU Make 3.77 is: Makefile: line 28: **** missing separator***** The old make worked very well, what is going on? Why Gnu Make 3.77 does understand My kernel Makefile. I tried the same with GENERIC config kernel, and the error ocurred. Can any body help me? Thank you for your time and cooperation. best regards. --- I use UNIX because reboots are for hardware upgrades. You use windowze because the guy on TV told you to ... ----- Gustavo Rios ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 17:19:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13914 for freebsd-stable-outgoing; Wed, 16 Dec 1998 17:19:48 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mimu.msdj.com (msdj11.msdj.com [210.160.169.45] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA13898 for ; Wed, 16 Dec 1998 17:19:38 -0800 (PST) (envelope-from mimu@msdj.com) Received: from localhost (localhost.msdj.com [127.0.0.1]) by mimu.msdj.com (8.8.8/3.4Wbeta6) with ESMTP id KAA02723 for ; Thu, 17 Dec 1998 10:19:59 +0900 (JST) To: freebsd-stable@FreeBSD.ORG Subject: Re: original make that came with 2.2.7 From: Shigeki Mimura In-Reply-To: Your message of "Wed, 16 Dec 1998 22:55:15 -0200 (EDT)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981217101958D.mimu@msdj.com> Date: Thu, 17 Dec 1998 10:19:58 +0900 X-Dispatcher: imput version 980522 Lines: 12 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It cannot make kernel with gnu-make. You have to use original make. I think better way solved your problem is you install gnu make from ports/packages. thank you. ##################################### ## Shigeki Mimura ## ## MSD-JAPAN Inc. ## ## E-mail:mimu@msdj.com ## ##################################### To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 17:25:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14275 for freebsd-stable-outgoing; Wed, 16 Dec 1998 17:25:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pav (pm40s44.intergate.bc.ca [207.194.175.253]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA14270 for ; Wed, 16 Dec 1998 17:25:04 -0800 (PST) (envelope-from promoteit@netscape.net) Date: Wed, 16 Dec 1998 17:25:04 -0800 (PST) From: Promote-It! To: Message-Id: <419.436145.71539560promoteit@netscape.net> Subject: Your website appeared in What's New on Yahoo! this week. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CONGRATULATIONS! Your website appeared in What's New on Yahoo! (or What's New Too) this week and will be added to the main Yahoo database in a few days! ************************************************** The Stakes Are Simply Too High To Leave Your Web Success To Chance!!! It is critical that the right people see your website. Simply designing a good site does not guarantee that it will attract visitors. The "if you build, they will come" premise is not true when conducting business on the Internet. So how do you entice prospective customers to your site? We deliver innovative, traffic-building programs that will get your website in front of the audience you want to reach. --->Search Engine Tune-Up! We create "KILLER" Meta Tags for your website. Watch your hit count soar when your site is listed in a top position with Alta Vista, AOL Netfind, Excite, Hotbot, Infoseek, Lycos, WebCrawler, and Yahoo! --->Promote-It! We submit your site to 459 awards sites, business publications, directories, ezines, search engines, what's new pages, yellow pages, and more! This will be done manually, by a real a real person, not by software that can fail! --->Customer-Direct! Using your keywords and description we create 5 "Spider Mirror Sites" and register them in all the major search engines to drive targeted visitors to your site. ************************************************** Please visit our website for more information! Promote-It! http://www.interweb-connections.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 17:55:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17122 for freebsd-stable-outgoing; Wed, 16 Dec 1998 17:55:15 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA17111 for ; Wed, 16 Dec 1998 17:55:12 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zqSeG-00079p-00; Wed, 16 Dec 1998 17:54:40 -0800 Date: Wed, 16 Dec 1998 17:54:37 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mike Smith cc: Michael Robinson , freebsd-stable@FreeBSD.ORG Subject: Re: MLEN < write length < MINCLSIZE "bug" In-Reply-To: <199812150437.UAA02728@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 14 Dec 1998, Mike Smith wrote: > > Will do. Will patches against the 2.2.7-RELEASE CVS repository be acceptable? > > If there hasn't been too much drift, they should easily merge into -STABLE, > > and maybe even -CURRENT. > > I'd really prefer diffs against -current; that's where this would be > committed. I don't know about that. This is being discussed on the freebsd-stable list. And, all known bug fixes should go to -stable too. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 20:01:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29229 for freebsd-stable-outgoing; Wed, 16 Dec 1998 20:01:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29222 for ; Wed, 16 Dec 1998 20:01:29 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id PAA02593; Thu, 17 Dec 1998 15:01:21 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma002121; Thu, 17 Dec 98 14:58:15 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id OAA06644 for ; Thu, 17 Dec 1998 14:58:15 +1100 From: "John Saunders" To: Subject: RE: ERRATA NOTICE: FreeBSD 2.2.8-RELEASE Date: Thu, 17 Dec 1998 14:58:15 +1100 Message-ID: <002501be2971$790422b0$6cb611cb@saruman.scitec.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199812161300.GAA11758@ice.cold.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I thought the link was necessary because the whereis program references it at the old place. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of > freebsd-errata-update@roguetrader.com > Sent: Thursday, 17 December 1998 0:00 > To: freebsd-stable@FreeBSD.ORG > Subject: ERRATA NOTICE: FreeBSD 2.2.8-RELEASE > > > > ****************************************************************** > ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 2.2.8-RELEASE ** > ****************************************************************** > > You can retrieve the complete ERRATA from: > > ftp://ftp.freebsd.org/pub/FreeBSD/2.2.8-RELEASE/ERRATA.TXT > > The last update was sent: Mon Nov 30 00:14:08 1998 > This update is sent: Wed Dec 16 06:00:27 1998 > > ------------------------------------------------------------------ > ---- SYSTEM ERRATA INFORMATION: > > o /usr/sbin/sysctl is an invalid link. > > Fix: sysctl(8) has actually moved to /sbin/sysctl. Simply remove > /usr/sbin/sysctl as it was included accidently in the > bin distribution and is not necessary. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 16 21:22:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06241 for freebsd-stable-outgoing; Wed, 16 Dec 1998 21:22:11 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06215; Wed, 16 Dec 1998 21:22:06 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.8.8/8.8.8) id AAA15437; Thu, 17 Dec 1998 00:22:14 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199812170522.AAA15437@cc942873-a.ewndsr1.nj.home.com> Subject: Re: original make that came with 2.2.7 In-Reply-To: from Gustavo Vieira Goncalves Coelho Rios at "Dec 16, 98 10:55:15 pm" To: grios@netshell.vicosa.com.br (Gustavo Vieira Goncalves Coelho Rios) Date: Thu, 17 Dec 1998 00:22:14 -0500 (EST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Reply-To: cjclark@home.com 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Did you install the GNU make over the 'old' make? Typically, GNU make is called 'gmake' so that both can be retained. Clobbering the OS packaged 'make' with 'gmake' seems something akin to covering 'cc' with 'gcc.' The FreeBSD supplied 'make' lives in /usr/bin/make. Is that where you put your GNU make? Over that? Or is the new one in /usr/local/bin? Whatever happens, I would suggest getting the orignial 'make' to build the kernel. You should be able to get one by just copying the binary from somewhere. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 09:22:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21453 for freebsd-stable-outgoing; Thu, 17 Dec 1998 09:22:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21447; Thu, 17 Dec 1998 09:22:53 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 0zqh8M-0001qn-00; Thu, 17 Dec 1998 19:22:42 +0200 From: Sheldon Hearn To: jkh@FreeBSD.ORG cc: stable@FreeBSD.ORG Subject: re: cvs commit: src/usr.bin/whereis whereis.pl Date: Thu, 17 Dec 1998 19:22:42 +0200 Message-ID: <7116.913915362@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jordan, > Modified files: (Branch: RELENG_2_2) > usr.bin/whereis whereis.pl > Log: > Urk. Look for sysctl in correct location. So this means it's safe to blow away the symbolic link in /usr/sbin, or am I being clueless? Or isn't that a binary question? ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 09:28:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21824 for freebsd-stable-outgoing; Thu, 17 Dec 1998 09:28:23 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21819 for ; Thu, 17 Dec 1998 09:28:22 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id MAA27111 for ; Thu, 17 Dec 1998 12:28:14 -0500 (EST) Date: Thu, 17 Dec 1998 12:28:14 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-stable@FreeBSD.ORG Subject: ATTN: 2.1.7 users Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a heads-up for anyone still using this... The newest nmap (port-scanning utility) will nuke your inetd process out of existence. No log entries nothing, it all just quietly goes away. Just an FYI... Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 11:31:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05111 for freebsd-stable-outgoing; Thu, 17 Dec 1998 11:31:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from joe.newsguy.com (linda.pathlink.com [205.185.79.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05105 for ; Thu, 17 Dec 1998 11:31:39 -0800 (PST) (envelope-from kachun@pathlink.com) Received: from dvl-1 (dvl-1.pathlink.com [207.211.168.211]) by joe.newsguy.com (8.8.7/8.8.5) with SMTP id LAA17372 for ; Thu, 17 Dec 1998 11:31:31 -0800 (PST) Message-Id: <199812171931.LAA17372@joe.newsguy.com> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Thu, 17 Dec 1998 11:31:23 -0800 To: freebsd-stable@FreeBSD.ORG From: Kachun Lee Subject: biodone panic? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I upgraded one of our servers from 2.2.5-STABLE to 2.2.7-STABLE. The cvsup was several days before 2.2.8-RELEASE... -------------- Dec 6 18:21:36 lex /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Dec 6 18:21:36 lex /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Dec 6 18:21:36 lex /kernel: The Regents of the University of California. All r ights reserved. Dec 6 18:21:36 lex /kernel: Dec 6 18:21:36 lex /kernel: FreeBSD 2.2.7-STABLE #0: Wed Nov 25 17:14:50 PST 19 98 Dec 6 18:21:36 lex /kernel: root@lex.pathlink.com:/n/src.bsd.2.2-releng/src/sys /compile/CLARK Dec 6 18:21:36 lex /kernel: CPU: Pentium II (quarter-micron) (400.91-MHz 686-cl ass CPU) Dec 6 18:21:36 lex /kernel: Origin = "GenuineIntel" Id = 0x652 Stepping=2 Dec 6 18:21:36 lex /kernel: Features=0x183fbff,,MMX,> Dec 6 18:21:36 lex /kernel: real memory = 536870912 (524288K bytes) Dec 6 18:21:36 lex /kernel: avail memory = 524570624 (512276K bytes) -------------- It has been panic'ing every several days with 'biodone not busy'... -------------- biodone: buffer alreaiodone: buffer already done biodone: buffer already done biodone: buffer already done biodone: buffer already done biodone: buffer already done panic: biodone: buffer not busy syncing disks... panic: biodone: buffer not busy Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... -------------- Is there a chance that this was addressed in latest 2.2.8-STABLE? Any suggestion will be greatly appreciated. Best regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 15:24:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03611 for freebsd-stable-outgoing; Thu, 17 Dec 1998 15:24:48 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03604 for ; Thu, 17 Dec 1998 15:24:46 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id VAA12455 for stable@freebsd.org; Thu, 17 Dec 1998 21:24:38 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199812172324.VAA12455@roma.coe.ufrj.br> Subject: Funny bug in file(1)... To: stable@FreeBSD.ORG Date: Thu, 17 Dec 1998 21:24:38 -0200 (EDT) 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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From Corel Wordperfect 8 for Linux: roma::jonny [627] file Readme Readme: Alpha Digital UNIX core file, generated from 'wnload Instructions' roma::jonny [628] head Readme Corel WordPerfect FTP Download Instructions This file has been written to document the steps required to install the FTP downloaded version of Corel WordPerfect. 1) Download the file(s) from the web into an empty directory. 2) Unzip each downloaded file(s). 3) Untar each downloaded file(s) (tar xf ). 4) Run the newly created Runme script. roma::jonny [629] ROTFL... :) Jonny -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 15:39:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05007 for freebsd-stable-outgoing; Thu, 17 Dec 1998 15:39:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from enterprise.cs.unm.edu (enterprise.cs.unm.edu [198.59.151.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA05001 for ; Thu, 17 Dec 1998 15:38:59 -0800 (PST) (envelope-from colinj@cs.unm.edu) Received: from viper.cs.unm.edu [198.59.151.25] by enterprise.cs.unm.edu with smtp (Exim 1.80 #2) id 0zqn0N-0004i0-00; Thu, 17 Dec 1998 16:38:51 -0700 Date: Thu, 17 Dec 1998 16:40:01 -0700 (MST) From: Colin Eric Johnson To: freebsd-stable@FreeBSD.ORG Subject: going from 2.2.8 to 3.0, when? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So here I am inbetween semesters and I'm think that this is an excellent time to do an upgrade. So now my question is, what's the planned date for the -STABLE branch to working on the 3.x code? Should I run with it now? Colin E. Johnson | colinj@unm.edu | http://www.unm.edu/~colinj/ busily trying to figure out how to get a Players Club card . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 16:10:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10464 for freebsd-stable-outgoing; Thu, 17 Dec 1998 16:10:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from enterprise.cs.unm.edu (enterprise.cs.unm.edu [198.59.151.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA10451 for ; Thu, 17 Dec 1998 16:10:18 -0800 (PST) (envelope-from cfaehl@cs.unm.edu) Received: from avarice.cs.unm.edu [198.59.151.252] by enterprise.cs.unm.edu with esmtp (Exim 1.80 #2) id 0zqnUe-00051b-00; Thu, 17 Dec 1998 17:10:08 -0700 X-Mailer: exmh version 2.0.2 2/24/98 To: Colin Eric Johnson cc: freebsd-stable@FreeBSD.ORG Subject: Re: going from 2.2.8 to 3.0, when? In-Reply-To: Message from Colin Eric Johnson of "Thu, 17 Dec 1998 16:40:01 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 17:10:11 -0700 From: "Chris D. Faehl" Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So here I am inbetween semesters and I'm think that this is an excellent > time to do an upgrade. So now my question is, what's the planned date for > the -STABLE branch to working on the 3.x code? Should I run with it now? > Don't do it, don't do it, don't try suicide... Sorry, my latent 70's Queen fetish got the best of me for a moment. I took a 2.2.8 box to 3.0 recently. My experience: fraught with pit traps, only for the very cautious and FreeBSD-aware, and still some strange problems. For now, I'd say best to reinstall from floppies. I'll elaborate on some of my problems for the Good Of All. I'd love correction and elucidation. a) cvsup/make buildworld/make installworld worked okay. b) rebuilding a kernel (with appropriate references to new CAM devices) worked okay. c) updated /etc okay, merged my changes with dist changes okay. d) made the new devices for the da? devices okay. e) rebooting couldn't quite get it's act together after that make installworld. "Bad System Call". Okay, I figured something like that might happen. Cold booted, and 3.0-current fsck'd just fine, booted into multi-user without issue. f) some ports broke. In particular, acroread didn't work (probs with a.out libraries and the linux emulator is my best guess). g) After a 'make aout-to-elf', I couldn't login on the console any longer - always "Login incorrect". But I could get in fine via ssh (I had built as a port before I took to elf). h) At that point, Jon wanted his box back ;). > Colin E. Johnson | colinj@unm.edu | http://www.unm.edu/~colinj/ > busily trying to figure out how to get a Players Club card . . . > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > ------------------------------------------------------------------------------- Chris Faehl | Email: cfaehl@cs.unm.edu The University of New Mexico | URL: http://www.cs.unm.edu/~cfaehl Computer Science Dept., Rm. FEC 313 | Phone: 505/277-3016 Albuquerque, NM 87131 USA | FAX: 505/277-6927 ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 16:17:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11818 for freebsd-stable-outgoing; Thu, 17 Dec 1998 16:17:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from enterprise.cs.unm.edu (enterprise.cs.unm.edu [198.59.151.20]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA11812 for ; Thu, 17 Dec 1998 16:17:55 -0800 (PST) (envelope-from colinj@cs.unm.edu) Received: from viper.cs.unm.edu [198.59.151.25] by enterprise.cs.unm.edu with smtp (Exim 1.80 #2) id 0zqnc3-00055S-00; Thu, 17 Dec 1998 17:17:47 -0700 Date: Thu, 17 Dec 1998 17:18:58 -0700 (MST) From: Colin Eric Johnson To: "Chris D. Faehl" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: going from 2.2.8 to 3.0, when? In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually I was planning on doing a fresh install of 3.0. I wasn't going to try and cvsup the 3.0 source. I can just as easily do the clean reinstall. On Thu, 17 Dec 1998, Chris D. Faehl wrote: > > So here I am inbetween semesters and I'm think that this is an excellent > > time to do an upgrade. So now my question is, what's the planned date for > > the -STABLE branch to working on the 3.x code? Should I run with it now? > > > > Don't do it, don't do it, don't try suicide... > > Sorry, my latent 70's Queen fetish got the best of me for a moment. > > I took a 2.2.8 box to 3.0 recently. My experience: fraught with pit traps, > only for the very cautious and FreeBSD-aware, and still some strange > problems. For now, I'd say best to reinstall from floppies. I'll > elaborate on some of my problems for the Good Of All. I'd love correction > and elucidation. > > a) cvsup/make buildworld/make installworld worked okay. > b) rebuilding a kernel (with appropriate references to new CAM devices) > worked okay. > c) updated /etc okay, merged my changes with dist changes okay. > d) made the new devices for the da? devices okay. > e) rebooting couldn't quite get it's act together after that make installworld. > "Bad System Call". Okay, I figured something like that might happen. > Cold booted, and 3.0-current fsck'd just fine, booted into multi-user > without issue. > f) some ports broke. In particular, acroread didn't work (probs with a.out > libraries and the linux emulator is my best guess). > g) After a 'make aout-to-elf', I couldn't login on the console any longer - > always "Login incorrect". But I could get in fine via ssh (I had > built as a port before I took to elf). > h) At that point, Jon wanted his box back ;). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 17:00:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16159 for freebsd-stable-outgoing; Thu, 17 Dec 1998 17:00:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16152 for ; Thu, 17 Dec 1998 17:00:34 -0800 (PST) (envelope-from root@ice.cold.org) Received: (from root@localhost) by ice.cold.org (8.8.8/8.8.5) id SAA23512; Thu, 17 Dec 1998 18:00:18 -0700 (MST) Date: Thu, 17 Dec 1998 18:00:18 -0700 (MST) Message-Id: <199812180100.SAA23512@ice.cold.org> Subject: ERRATA NOTICE: FreeBSD 2.2.8-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 2.2.8-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/2.2.8-RELEASE/ERRATA.TXT The last update was sent: Wed Dec 16 05:54:21 1998 This update is sent: Thu Dec 17 18:00:18 1998 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: o /usr/sbin/sysctl is an invalid link and whereis(1) doesn't work. Fix: sysctl(8) has actually moved to /sbin/sysctl. Simply create a symbolic link for compatability purposes as follows: ln -sf /sbin/sysctl /usr/sbin or syncronize your sources with 2.2-stable and rebuild/install from /usr/src/usr.sbin/whereis/ and just rm /usr/sbin/sysctl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 17:04:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16571 for freebsd-stable-outgoing; Thu, 17 Dec 1998 17:04:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.206.244]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16544 for ; Thu, 17 Dec 1998 17:04:47 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from backup.zippynet.iol.net.au (backup.zippynet.iol.net.au [172.22.2.4]) by backup.af.speednet.com.au (8.9.1/8.9.1) with ESMTP id MAA10875; Fri, 18 Dec 1998 12:03:52 +1100 (EST) Date: Fri, 18 Dec 1998 12:03:52 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.zippynet.iol.net.au To: "Chris D. Faehl" cc: Colin Eric Johnson , freebsd-stable@FreeBSD.ORG Subject: Re: going from 2.2.8 to 3.0, when? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998, Chris D. Faehl wrote: > ... I'll > elaborate on some of my problems for the Good Of All. I'd love correction > and elucidation. [snip] > h) At that point, Jon wanted his box back ;). Tell him "No! Fsck off!!" :-) > ------------------------------------------------------------------------------- > Chris Faehl | Email: cfaehl@cs.unm.edu > The University of New Mexico | URL: http://www.cs.unm.edu/~cfaehl > Computer Science Dept., Rm. FEC 313 | Phone: 505/277-3016 > Albuquerque, NM 87131 USA | FAX: 505/277-6927 > ------------------------------------------------------------------------------- > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speed Internet Services http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 19:55:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09293 for freebsd-stable-outgoing; Thu, 17 Dec 1998 19:55:44 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from n4hhe.ampr.org (tnt3-95.HiWAAY.net [208.147.146.95]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09283 for ; Thu, 17 Dec 1998 19:55:40 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by n4hhe.ampr.org (8.9.1/8.9.1) with ESMTP id VAA06221; Thu, 17 Dec 1998 21:16:39 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199812180316.VAA06221@n4hhe.ampr.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Chris D. Faehl" cc: Colin Eric Johnson , freebsd-stable@FreeBSD.ORG From: David Kelly Subject: Re: going from 2.2.8 to 3.0, when? In-reply-to: Message from "Chris D. Faehl" of "Thu, 17 Dec 1998 17:10:11 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Dec 1998 21:16:37 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chris D. Faehl" writes: > > So here I am inbetween semesters and I'm think that this is an excellent > > time to do an upgrade. So now my question is, what's the planned date for > > the -STABLE branch to working on the 3.x code? Should I run with it now? > > > > Don't do it, don't do it, don't try suicide... > > Sorry, my latent 70's Queen fetish got the best of me for a moment. I changed over to 3.0-current about 6 weeks ago. Have "make world"'ed once since then. System was got funky about the 3rd week in November with a new kernel. Used cvs to checkout /usr/src/sys from November 9 and restored proper behaviour. Am running a Dec 9 kernel now with only one problem with an Archive Anaconda tape drive (doesn't work). My DDS-2 tape drive works perfectly. Between semesters sounds like a perfect time to try 3.0. Be sure you have a good backup first. As always, YMMV. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 17 19:59:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09630 for freebsd-stable-outgoing; Thu, 17 Dec 1998 19:59:10 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from jason02.u.washington.edu (jason02.u.washington.edu [140.142.76.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA09621 for ; Thu, 17 Dec 1998 19:59:06 -0800 (PST) (envelope-from jcwells@u.washington.edu) Received: from saul6.u.washington.edu (root@saul6.u.washington.edu [140.142.82.1]) by jason02.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA35728; Thu, 17 Dec 1998 19:58:56 -0800 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul6.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id TAA09233; Thu, 17 Dec 1998 19:58:56 -0800 (PST) Date: Thu, 17 Dec 1998 19:58:29 -0800 (PST) From: "Jason C. Wells" X-Sender: jason@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: Colin Eric Johnson cc: freebsd-stable@FreeBSD.ORG Subject: Re: going from 2.2.8 to 3.0, when? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Dec 1998, Colin Eric Johnson wrote: >So here I am inbetween semesters and I'm think that this is an excellent >time to do an upgrade. So now my question is, what's the planned date for >the -STABLE branch to working on the 3.x code? Should I run with it now? I read the other guys reply and say "Baaaah!!!" Go for it. Especially with a clean install. Hey... why deal with aout to elf at a later date. Go to elf now. I upgraded my box from 2.2.7 to 3.0 (with a lot of work to recompile all of my ports) but now my system is entirely ELF. I didn't lose any data or configuration. I do however have to clean out /etc as I noticed that 3.0 made some changes. HTH! Catchya Later, | UW Mechanical Engineering Jason Wells | http://weber.u.washington.edu/~jcwells/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 18 05:54:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10454 for freebsd-stable-outgoing; Fri, 18 Dec 1998 05:54:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10449 for ; Fri, 18 Dec 1998 05:54:14 -0800 (PST) (envelope-from lowell@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id IAA19529; Fri, 18 Dec 1998 08:54:05 -0500 (EST) Received: by world.std.com (TheWorld/Spike-2.0) id AA21575; Fri, 18 Dec 1998 08:54:05 -0500 To: freebsd-stable@FreeBSD.ORG Subject: Re: ERRATA NOTICE: FreeBSD 2.2.8-RELEASE References: <199812180100.SAA23512@ice.cold.org> From: Lowell Gilbert Date: 18 Dec 1998 08:54:04 -0500 In-Reply-To: freebsd-errata-update@roguetrader.com's message of 18 Dec 1998 02:10:12 +0100 Message-Id: Lines: 17 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Except that whereis is in usr/bin, not usr/sbin... freebsd-errata-update@roguetrader.com writes: > The last update was sent: Wed Dec 16 05:54:21 1998 > This update is sent: Thu Dec 17 18:00:18 1998 > > ------------------------------------------------------------------ > ---- SYSTEM ERRATA INFORMATION: > > o /usr/sbin/sysctl is an invalid link and whereis(1) doesn't work. > Fix: sysctl(8) has actually moved to /sbin/sysctl. Simply create > a symbolic link for compatability purposes as follows: > ln -sf /sbin/sysctl /usr/sbin > > or syncronize your sources with 2.2-stable and rebuild/install > from /usr/src/usr.sbin/whereis/ and just rm /usr/sbin/sysctl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 18 06:02:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11455 for freebsd-stable-outgoing; Fri, 18 Dec 1998 06:00:38 -0800 (PST) (envelope-from owner-freebsd-stable@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 GAA11450 for ; Fri, 18 Dec 1998 06:00:37 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id GAA62613; Fri, 18 Dec 1998 06:00:39 -0800 (PST) To: Lowell Gilbert cc: freebsd-stable@FreeBSD.ORG Subject: Re: ERRATA NOTICE: FreeBSD 2.2.8-RELEASE In-reply-to: Your message of "18 Dec 1998 08:54:04 EST." Date: Fri, 18 Dec 1998 06:00:39 -0800 Message-ID: <62609.913989639@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Except that whereis is in usr/bin, not usr/sbin... Whoops, typo - thanks, fixed. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 18 08:58:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29964 for freebsd-stable-outgoing; Fri, 18 Dec 1998 08:58:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from king.ki.informatik.uni-frankfurt.de (king.ki.informatik.uni-frankfurt.de [141.2.10.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29950 for ; Fri, 18 Dec 1998 08:58:22 -0800 (PST) (envelope-from marko@king.ki.informatik.uni-frankfurt.de) Received: (from marko@localhost) by king.ki.informatik.uni-frankfurt.de (8.8.6 (PHNE_14041)/8.7.1) id RAA09180; Fri, 18 Dec 1998 17:58:09 +0100 (MEZ) Date: Fri, 18 Dec 1998 17:58:09 +0100 (MEZ) Message-Id: <199812181658.RAA09180@king.ki.informatik.uni-frankfurt.de> From: Marko Schuetz MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-stable@FreeBSD.ORG Subject: ICP vortex GDT RP series support??? X-Mailer: VM 6.34 under Emacs 20.2.1 Reply-To: marko@cs.uni-frankfurt.de Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone working on support for these disk array controllers? Marko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 18 22:04:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29600 for freebsd-stable-outgoing; Fri, 18 Dec 1998 22:04:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail1.panix.com (mail1.panix.com [166.84.0.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29595 for ; Fri, 18 Dec 1998 22:04:23 -0800 (PST) (envelope-from dexter@dexter.dialup.access.net) Received: from dexter.dialup.access.net (dexter.dialup.access.net [166.84.192.199]) by mail1.panix.com (8.8.8/8.8.8/PanixM1.3) with ESMTP id BAA13775; Sat, 19 Dec 1998 01:04:18 -0500 (EST) Received: (from dexter@localhost) by dexter.dialup.access.net (8.8.8/8.8.5) id BAA24647; Sat, 19 Dec 1998 01:04:15 -0500 (EST) Message-ID: <19981219010410.62055@panix.com> Date: Sat, 19 Dec 1998 01:04:10 -0500 From: Dexter McNeil To: Wes Peters Cc: freebsd-stable@FreeBSD.ORG Subject: Re: High speed serial on -STABLE References: <36755AE3.FB91BC8E@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD dexter.dialup.access.net 2.2.8-STABLE FreeBSD 2.2.8-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Holy Moly, a question I can answer! I've been using 16C650s instead of 16550s for 4 years. I've had the '650 support turned on in sio.c for every version that I've been running since 2.2.5. Runs great with my ISDN TA (BitSurfer). BTW, this is on a 486DX66. If your cards have socketed UARTS (40 pin DIP being easy to remove, the square 44 pin PLCCs are a _hump_ to remove without the right tool) you can just swap the chips. Cheers, Dexter McNeil dexter@panix.com On Mon, Dec 14, 1998 at 11:37:23AM -0700, Wes Peters wrote: > Is anyone using the 16C650 support in sio.c on -STABLE, or any other > recent 2.2.x? I have a FreeBSD dialup server that I'm adding ISDN > support to, and need to buy a fast(er) serial card to support an > extern T/A. > > Thanks in advance for your help. > > -- > Where am I, and what am I doing in this handbasket? > > Wes Peters +1.801.915.2061 > Softweyr LLC wes@softweyr.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 17:57:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18254 for freebsd-stable-outgoing; Sat, 19 Dec 1998 17:57:48 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.monmouth.com (shell.monmouth.com [205.231.236.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18243 for ; Sat, 19 Dec 1998 17:57:45 -0800 (PST) (envelope-from support@lomag.net) Received: from lomag.net (bg-tc-ppp103.monmouth.com [209.191.60.104]) by shell.monmouth.com (8.9.0/8.9.0) with ESMTP id UAA21851 for ; Sat, 19 Dec 1998 20:56:20 -0500 (EST) Message-ID: <367C5978.B1242AD4@lomag.net> Date: Sat, 19 Dec 1998 20:57:12 -0500 From: Lomag Organization: Lomag Internet Services X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: FreeBSD 3.0-STABLE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone please cue me in as when 3.0-stablr branch will be ready? I'm forced to use 3.0-current and its very unstable, stays up for about 10 days, after that things just go haywire. I have to use 3.0 to support my UW2 scsi card and Seagate Cheetah hard drives. If anyone can please tell me so I know when to expect it to upgrade asap. Regards, Mark Skurzynski support@lomag.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 18:02:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18717 for freebsd-stable-outgoing; Sat, 19 Dec 1998 18:02:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (castles151.castles.com [208.214.165.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18712 for ; Sat, 19 Dec 1998 18:02: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 SAA04158; Sat, 19 Dec 1998 18:00:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812200200.SAA04158@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Lomag cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 3.0-STABLE In-reply-to: Your message of "Sat, 19 Dec 1998 20:57:12 EST." <367C5978.B1242AD4@lomag.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 19 Dec 1998 18:00:25 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can someone please cue me in as when 3.0-stablr branch > will be ready? Please search the -current list archives for the innmerabale announcements about this. > I'm forced to use 3.0-current and its > very unstable, stays up for about 10 days, after that > things just go haywire. You know, it would be much more helpful if rather than whining about it you participated in working out what's going wrong. Without your help, 3.0-stable is going to behave exactly like 3.0-current (I don't know where you get the impression that changing the name of the branch will have any effect on how it behaves). -- \\ 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-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 18:32:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21906 for freebsd-stable-outgoing; Sat, 19 Dec 1998 18:32:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from multivac.fatburen.org (multivac.fatburen.org [62.20.128.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21898 for ; Sat, 19 Dec 1998 18:32:09 -0800 (PST) (envelope-from staffanu@multivac.fatburen.org) Received: (from staffanu@localhost) by multivac.fatburen.org (8.8.8/8.8.8) id DAA10164; Sun, 20 Dec 1998 03:31:58 +0100 (CET) (envelope-from staffanu) To: freebsd-stable@FreeBSD.ORG Subject: Kernel panic Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Staffan Ulfberg Date: 20 Dec 1998 03:31:52 +0100 Message-ID: <873e6b1r3b.fsf@multivac.fatburen.org> Lines: 25 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I had a kernel panic on my 2.2.8 system a few days ago; just thought I'd tell you about it. You might think I'm totally stupid after reading my description of what caused it, and I probably was at the time: it was sometime around 4.30am... I was running two programs that both use mmap() on the same 500MB file. I killed one of the programs and forgot about the other, and wanted to delete the file and make a new one with all zeros. Deleting the file made it disappear from the directory listing allright, but didn't free up any disk space, so I couldn't create a new 500MB file on that partition. Hmmmm... What to do? Well, I did fsck on the live filesystem and answered yes on the question of whether I wanted to recover 500MB of "lost" file space. Then, I suddenly remembered that other program running, and well, of course I realized why the space for the file hadn't been available earlier... Anyway, I killed that other program too, which had the kernel panic. I sort of think that a kernel panic is a bug, regardless of the level of stupidity needed to trigger it. Any comments? Staffan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 19:10:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24532 for freebsd-stable-outgoing; Sat, 19 Dec 1998 19:10:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ccsales.com (ccsales.com [216.0.22.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24527 for ; Sat, 19 Dec 1998 19:10:31 -0800 (PST) (envelope-from randyk@ccsales.com) Received: from ntrkcasa (pool98.hiper.net [216.0.22.98]) by ccsales.com (8.9.1/8.9.0) with SMTP id TAA15044; Sat, 19 Dec 1998 19:10:39 -0800 (PST) Message-Id: <3.0.5.32.19981219190923.04b0b8c0@ccsales.com> X-Sender: randyk@ccsales.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 19 Dec 1998 19:09:23 -0800 To: Lomag , freebsd-stable@FreeBSD.ORG From: "Randy A. Katz" Subject: Re: FreeBSD 3.0-STABLE In-Reply-To: <367C5978.B1242AD4@lomag.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check your hardware settings. I've had 3.0 working for over 6 months now...no problems through current. I've had it running on over 8 machines, 2 of which are production machines. At 08:57 PM 12/19/98 -0500, Lomag wrote: >Can someone please cue me in as when 3.0-stablr branch >will be ready? I'm forced to use 3.0-current and its >very unstable, stays up for about 10 days, after that >things just go haywire. I have to use 3.0 to support >my UW2 scsi card and Seagate Cheetah hard drives. >If anyone can please tell me so I know when to expect >it to upgrade asap. > >Regards, >Mark Skurzynski >support@lomag.net > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 19:13:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24938 for freebsd-stable-outgoing; Sat, 19 Dec 1998 19:13:37 -0800 (PST) (envelope-from owner-freebsd-stable@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 TAA24927 for ; Sat, 19 Dec 1998 19:13:34 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id TAA20571; Sat, 19 Dec 1998 19:13:23 -0800 (PST) To: Staffan Ulfberg cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel panic In-reply-to: Your message of "20 Dec 1998 03:31:52 +0100." <873e6b1r3b.fsf@multivac.fatburen.org> Date: Sat, 19 Dec 1998 19:13:23 -0800 Message-ID: <20568.914123603@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > on that partition. Hmmmm... What to do? Well, I did fsck on the > live filesystem and answered yes on the question of whether I wanted > to recover 500MB of "lost" file space. You fsck'd a live, mounted filesystem? Really?!? Of course you paniced. It's not a bug to freak out when a clueless administrator stomps on the on-disk version of a filesystem and renders it inconsistent with various cached memory contents. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 19:29:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25857 for freebsd-stable-outgoing; Sat, 19 Dec 1998 19:29:47 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from multivac.fatburen.org (multivac.fatburen.org [62.20.128.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25851 for ; Sat, 19 Dec 1998 19:29:46 -0800 (PST) (envelope-from staffanu@multivac.fatburen.org) Received: (from staffanu@localhost) by multivac.fatburen.org (8.8.8/8.8.8) id EAA10920; Sun, 20 Dec 1998 04:29:34 +0100 (CET) (envelope-from staffanu) To: "Jordan K. Hubbard" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel panic References: <20568.914123603@zippy.cdrom.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Staffan Ulfberg Date: 20 Dec 1998 04:29:32 +0100 In-Reply-To: "Jordan K. Hubbard"'s message of Sat, 19 Dec 1998 19:13:23 -0800 Message-ID: <87zp8jze1v.fsf@multivac.fatburen.org> Lines: 17 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > You fsck'd a live, mounted filesystem? Really?!? I somehow thought that fsck wouldn't even allow modifying a live filesystem, but well, one has to try it to know for sure, right? :) > Of course you paniced. It's not a bug to freak out when a clueless > administrator stomps on the on-disk version of a filesystem and > renders it inconsistent with various cached memory contents. Guilty as charged, I suppose. However, since this was my /var/tmp partition I wasn't too anxious about what would happen. I hadn't expected a panic, though, even if I very well can understand the reasons for it, in retrospect. Staffan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 19:36:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26669 for freebsd-stable-outgoing; Sat, 19 Dec 1998 19:36:40 -0800 (PST) (envelope-from owner-freebsd-stable@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 TAA26659 for ; Sat, 19 Dec 1998 19:36:37 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id TAA26870; Sat, 19 Dec 1998 19:36:27 -0800 (PST) To: Staffan Ulfberg cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel panic In-reply-to: Your message of "20 Dec 1998 04:29:32 +0100." <87zp8jze1v.fsf@multivac.fatburen.org> Date: Sat, 19 Dec 1998 19:36:26 -0800 Message-ID: <26863.914124986@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Guilty as charged, I suppose. However, since this was my /var/tmp > partition I wasn't too anxious about what would happen. I hadn't > expected a panic, though, even if I very well can understand the > reasons for it, in retrospect. Well, now you know why root is considered a special privilege at least. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 23:48:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14149 for freebsd-stable-outgoing; Sat, 19 Dec 1998 23:48:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14140 for ; Sat, 19 Dec 1998 23:48:35 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zrdbL-0001B7-00; Sat, 19 Dec 1998 23:48:31 -0800 Date: Sat, 19 Dec 1998 23:48:27 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Lomag cc: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 3.0-STABLE In-Reply-To: <367C5978.B1242AD4@lomag.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Dec 1998, Lomag wrote: > Can someone please cue me in as when 3.0-stablr branch > will be ready? I'm forced to use 3.0-current and its > very unstable, stays up for about 10 days, after that > things just go haywire. I have to use 3.0 to support > my UW2 scsi card and Seagate Cheetah hard drives. > If anyone can please tell me so I know when to expect > it to upgrade asap. "3.0-stable" is just a name. Basically, the name "3.0-stable" will be given to one of the branches when development on "3.0-current" forks. Questions about 3.0-current should go to the freebsd-current mailing list. Include more detail than "things go haywire", as that won't help anyone fix your problem. Also, 2.2-stable+CAM will also support your UW2 card. > Regards, > Mark Skurzynski > support@lomag.net Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 19 23:52:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14606 for freebsd-stable-outgoing; Sat, 19 Dec 1998 23:52:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14601 for ; Sat, 19 Dec 1998 23:52:02 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zrdeR-0001nt-00; Sat, 19 Dec 1998 23:51:43 -0800 Date: Sat, 19 Dec 1998 23:51:39 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Staffan Ulfberg cc: freebsd-stable@FreeBSD.ORG Subject: Re: Kernel panic In-Reply-To: <873e6b1r3b.fsf@multivac.fatburen.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Dec 1998, Staffan Ulfberg wrote: > I sort of think that a kernel panic is a bug, regardless of the level > of stupidity needed to trigger it. Any comments? Well, basically you corrupted your filesystems. Corrupted filesystems cause panics. It isn't a bug. Panics are the only recourse. What else could the kernel do? The filesystem is unintelligble. The safest thing is to panic, which should cause a reboot and perhaps will be better next time around. > Staffan Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message