From owner-freebsd-stable Sun Dec 14 01:52:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA25038 for stable-outgoing; Sun, 14 Dec 1997 01:52:41 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA25012; Sun, 14 Dec 1997 01:52:32 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id UAA11602; Sun, 14 Dec 1997 20:45:05 +1100 Date: Sun, 14 Dec 1997 20:45:05 +1100 From: Bruce Evans Message-Id: <199712140945.UAA11602@godzilla.zeta.org.au> To: asami@cs.berkeley.edu, jkh@FreeBSD.ORG, nnd@nnd.itfs.nsk.su, stable@FreeBSD.ORG Subject: Re: make buildworld -j2 problems Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I looked at the logs a bit more and found out why. This part looks >like: > >=== >.ORDER: grammar.c tokdefs.h >tokdefs.h grammar.c: grammar.y > ${YACC} ${YACCFLAGS} -d ${PCAP_DISTDIR}/grammar.y > mv y.tab.c grammar.c > mv y.tab.h tokdefs.h >=== > >in -current. .ORDER might have been necessary here, but merging only >that line to -stable was bogus. (Although I still don't quite see why >we need .ORDER -- they are both made from the same rule, it seems.) .ORDER is needed to prevent `make' from executing two copies of the rule concurrently. > * (2) I'll try again after adding a "scanner.so: tokdefs.h" line. But > * it seems to me that there should be a more elegant way to handle > * this. (Don't we need to add a ".po" line too?) The more elegant way is already in bsd.lib.mk. It substitutes .so or .po for .o as required. >The answer to this question is probably also in -current. I'll see >about merging the 1.12 -> 1.13 fix: Removing the `scanner.o: tokdefs.h' line in rev.1.13 was a mistake. scanner.o really does depend on tokdefs.h, and the dependency is not otherwise given in the Makefile. It worked in the non-parallel case because grammar.c is before scanner.c in ${SRCS}. It works for `make depend' because tokdefs.h is in ${SRCS} (and also because grammar.c is in ${SRCS} and building grammar.c builds tokdefs.h; perhaps tokdefs.h doesn't need to be in ${SRCS} because of this). Of course, it works for `make' after `make depend', but `make depend' should not be necessary in clean obj directories. See sh/Makefile for more instructive examples. There, created files like tokdefs.h are included in more than one .c file. This makes it more likely for parallel makes to fail unless lots of dependencies are listed explicitly. >=== >1.13 Sun Jan 5 18:25:53 1997 by wollman > >Fix Makefile so that dependencies are actually right this time. >It is almost always the wrong thing to put .y and .l files directly >into the SRCS. >=== I think it was also mistake to override the default rule for creating grammar.c from grammar.y. The default rule creates y.tab.h as a side effect, and I don't see any additional problems for creating tokdefs.h by mv'ing y.tab.h as in the old rule. Then .ORDER would not be required. There might be problems with concurrent yaccs clobbering each other's y.tab.[ch], but only one yacc is necessary here (since there is only one yacc source file), and multiple ones would have to be handled more carefully anyway (e.g., using .ORDER or yacc -b or yacc -o). Bruce From owner-freebsd-stable Sun Dec 14 14:45:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA17550 for stable-outgoing; Sun, 14 Dec 1997 14:45:09 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from lehua.ilhawaii.net (lehua.ilhawaii.net [206.127.242.100]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA17545 for ; Sun, 14 Dec 1997 14:45:05 -0800 (PST) (envelope-from source@hilo.net) Received: from hilo.net (pm4-7.ilhawaii.net [206.127.241.7]) by lehua.ilhawaii.net (8.8.7/8.6.5) with ESMTP id MAA13249 for ; Sun, 14 Dec 1997 12:46:06 -1000 (HST) Message-ID: <34945E62.A68706CB@hilo.net> Date: Sun, 14 Dec 1997 12:32:03 -1000 From: Cheryl X-Mailer: Mozilla 4.02 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk subscribe freebsd-stable From owner-freebsd-stable Mon Dec 15 01:20:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA10709 for stable-outgoing; Mon, 15 Dec 1997 01:20:30 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA10699 for ; Mon, 15 Dec 1997 01:20:25 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from avalon.ghostwheel.com (avalon.ghostwheel.com [207.201.56.88]) by amber.ghostwheel.com (8.8.8/8.8.5) with SMTP id BAA00228 for ; Mon, 15 Dec 1997 01:19:32 -0800 (PST) Message-Id: <3.0.5.32.19971215011831.00928cd0@amber.ghostwheel.com> X-Sender: merlin@amber.ghostwheel.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 15 Dec 1997 01:18:31 -0800 To: stable@freebsd.org From: Christopher Knight Subject: sysinstall/qcam problem with 2.2-stable Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=====================_882206311==_" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk --=====================_882206311==_ Content-Type: text/plain; charset="us-ascii" -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, My first post to this mailing list... I do not KNOW that this belongs here. I am posting here because I have in the past used the kernel implementation of the qcam drivers without the problems that I will described below. Since I just became current with stable, it seemed that this is a good place to start with my problem. Please direct me to the proper venue if my plea for help does not belong here. Two nights ago I brought myself current to -current with cvsup. After updating my sources, I performed a make world and compiled myself a new GENERIC kernel. After I felt safe with this, I started tweaking. The first step was removing all unused network, scsi and hd drivers from a copy of GENERIC. No problems. Next... I commented out the lpt0 driver and added the following for qcam0: #device lpt0 at isa? port? tty irq 7 vector lptintr device qcam0 at isa? port "IO_LPT1" Everything SEEMED to be fine. Until I ran /stand/sysinstall, the following error was displayed: Dec 15 00:28:28 amber /kernel: stray irq 7 OK, I modified the qcam0 device to snag irq 7 in the same manner that was used for the now disabled lpt0: device qcam0 at isa? port "IO_LPT1" tty irq 7 Now, when I try to run sysinstall, the following is displayed as the system crashes: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xefbffe20 frame pointer = 0x10:0xefbffe78 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 203 (sysinstall) interrupt mask = net tty panic: page fault Any help is appreciated! - -ck -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.0 Charset: noconv iQA/AwUBNJT108UYx/eFxuGhEQLwpwCg6NQBBcEeGzvZkPJPn33pvmtJkPQAoLet nAHvOQrYiQtJwTeEaLQJSNdW =T0ss -----END PGP SIGNATURE----- --=====================_882206311==_ Content-Type: text/plain; charset="us-ascii" Content-Disposition: attachment; filename="kernel.txt" Dec 15 00:10:06 amber /kernel: FreeBSD 2.2.5-STABLE #0: Sun Dec 14 23:02:11 PST 1997 Dec 15 00:10:06 amber /kernel: merlin@amber.ghostwheel.com:/usr/src/sys/compile/CMK.2 Dec 15 00:10:06 amber /kernel: CPU: Pentium (166.19-MHz 586-class CPU) Dec 15 00:10:06 amber /kernel: Origin = "GenuineIntel" Id = 0x52c Stepping=12 Dec 15 00:10:06 amber /kernel: Features=0x1bf Dec 15 00:10:06 amber /kernel: real memory = 67108864 (65536K bytes) Dec 15 00:10:06 amber /kernel: avail memory = 62730240 (61260K bytes) Dec 15 00:10:06 amber /kernel: Probing for devices on PCI bus 0: Dec 15 00:10:06 amber /kernel: chip0 rev 1 on pci0:0 Dec 15 00:10:06 amber /kernel: chip1 rev 0 on pci0:7:0 Dec 15 00:10:06 amber /kernel: chip2 rev 0 on pci0:7:1 Dec 15 00:10:06 amber /kernel: vga0 rev 227 int a irq 9 on pci0:17 Dec 15 00:10:06 amber /kernel: ahc0 rev 1 int a irq 11 on pci0:19 Dec 15 00:10:06 amber /kernel: ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs Dec 15 00:10:06 amber /kernel: ahc0 waiting for scsi devices to settle Dec 15 00:10:06 amber /kernel: (ahc0:0:0): "QUANTUM FIREBALL_TM2110S 300X" type 0 fixed SCSI 2 Dec 15 00:10:06 amber /kernel: sd0(ahc0:0:0): Direct-Access 2014MB (4124736 512 byte sectors) Dec 15 00:10:06 amber /kernel: (ahc0:1:0): "FUJITSU M2624F-512 0405" type 0 fixed SCSI 1 Dec 15 00:10:06 amber /kernel: sd1(ahc0:1:0): Direct-Access 496MB (1015812 512 byte sectors) Dec 15 00:10:06 amber /kernel: (ahc0:2:0): "QUANTUM LPS270S 590A" type 0 fixed SCSI 2 Dec 15 00:10:06 amber /kernel: sd2(ahc0:2:0): Direct-Access 258MB (528808 512 byte sectors) Dec 15 00:10:06 amber /kernel: (ahc0:6:0): "TOSHIBA CD-ROM XM-3601TA 0725" type 5 removable SCSI 2 Dec 15 00:10:06 amber /kernel: cd0(ahc0:6:0): CD-ROM cd present [328222 x 2048 byte records] Dec 15 00:10:07 amber /kernel: Probing for devices on the ISA bus: Dec 15 00:10:07 amber /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Dec 15 00:10:07 amber /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Dec 15 00:10:07 amber /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Dec 15 00:10:07 amber /kernel: sio0: type 16550A Dec 15 00:10:07 amber /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Dec 15 00:10:07 amber /kernel: sio1: type 16550A Dec 15 00:10:07 amber /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Dec 15 00:10:07 amber /kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 15 00:10:07 amber /kernel: fd0: 1.44MB 3.5in Dec 15 00:10:07 amber /kernel: 1 3C5x9 board(s) on ISA found at 0x300 Dec 15 00:10:07 amber /kernel: ep0 at 0x300-0x30f irq 10 on isa Dec 15 00:10:07 amber /kernel: ep0: aui/utp[*UTP*] address 00:20:af:76:2f:c7 Dec 15 00:10:07 amber /kernel: npx0 flags 0x1 on motherboard Dec 15 00:10:07 amber /kernel: npx0: INT 16 interface Dec 15 00:10:07 amber /kernel: qcam0 at 0x378 on isa Dec 15 00:10:07 amber /kernel: qcam0: unidirectional parallel port Dec 15 00:10:07 amber /kernel: Intel Pentium F00F detected, installing workaround --=====================_882206311==_-- From owner-freebsd-stable Mon Dec 15 02:24:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA15388 for stable-outgoing; Mon, 15 Dec 1997 02:24:36 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from baloon.mimi.com (sjx-ca124-48.ix.netcom.com [207.223.162.176]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA15383; Mon, 15 Dec 1997 02:24:27 -0800 (PST) (envelope-from asami@sunrise.cs.berkeley.edu) Received: (from asami@localhost) by baloon.mimi.com (8.8.8/8.8.8) id CAA14443; Mon, 15 Dec 1997 02:24:04 -0800 (PST) (envelope-from asami) Date: Mon, 15 Dec 1997 02:24:04 -0800 (PST) Message-Id: <199712151024.CAA14443@baloon.mimi.com> To: bde@zeta.org.au CC: jkh@FreeBSD.ORG, nnd@nnd.itfs.nsk.su, stable@FreeBSD.ORG In-reply-to: <199712140945.UAA11602@godzilla.zeta.org.au> (message from Bruce Evans on Sun, 14 Dec 1997 20:45:05 +1100) Subject: Re: make buildworld -j2 problems From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * .ORDER is needed to prevent `make' from executing two copies of the rule * concurrently. Oh, I see. * Removing the `scanner.o: tokdefs.h' line in rev.1.13 was a mistake. * scanner.o really does depend on tokdefs.h, and the dependency is not * otherwise given in the Makefile. It worked in the non-parallel case * because grammar.c is before scanner.c in ${SRCS}. It works for `make * depend' because tokdefs.h is in ${SRCS} (and also because grammar.c is * in ${SRCS} and building grammar.c builds tokdefs.h; perhaps tokdefs.h * doesn't need to be in ${SRCS} because of this). Of course, it works for * `make' after `make depend', but `make depend' should not be necessary * in clean obj directories. Umm. Well it's not me that made that change. So what do you propose, revert it back? * See sh/Makefile for more instructive examples. There, created files * like tokdefs.h are included in more than one .c file. This makes it * more likely for parallel makes to fail unless lots of dependencies * are listed explicitly. Eek. That's one hairy beast. I'll see if I can digest that one.... * I think it was also mistake to override the default rule for creating * grammar.c from grammar.y. The default rule creates y.tab.h as a side * effect, and I don't see any additional problems for creating tokdefs.h by * mv'ing y.tab.h as in the old rule. Then .ORDER would not be required. * There might be problems with concurrent yaccs clobbering each other's * y.tab.[ch], but only one yacc is necessary here (since there is only * one yacc source file), and multiple ones would have to be handled more * carefully anyway (e.g., using .ORDER or yacc -b or yacc -o). Um, so should be back it out? Satoshi From owner-freebsd-stable Mon Dec 15 02:39:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA16256 for stable-outgoing; Mon, 15 Dec 1997 02:39:49 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA16248 for ; Mon, 15 Dec 1997 02:39:46 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from avalon.ghostwheel.com (avalon.ghostwheel.com [207.201.56.88]) by amber.ghostwheel.com (8.8.8/8.8.5) with SMTP id CAA00453 for ; Mon, 15 Dec 1997 02:38:54 -0800 (PST) Message-Id: <3.0.5.32.19971215023742.00939100@amber.ghostwheel.com> X-Sender: merlin@amber.ghostwheel.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 15 Dec 1997 02:37:42 -0800 To: stable@freebsd.org From: Christopher Knight Subject: Re: sysinstall/qcam problem with 2.2-stable In-Reply-To: <3.0.5.32.19971215011831.00928cd0@amber.ghostwheel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 At 01:18 AM 12/15/97 -0800, you wrote: > Two nights ago I brought myself current to -current with cvsup. >After updating my sources, I performed a make world and compiled >myself a new GENERIC kernel. My apologies, I mispoke above. I brought myself current to -STABLE with cvsup two days ago. - -ck -----BEGIN PGP SIGNATURE----- Version: PGP for Personal Privacy 5.0 Charset: noconv iQA/AwUBNJUIc8UYx/eFxuGhEQJizACeMt1MXPq2I3tlAy5hpxGVregZi+YAoN+r GOgV0Ku7/Ktd8bdAnfXKx86r =OH9T -----END PGP SIGNATURE----- From owner-freebsd-stable Mon Dec 15 04:10:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA21460 for stable-outgoing; Mon, 15 Dec 1997 04:10:09 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA21427; Mon, 15 Dec 1997 04:10:00 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id XAA27712; Mon, 15 Dec 1997 23:03:00 +1100 Date: Mon, 15 Dec 1997 23:03:00 +1100 From: Bruce Evans Message-Id: <199712151203.XAA27712@godzilla.zeta.org.au> To: asami@cs.berkeley.edu, bde@zeta.org.au Subject: Re: make buildworld -j2 problems Cc: jkh@FreeBSD.ORG, nnd@nnd.itfs.nsk.su, stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > * .ORDER is needed to prevent `make' from executing two copies of the rule > * concurrently. > >Oh, I see. > > * Removing the `scanner.o: tokdefs.h' line in rev.1.13 was a mistake. >... >Umm. Well it's not me that made that change. So what do you propose, >revert it back? Revert it forward ;-). > > * I think it was also mistake to override the default rule for creating > * grammar.c from grammar.y. The default rule creates y.tab.h as a side >Um, so should be back it out? Not sure about this. The current rule works, but requires more code (first for the rule, then for .ORDER to make it work). Perhaps the correct fix is to not rename y.tab.h. Renaming y.tab.c is another mistake. It breaks breaks debugging (the renamed file contains line numbers for the original). bsd.{prog,lib}.mk probably should override sys.mk to do this better. It should also add the generated files to CLEANFILES. Bruce From owner-freebsd-stable Mon Dec 15 04:20:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA22146 for stable-outgoing; Mon, 15 Dec 1997 04:20:32 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA22138 for ; Mon, 15 Dec 1997 04:20:22 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id XAA28082; Mon, 15 Dec 1997 23:13:51 +1100 Date: Mon, 15 Dec 1997 23:13:51 +1100 From: Bruce Evans Message-Id: <199712151213.XAA28082@godzilla.zeta.org.au> To: merlin@ghostwheel.com, stable@FreeBSD.ORG Subject: Re: sysinstall/qcam problem with 2.2-stable Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Next... I commented out the lpt0 driver and added the following >for qcam0: > >#device lpt0 at isa? port? tty irq 7 vector lptintr >device qcam0 at isa? port "IO_LPT1" > > Everything SEEMED to be fine. Until I ran /stand/sysinstall, the >following error was displayed: > > Dec 15 00:28:28 amber /kernel: stray irq 7 This is probably correct behaviour. Using irq 7 in a driver breaks reporting of stray interrupts. > OK, I modified the qcam0 device to snag irq 7 in the same manner >that was used for the now disabled lpt0: > >device qcam0 at isa? port "IO_LPT1" tty irq 7 Don't do that. qcam doesn't use interrupts, and this line is missing a vector for the interrupt. The configuration error is not detected by config, and this line happens to be equivalent to: device qcam0 at isa? port "IO_LPT1" tty irq 7 vector 0 >Now, when I try to run sysinstall, the following is displayed as the >system crashes: > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x0 >fault code = supervisor read, page not present >instruction pointer = 0x8:0x0 This is because the stray interrupt was sent to the "handler" at address 0 instead of the normal stray interrupt handler. Bruce From owner-freebsd-stable Mon Dec 15 09:37:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA16823 for stable-outgoing; Mon, 15 Dec 1997 09:37:58 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA16818; Mon, 15 Dec 1997 09:37:48 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id MAA00814; Mon, 15 Dec 1997 12:37:38 -0500 (EST) (envelope-from toor) Message-Id: <199712151737.MAA00814@dyson.iquest.net> Subject: Re: Stability Of FreeBSD 2.2.5 CD-ROM Release In-Reply-To: <3479A106.6B6E@natsoft.com.au> from Craig Wilson at "Nov 24, 97 03:45:10 pm" To: craig@natsoft.com.au (Craig Wilson) Date: Mon, 15 Dec 1997 12:37:38 -0500 (EST) Cc: dyson@freebsd.org, stable@freebsd.org From: "John S. Dyson" Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Craig Wilson said: > John S. Dyson wrote: > > If you are using FreeBSD in a pseudo-mission critical application, I strongly > > suggest applying the vm_page patches that have been included into the > > RELENG_2_2 code. Also, there is an odd "delay" problem happening, and > > frankly, there is no upper level reason in the VFS or VM code that I can see. > > John, thank you for your reply. > > Does 2.2.2 suffer from the vm_page problem, or the delay problem? > The vm_page problem does exist in 2.2.2, and 2.2.5. 2.2.6 will not have it. I can't remember about the delay problem. Thanks for pinging me on it through. > > Could you please tell me what files are required to fix the vm_page > problem? > /sys/vm/vm_page.c (from 2.2.5 to -stable) I'll try to post this to various users who are asking about problems in 2.2.5. -- John dyson@freebsd.org jdyson@nc.com From owner-freebsd-stable Mon Dec 15 10:45:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA24579 for stable-outgoing; Mon, 15 Dec 1997 10:45:39 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA24574 for ; Mon, 15 Dec 1997 10:45:34 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from avalon.ghostwheel.com (avalon.ghostwheel.com [207.201.56.88]) by amber.ghostwheel.com (8.8.8/8.8.5) with SMTP id KAA01261; Mon, 15 Dec 1997 10:44:17 -0800 (PST) Message-Id: <3.0.5.32.19971215104217.0093aa00@amber.ghostwheel.com> X-Sender: merlin@amber.ghostwheel.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 15 Dec 1997 10:42:17 -0800 To: Bruce Evans , stable@FreeBSD.ORG From: Christopher Knight Subject: Re: sysinstall/qcam problem with 2.2-stable In-Reply-To: <199712151213.XAA28082@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 11:13 PM 12/15/97 +1100, Bruce Evans wrote: >> Dec 15 00:28:28 amber /kernel: stray irq 7 > >This is probably correct behaviour. Using irq 7 in a driver breaks >reporting of stray interrupts. This may be a dumb newbie question... but why is a stray interrupt 7 generated when sysinstall is run? >> OK, I modified the qcam0 device to snag irq 7 in the same manner >>that was used for the now disabled lpt0: >> >>device qcam0 at isa? port "IO_LPT1" tty irq 7 > >Don't do that. qcam doesn't use interrupts, and this line is missing >a vector for the interrupt. The configuration error is not detected >by config, and this line happens to be equivalent to: > >device qcam0 at isa? port "IO_LPT1" tty irq 7 vector 0 Thank you for the explanation. I knew there is a reason I should not be tweaking my box, in areas I have little experience, when I'm having a sleepless night. :) -ck From owner-freebsd-stable Mon Dec 15 12:01:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA05349 for stable-outgoing; Mon, 15 Dec 1997 12:01:17 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from passer.osg.gov.bc.ca (passer.osg.gov.bc.ca [142.32.110.29]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA05342 for ; Mon, 15 Dec 1997 12:01:13 -0800 (PST) (envelope-from cschuber@passer.osg.gov.bc.ca) Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.8.8/8.6.10) id LAA12287 for ; Mon, 15 Dec 1997 11:30:21 -0800 (PST) Message-Id: <199712151930.LAA12287@passer.osg.gov.bc.ca> Received: from localhost(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost, id smtpdaawgna; Mon Dec 15 11:30:13 1997 X-Mailer: exmh version 2.0gamma 1/27/96 Reply-to: Cy Schubert - ITSD Open Systems Group X-Sender: cschuber To: freebsd-stable@freebsd.org Subject: 2.2.6 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Dec 1997 11:28:51 -0800 From: Cy Schubert - ITSD Open Systems Group Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm not looking for any firm dates. When is it anticipated (best guess) that 2.2.6-RELEASE will be out? Will it be shipped on CDROM? Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca Cy.Schubert@gems8.gov.bc.ca "Quit spooling around, JES do it." From owner-freebsd-stable Mon Dec 15 18:36:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA12412 for stable-outgoing; Mon, 15 Dec 1997 18:36:23 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA12407 for ; Mon, 15 Dec 1997 18:36:20 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id SAA23947; Mon, 15 Dec 1997 18:35:41 -0800 (PST) To: Cy Schubert - ITSD Open Systems Group cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 In-reply-to: Your message of "Mon, 15 Dec 1997 11:28:51 PST." <199712151930.LAA12287@passer.osg.gov.bc.ca> Date: Mon, 15 Dec 1997 18:35:41 -0800 Message-ID: <23943.882239741@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm not looking for any firm dates. When is it anticipated (best guess) that > 2.2.6-RELEASE will be out? Will it be shipped on CDROM? Q1 98 and yes. :) Jordan From owner-freebsd-stable Mon Dec 15 22:03:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA27208 for stable-outgoing; Mon, 15 Dec 1997 22:03:47 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from super.zippo.com (perry.zippo.com [207.211.168.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA27195 for ; Mon, 15 Dec 1997 22:03:42 -0800 (PST) (envelope-from reyesf@super.zippo.com) Received: (from reyesf@localhost) by super.zippo.com (8.8.6/8.8.7) id WAA02757; Mon, 15 Dec 1997 22:03:40 -0800 (PST) Message-Id: <199712160603.WAA02757@super.zippo.com> From: "Francisco Reyes" To: "Jordan K. Hubbard" Cc: "freebsd-stable@freebsd.org" Date: Tue, 16 Dec 97 01:03:22 -0400 Reply-To: "Francisco Reyes" Priority: Normal X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: 2.2.6 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Dec 1997 18:35:41 -0800, Jordan K. Hubbard wrote: >> I'm not looking for any firm dates. When is it anticipated (best guess) that > >> 2.2.6-RELEASE will be out? Will it be shipped on CDROM? > >Q1 98 and yes. :) Any hints on new features? I had never ran "stable" before until about 3 weeks ago so how does it differ going from Stable to a new release? How about if one was on "current", would there be much of a difference (if any)? Before I got CVSup working I used to go from Release to Release so there usually where significant changes/enhancements. Any reason why we don't any have info on upcoming releases on the web? From owner-freebsd-stable Mon Dec 15 23:06:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA01559 for stable-outgoing; Mon, 15 Dec 1997 23:06:53 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id XAA01548 for ; Mon, 15 Dec 1997 23:06:50 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xhr5P-0000qt-00; Mon, 15 Dec 1997 23:06:35 -0800 Date: Mon, 15 Dec 1997 23:06:31 -0800 (PST) From: Tom To: Francisco Reyes cc: "Jordan K. Hubbard" , "freebsd-stable@freebsd.org" Subject: Re: 2.2.6 In-Reply-To: <199712160603.WAA02757@super.zippo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 16 Dec 1997, Francisco Reyes wrote: > On Mon, 15 Dec 1997 18:35:41 -0800, Jordan K. Hubbard wrote: > > >> I'm not looking for any firm dates. When is it anticipated (best guess) that > > > >> 2.2.6-RELEASE will be out? Will it be shipped on CDROM? > > > >Q1 98 and yes. :) > > Any hints on new features? > > I had never ran "stable" before until about 3 weeks ago so how does > it differ going from Stable to a new release? How about if one was on The new release will just be copy of stable taken on a particular date. You should notice very little difference, especially if you are running a three week old copy of stable. Of course, that is the whole point: the stable branch is not supposed to change. > "current", would there be much of a difference (if any)? Before I got The difference between current and stable is huge. Those huge changes are, at this time, half good and half bad. Once that changes, releases will be made from the current branch, and stable will be retired. > Any reason why we don't any have info on upcoming releases on the > web? This begs the question: why do we need info about upcoming releases on the web? Tom From owner-freebsd-stable Tue Dec 16 01:22:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA10407 for stable-outgoing; Tue, 16 Dec 1997 01:22:12 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA10396 for ; Tue, 16 Dec 1997 01:22:08 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id BAA25035; Tue, 16 Dec 1997 01:21:56 -0800 (PST) To: "Francisco Reyes" cc: "freebsd-stable@freebsd.org" Subject: Re: 2.2.6 In-reply-to: Your message of "Tue, 16 Dec 1997 01:03:22 -0400." <199712160603.WAA02757@super.zippo.com> Date: Tue, 16 Dec 1997 01:21:55 -0800 Message-ID: <25031.882264115@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Any hints on new features? Nope. I don't prepare this kind of information until a release is imminent since it's too much trouble to maintain incrementally. For the finest of all possible "hints" - see the commit logs for the 2.2-stable branch. :-) > I had never ran "stable" before until about 3 weeks ago so how does > it differ going from Stable to a new release? How about if one was on I'm not sure I understand the question. > "current", would there be much of a difference (if any)? Before I got Between -current and -stable? Sure, lots. > Any reason why we don't any have info on upcoming releases on the > web? See above. :) Jordan From owner-freebsd-stable Tue Dec 16 02:40:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA15291 for stable-outgoing; Tue, 16 Dec 1997 02:40:21 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA15278 for ; Tue, 16 Dec 1997 02:40:17 -0800 (PST) (envelope-from wosch@cs.tu-berlin.de) Received: from panke.panke.de (anonymous214.ppp.cs.tu-berlin.de [130.149.17.214]) by mail.cs.tu-berlin.de (8.8.6/8.8.8) with ESMTP id LAA14677; Tue, 16 Dec 1997 11:29:41 +0100 (MET) Received: (from wosch@localhost) by panke.panke.de (8.8.5/8.6.12) id DAA00831; Tue, 16 Dec 1997 03:17:50 +0100 (MET) To: Cy Schubert - ITSD Open Systems Group Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 References: <199712151930.LAA12287@passer.osg.gov.bc.ca> From: Wolfram Schneider Date: 16 Dec 1997 03:17:48 +0100 In-Reply-To: Cy Schubert - ITSD Open Systems Group's message of Mon, 15 Dec 1997 11:28:51 -0800 Message-ID: Lines: 7 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Cy Schubert - ITSD Open Systems Group writes: > I'm not looking for any firm dates. When is it anticipated (best guess) > that 2.2.6-RELEASE will be out? Will it be shipped on CDROM? One day before the 2.2.6.1-RELEASE ;-) Wolfram From owner-freebsd-stable Tue Dec 16 04:08:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA20430 for stable-outgoing; Tue, 16 Dec 1997 04:08:40 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA20422 for ; Tue, 16 Dec 1997 04:08:35 -0800 (PST) (envelope-from thomas@ghpc8.ihf.rwth-aachen.de) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.7/8.8.6) with ESMTP id NAA29899 for ; Tue, 16 Dec 1997 13:08:18 +0100 (CET) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.7/8.8.5) id NAA29482; Tue, 16 Dec 1997 13:08:16 +0100 (CET) To: stable@FreeBSD.ORG Subject: buildworld failure From: Thomas Gellekum Date: 16 Dec 1997 13:08:13 +0100 Message-ID: <87ra7dsd76.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 57 X-Mailer: Gnus v5.4.37/XEmacs 19.16 Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Moin, current sources (cvsup'd this morning), first `make buildworld' since 11/04: -------------------------------------------------------------- Cleaning up the temporary build tree -------------------------------------------------------------- mkdir -p /usr/obj/usr/src/tmp chflags -R noschg /usr/obj/usr/src/tmp/ rm -rf /usr/obj/usr/src/tmp [...] ===> lkm/wcd cc -nostdinc -O -pipe -nostdinc -I. -DWCD_MODULE -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/wcd/../../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lkm/wcd/../../sys/i386/isa/wcd.c /usr/src/lkm/wcd/../../sys/i386/isa/wcd.c:1114: redefinition of `_module' /usr/src/lkm/wcd/../../sys/i386/isa/wcd.c:1113: `_module' previously defined here /usr/src/lkm/wcd/../../sys/i386/isa/wcd.c: In function `wcd_mod': /usr/src/lkm/wcd/../../sys/i386/isa/wcd.c:1184: `rwcd_module' undeclared (first use this function) /usr/src/lkm/wcd/../../sys/i386/isa/wcd.c:1184: (Each undeclared identifier is reported only once /usr/src/lkm/wcd/../../sys/i386/isa/wcd.c:1184: for each function it appears in.) /usr/src/lkm/wcd/../../sys/i386/isa/wcd.c:1190: `wcd_module' undeclared (first use this function) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. The versions of lkm.h and wcd.c are File: wcd.c Status: Up-to-date Working revision: 1.39 Mon Dec 15 08:57:39 1997 ^^^^ (huh?) Repository revision: 1.39 /usr/cvs/src/sys/i386/isa/wcd.c,v Sticky Tag: RELENG_2_2 (branch: 1.39.2) Sticky Date: (none) Sticky Options: (none) File: lkm.h Status: Up-to-date Working revision: 1.12.2.2 Mon Dec 15 09:21:30 1997 Repository revision: 1.12.2.2 /usr/cvs/src/sys/sys/lkm.h,v Sticky Tag: RELENG_2_2 (branch: 1.12.2) Sticky Date: (none) Sticky Options: (none) What am I missing here? tg From owner-freebsd-stable Tue Dec 16 11:11:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA19843 for stable-outgoing; Tue, 16 Dec 1997 11:11:08 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA19838 for ; Tue, 16 Dec 1997 11:11:05 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id LAA26646; Tue, 16 Dec 1997 11:10:34 -0800 (PST) To: Wolfram Schneider cc: Cy Schubert - ITSD Open Systems Group , freebsd-stable@FreeBSD.ORG Subject: Re: 2.2.6 In-reply-to: Your message of "16 Dec 1997 03:17:48 +0100." Date: Tue, 16 Dec 1997 11:10:33 -0800 Message-ID: <26643.882299433@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Cy Schubert - ITSD Open Systems Group writes: > > I'm not looking for any firm dates. When is it anticipated (best guess) > > that 2.2.6-RELEASE will be out? Will it be shipped on CDROM? > > One day before the 2.2.6.1-RELEASE ;-) *Slap* :-) From owner-freebsd-stable Tue Dec 16 15:30:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA10818 for stable-outgoing; Tue, 16 Dec 1997 15:30:24 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id PAA10812; Tue, 16 Dec 1997 15:30:19 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xi6RN-0003qW-00; Tue, 16 Dec 1997 15:30:17 -0800 Date: Tue, 16 Dec 1997 15:30:14 -0800 (PST) From: Tom To: stable@freebsd.org, wpaul@freebsd.org Subject: current ypbind into stable? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Could some one commit the current ypbind into stable? The "-m" param for ypbind is very handy for non-local NIS servers. I'm doing this already by installing the ypbind from current into /usr/local/sbin and using it instead. Tom From owner-freebsd-stable Tue Dec 16 17:49:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22562 for stable-outgoing; Tue, 16 Dec 1997 17:49:16 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from baklava.alt.net (root@baklava.alt.net [207.14.113.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA22527 for ; Tue, 16 Dec 1997 17:48:51 -0800 (PST) (envelope-from ccaputo@alt.net) Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.8.5/8.7.3) with SMTP id RAA06315; Tue, 16 Dec 1997 17:48:45 -0800 (PST) Date: Tue, 16 Dec 1997 17:48:45 -0800 (PST) From: Chris Caputo To: freebsd-stable@freebsd.org Subject: DEC DE500-BA supported? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a new card which apparently has replaced the DE500-AA. It uses the DEC 21143 chip. The if_de.c driver appears to support this, but does anyone have any actual experience with stable. Thanks, Chris From owner-freebsd-stable Tue Dec 16 19:31:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA01641 for stable-outgoing; Tue, 16 Dec 1997 19:31:18 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from titanium.yy.cs.keio.ac.jp (titanium.yy.cs.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA01632 for ; Tue, 16 Dec 1997 19:31:13 -0800 (PST) (envelope-from sanpei@yy.cs.keio.ac.jp) Received: from lavender.rad.cc.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by titanium.yy.cs.keio.ac.jp (8.8.8+3.0Wbeta7/3.6W) with ESMTP id MAA09764; Wed, 17 Dec 1997 12:30:22 +0900 (JST) Received: (from sanpei@localhost) by lavender.rad.cc.keio.ac.jp (8.8.5/3.6Wbeta4) id MAA01163; Wed, 17 Dec 1997 12:30:21 +0900 (JST) Message-Id: <199712170330.MAA01163@lavender.rad.cc.keio.ac.jp> To: freebsd-stable@FreeBSD.ORG, ccaputo@alt.net Subject: DEC DE500-BA supported? X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 17 Dec 1997 12:30:21 +0900 From: MIHIRA "Sanpei" Yoshiro Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >This is a new card which apparently has replaced the DE500-AA. It uses >the DEC 21143 chip. The if_de.c driver appears to support this, but does >anyone have any actual experience with stable. I tested 2.2.2-RELEASE box with latest de driver[1]. I use 100BASE-T(half duplex) about two months, there are no problem. I think Auto sense mode has some problem(1997/10/20 version of if_de). I set statically 100baseTX via ifconfig link option as below. ifconfig_de0="inet 131.113.y.z netmask 255.255.255.0 link0 link1 -link2" [1] Matt Thomas's de driver page. http://www.3am-software.com/ [2] dmesgs de0 rev 48 int a irq 9 on pci0:11 de0: DEC DE500-BA 21143 [10-100Mb/s] pass 3.0 de0: address xx:xx:xx:xx:xx:xx de0: media: 1="10baseT" 2="Full Duplex 10baseT" 3="100baseTX" 4="Full Duplex 100baseTX" --- Yoshiro MIHIRA Dr. Candidate, Yamamoto Lab. Department of Computer Science Keio University. Yokohama, Japan From owner-freebsd-stable Wed Dec 17 07:10:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA16896 for stable-outgoing; Wed, 17 Dec 1997 07:10:36 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from isb.ncr.com.pk (waraich@isb.ncr.com.pk [194.133.48.215]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA16877 for ; Wed, 17 Dec 1997 07:10:24 -0800 (PST) (envelope-from waraich@Pakistan.NCR.COM) Received: (from waraich@localhost) by isb.ncr.com.pk (8.8.8/8.8.8) id UAA00838; Wed, 17 Dec 1997 20:13:47 +0500 (PKT) (envelope-from Saad.Waraich) From: "Saad M. Waraich" Message-Id: <199712171513.UAA00838@isb.ncr.com.pk> Subject: Panic on stable To: freebsd-stable@freebsd.org Date: Wed, 17 Dec 1997 20:13:47 +0500 (PKT) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi I've 2.2.5-stable for a while now, cvsup'ing every once in a while. No problems at all. The machine has continously up for over a year now, barring power failures etc. The machine is a 486/100 NCR Globalyst 525 with an IDE disk, Adaptec 152x SCSI card and a Seagate 2 gig scsi disk. A short while ago the scsi disk spun down and the machine crashed (rather panic'd). Relevant lines from /var/log/messages follow. Could someone please explain them to me. ------------------------------------------------------------------------- Dec 17 19:11:48 isb /kernel: aic at line 2404: unexpected busfree phase Dec 17 19:11:48 isb /kernel: Debugger("aic6360") called. Dec 17 19:11:48 isb /kernel: panic: panic for historical reasons Dec 17 19:11:48 isb /kernel: Dec 17 19:11:48 isb /kernel: syncing disks... Dec 17 19:11:48 isb /kernel: Dec 17 19:11:48 isb /kernel: Fatal trap 12: page fault while in kernel mode Dec 17 19:11:48 isb /kernel: fault virtual address = 0x10 Dec 17 19:11:48 isb /kernel: fault code = supervisor read, page not present Dec 17 19:11:48 isb /kernel: instruction pointer = 0x8:0xf01320e6 Dec 17 19:11:48 isb /kernel: stack pointer = 0x10:0xf01e1e88 Dec 17 19:11:48 isb /kernel: frame pointer = 0x10:0xf01e1e98 Dec 17 19:11:48 isb /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Dec 17 19:11:49 isb /kernel: = DPL 0, pres 1, def32 1, gran 1 Dec 17 19:11:49 isb /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Dec 17 19:11:49 isb /kernel: current process = Idle Dec 17 19:11:49 isb /kernel: interrupt mask = bio Dec 17 19:11:49 isb /kernel: panic: page fault Dec 17 19:11:49 isb /kernel: Automatic reboot in 15 seconds - press a key on the console to abort Dec 17 19:11:49 isb /kernel: Rebooting... -- Saad From owner-freebsd-stable Wed Dec 17 11:49:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA06980 for stable-outgoing; Wed, 17 Dec 1997 11:49:14 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA06973 for ; Wed, 17 Dec 1997 11:49:09 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id RAA28768 for stable@FreeBSD.ORG; Wed, 17 Dec 1997 17:49:03 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199712171949.RAA28768@gaia.coppe.ufrj.br> Subject: Re: How to know when stable branch is updated? In-Reply-To: from Tom at "Dec 13, 97 00:18:21 am" To: stable@FreeBSD.ORG Date: Wed, 17 Dec 1997 17:49:02 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk #define quoting(Tom) // You can subscribe to the cvs mailing lists. The CVS system // automatically sends out updates to these lists. Beware, most // announcements will be about current, but the ones that are applied to // RELENG_2_2 are detailed. Is it hard to create a cvs-stable list, just for commits regarding -stable ? It would be really useful in such cases... Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-stable Wed Dec 17 13:43:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA16565 for stable-outgoing; Wed, 17 Dec 1997 13:43:14 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA16547 for ; Wed, 17 Dec 1997 13:43:09 -0800 (PST) (envelope-from merlin@ghostwheel.com) Received: from amber.ghostwheel.com (amber.ghostwheel.com [207.201.56.89]) by amber.ghostwheel.com (8.8.8/8.8.5) with SMTP id NAA06721 for ; Wed, 17 Dec 1997 13:42:40 -0800 (PST) Date: Wed, 17 Dec 1997 13:42:40 -0800 (PST) From: Christopher Knight To: stable@FreeBSD.ORG Subject: Re: How to know when stable branch is updated? In-Reply-To: <199712171949.RAA28768@gaia.coppe.ufrj.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just start up cvsup. :) Once I did the initial sync between my sources and stable, I found it was easier/faster to run cvsup every couple of days. That way the incrimental changes take very little time to pull down. -ck ----------------------------------------------------------------------------- Rub her feet. -Lazarus Long ----------------------------------------------------------------------------- On Wed, 17 Dec 1997, Joao Carlos Mendes Luis wrote: > #define quoting(Tom) > // You can subscribe to the cvs mailing lists. The CVS system > // automatically sends out updates to these lists. Beware, most > // announcements will be about current, but the ones that are applied to > // RELENG_2_2 are detailed. > > Is it hard to create a cvs-stable list, just for commits regarding > -stable ? It would be really useful in such cases... > > Jonny > > -- > Joao Carlos Mendes Luis jonny@gta.ufrj.br > +55 21 290-4698 jonny@coppe.ufrj.br > Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI > PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 > From owner-freebsd-stable Wed Dec 17 14:58:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA23663 for stable-outgoing; Wed, 17 Dec 1997 14:58:10 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (ppp9.portal.net.au [202.12.71.109]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA23653 for ; Wed, 17 Dec 1997 14:58:01 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id JAA01729; Thu, 18 Dec 1997 09:06:05 +1030 (CST) Message-Id: <199712172236.JAA01729@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Saad M. Waraich" cc: freebsd-stable@freebsd.org Subject: Re: Panic on stable In-reply-to: Your message of "Wed, 17 Dec 1997 20:13:47 +0500." <199712171513.UAA00838@isb.ncr.com.pk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Dec 1997 09:06:05 +1030 From: Mike Smith Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi > I've 2.2.5-stable for a while now, cvsup'ing every once in a while. No problems > at all. The machine has continously up for over a year now, barring power > failures etc. > > The machine is a 486/100 NCR Globalyst 525 with an IDE disk, Adaptec 152x SCSI > card and a Seagate 2 gig scsi disk. That's a pretty amazing track record for a machine using that disk. > A short while ago the scsi disk spun down and the machine crashed (rather > panic'd). > > Relevant lines from /var/log/messages follow. Could someone please explain > them to me. > > ------------------------------------------------------------------------- > Dec 17 19:11:48 isb /kernel: aic at line 2404: unexpected busfree phase The 'aic' driver (the driver for the 152x card) was not expecting the bus to be free. This is probably due to the disk spinning down. > Dec 17 19:11:48 isb /kernel: Debugger("aic6360") called. > Dec 17 19:11:48 isb /kernel: panic: panic for historical reasons There is no debugger in your system, so the aic driver has paniced. It is at a complete loss as to what to do at this point. > Dec 17 19:11:48 isb /kernel: > Dec 17 19:11:48 isb /kernel: syncing disks... > Dec 17 19:11:48 isb /kernel: > Dec 17 19:11:48 isb /kernel: Fatal trap 12: page fault while in kernel mode The kernel is attempting to flush the cache to disk, but to do that it needs to use the 'aic' driver which is completely confused, causing a fatal trap ('system crash'). The 'aic' driver isn't particularly good at handling problems with disks. If your disk is spinning down, the system is going to follow it. The solution would be to replace the disk. If it's only a couple of years old, it may still be under warranty. mike From owner-freebsd-stable Thu Dec 18 14:36:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA28712 for stable-outgoing; Thu, 18 Dec 1997 14:36:31 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA28707 for ; Thu, 18 Dec 1997 14:36:28 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xioYL-0001bH-00; Thu, 18 Dec 1997 15:36:25 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id PAA12972; Thu, 18 Dec 1997 15:36:44 -0700 (MST) Message-Id: <199712182236.PAA12972@harmony.village.org> To: Joao Carlos Mendes Luis Subject: Re: How to know when stable branch is updated? Cc: stable@freebsd.org In-reply-to: Your message of "Wed, 17 Dec 1997 17:49:02 -0200." <199712171949.RAA28768@gaia.coppe.ufrj.br> References: <199712171949.RAA28768@gaia.coppe.ufrj.br> Date: Thu, 18 Dec 1997 15:36:44 -0700 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199712171949.RAA28768@gaia.coppe.ufrj.br> Joao Carlos Mendes Luis writes: : Is it hard to create a cvs-stable list, just for commits regarding : -stable ? It would be really useful in such cases... I don't know how hard the mialing list would be, but it shouldn't be too hard to write a script that looks in the commit logs (the ones that are basically an archive of all the cvs mail) looking for RELENG_2_2. Warner From owner-freebsd-stable Thu Dec 18 18:07:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA11716 for stable-outgoing; Thu, 18 Dec 1997 18:07:55 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA11709 for ; Thu, 18 Dec 1997 18:07:50 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id AAA10828; Fri, 19 Dec 1997 00:07:25 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199712190207.AAA10828@gaia.coppe.ufrj.br> Subject: Re: How to know when stable branch is updated? In-Reply-To: <199712182236.PAA12972@harmony.village.org> from Warner Losh at "Dec 18, 97 03:36:44 pm" To: imp@village.org (Warner Losh) Date: Fri, 19 Dec 1997 00:07:25 -0200 (EDT) Cc: jonny@coppe.ufrj.br, stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk #define quoting(Warner Losh) // : Is it hard to create a cvs-stable list, just for commits regarding // : -stable ? It would be really useful in such cases... // // I don't know how hard the mialing list would be, but it shouldn't be // too hard to write a script that looks in the commit logs (the ones // that are basically an archive of all the cvs mail) looking for // RELENG_2_2. Just after your bandwidth has already been wasted getting all cvs files. :) Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-stable Thu Dec 18 18:34:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA13171 for stable-outgoing; Thu, 18 Dec 1997 18:34:56 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA13166 for ; Thu, 18 Dec 1997 18:34:48 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0xisGz-0001g0-00; Thu, 18 Dec 1997 19:34:45 -0700 Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.8.8/8.8.3) with ESMTP id TAA13790; Thu, 18 Dec 1997 19:35:11 -0700 (MST) Message-Id: <199712190235.TAA13790@harmony.village.org> To: Joao Carlos Mendes Luis Subject: Re: How to know when stable branch is updated? Cc: stable@freebsd.org In-reply-to: Your message of "Fri, 19 Dec 1997 00:07:25 -0200." <199712190207.AAA10828@gaia.coppe.ufrj.br> References: <199712190207.AAA10828@gaia.coppe.ufrj.br> Date: Thu, 18 Dec 1997 19:35:10 -0700 From: Warner Losh Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199712190207.AAA10828@gaia.coppe.ufrj.br> Joao Carlos Mendes Luis writes: : Just after your bandwidth has already been wasted getting all cvs files. :) Nah. All you need are the files in the CVS/CVSROOT/changelogs should be enough. They aren't that huge... Warner From owner-freebsd-stable Thu Dec 18 20:48:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA21452 for stable-outgoing; Thu, 18 Dec 1997 20:48:57 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA21446 for ; Thu, 18 Dec 1997 20:48:52 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-186.HiWAAY.net [208.147.148.186]) by fly.HiWAAY.net (8.8.7/8.8.6) with ESMTP id WAA26570 for ; Thu, 18 Dec 1997 22:48:48 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id WAA05979 for ; Thu, 18 Dec 1997 22:48:47 -0600 (CST) Message-Id: <199712190448.WAA05979@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: stable@freebsd.org From: David Kelly Subject: Re: How to know when stable branch is updated? In-reply-to: Message from Joao Carlos Mendes Luis of "Fri, 19 Dec 1997 00:07:25 -0200." <199712190207.AAA10828@gaia.coppe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Dec 1997 22:48:46 -0600 Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is it hard to create a cvs-stable list, just for commits regarding > -stable ? It would be really useful in such cases... Maybe I've been to quick to delete the other messages in this thread, but has anyone suggested subscribing to the appropriate CTM list in order to know when -stable is upgraded? Then you get the upgrade at the same time. With CTM you get the source but not the CVS comments. Unless you subscribe to the CVS CTM list. -- 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. From owner-freebsd-stable Fri Dec 19 00:58:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA04642 for stable-outgoing; Fri, 19 Dec 1997 00:58:23 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA04627 for ; Fri, 19 Dec 1997 00:58:15 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id TAA04619; Fri, 19 Dec 1997 19:52:32 +1100 Date: Fri, 19 Dec 1997 19:52:32 +1100 From: Bruce Evans Message-Id: <199712190852.TAA04619@godzilla.zeta.org.au> To: imp@village.org, jonny@coppe.ufrj.br Subject: Re: How to know when stable branch is updated? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >: Just after your bandwidth has already been wasted getting all cvs files. :) > >Nah. All you need are the files in the CVS/CVSROOT/changelogs should >be enough. They aren't that huge... Rotating them makes some updates huge and compressing them makes them harder to use. Bruce From owner-freebsd-stable Fri Dec 19 02:58:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA11106 for stable-outgoing; Fri, 19 Dec 1997 02:58:18 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from brane.digs.iafrica.com (sz9qqJZhjAwfwSwIVn+NuqZjBYr1qnj8@brane.digs.iafrica.com [196.7.162.25]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id CAA11091 for ; Fri, 19 Dec 1997 02:58:01 -0800 (PST) (envelope-from iang@digs.iafrica.com) Received: from digs.iafrica.com [127.0.0.1] ([GTPld4P6XWAY5n+ndQL1vZvW3W23qlpV]) by brane.digs.iafrica.com with esmtp (Exim 1.71 #1) id 0xj07w-0000Vv-00; Fri, 19 Dec 1997 12:57:56 +0200 To: stable@freebsd.org Subject: fsck problem at boot time X-Attribution: BOFH Date: Fri, 19 Dec 1997 12:57:56 +0200 From: Ian Freislich Message-Id: Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Were having a problem with our news server at boot time. Fsck complains that it can't alloc about 8Mb of memory for lncntp (?) when it comes to check the news spool filesystem - a ccd of 4 4Gb disks. This problem relates to the resources allowed to the boot process, run as user daemon - as I'm led to believe. Fscking a 16Gb disk requires more memory than the kernel is willing to give to fsck. The entry in /etc/login.conf for daemon hints that the limits set here are used for rc. Changing the limits here, running cap_mkdb and rebooting proved otherwise. My eventual solution to the problem was to add the follwing to .etc.rc: ulimit -d 65536 ulimit -s 65536 ulimit -m 65536 ulimit -l 65536 Which is IMHO a rather inelegant hack. Can anyone suggest a better solution or at least empathise :) -- igf (Ian Freislich) Senior Network Enginner UUNET Internet Africa http://copernicus.iafrica.com/ From owner-freebsd-stable Fri Dec 19 10:19:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA05294 for stable-outgoing; Fri, 19 Dec 1997 10:19:49 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from homer.duff-beer.com (mail@homer.duff-beer.com [194.207.51.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA05275 for ; Fri, 19 Dec 1997 10:19:43 -0800 (PST) (envelope-from scot@poptart.org) Received: from localhost (scot@localhost) by homer.duff-beer.com (8.8.5/8.8.5) with SMTP id SAA08782; Fri, 19 Dec 1997 18:18:50 GMT Date: Fri, 19 Dec 1997 18:18:49 +0000 (GMT) From: Scot Elliott To: Ian Freislich cc: stable@FreeBSD.ORG Subject: Re: fsck problem at boot time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Dec 1997, Ian Freislich wrote: > This problem relates to the resources allowed to the boot process, > run as user daemon - as I'm led to believe. Fscking a 16Gb disk > requires more memory than the kernel is willing to give to fsck. > The entry in /etc/login.conf for daemon hints that the limits set > here are used for rc. Changing the limits here, running cap_mkdb > and rebooting proved otherwise. The 2.2.2 system I recently installed didn't have a default login.conf - and everything works fine. I see that my new /usr/src/etc which I've since CVSupped, has one with these dodgy default settings in it. It does say at the top of the file that it's an *example*... and I rather think that it's bad news to use this without altering it yfour your own use first. I personally dislike the practice of setting CPU limits for users. There really seems very little point in putting a hard limit of CPU time on a process. This is especialy true for root and daemon - which are used to run system daemons which persist for the whole uptime of the machine. Any server that actually does anything would eventually be killed if it had a hard CPU limit set. Similarly, for login users, there seems very little point because any job which takes that much CPU time can just be split into multiple jobs taking less CPU time - hense using the same total resources and just inconvieniencing the user. It would make more sense to limit CPU resources as a percentage per day or hour. For instance, allocate daemon 25% CPU resources if you only want your server proceses to use a quarter of the machine's CPU. But then you have a problem of what to do when that limit's reached. To be honest Id suggest just staying away from limiting system users. It seems a whole lot simpler just to let them get on with what they do with no interference. Scot Elliott ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)1344 899401 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html From owner-freebsd-stable Fri Dec 19 10:20:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA05384 for stable-outgoing; Fri, 19 Dec 1997 10:20:02 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA05323 for ; Fri, 19 Dec 1997 10:19:56 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xj71H-0005yC-00; Fri, 19 Dec 1997 10:19:31 -0800 Date: Fri, 19 Dec 1997 10:19:29 -0800 (PST) From: Tom To: Ian Freislich cc: stable@freebsd.org Subject: Re: fsck problem at boot time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Dec 1997, Ian Freislich wrote: > The entry in /etc/login.conf for daemon hints that the limits set > here are used for rc. Changing the limits here, running cap_mkdb > and rebooting proved otherwise. Also remove the "tc" entry from the "daemon" class. Whoever created the default /etc/login.conf must be on drugs or something, as including the default entries within each class makes no sense. Basically, this overrides the settings you have set with the lower settings from "default" class. Tom From owner-freebsd-stable Fri Dec 19 11:26:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA10755 for stable-outgoing; Fri, 19 Dec 1997 11:26:32 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mx3.cso.uiuc.edu (mx3.cso.uiuc.edu [128.174.5.24]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA10748 for ; Fri, 19 Dec 1997 11:26:27 -0800 (PST) (envelope-from igor@alecto.physics.uiuc.edu) Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [128.174.83.167]) by mx3.cso.uiuc.edu (8.8.7/8.8.7) with SMTP id NAA27144; Fri, 19 Dec 1997 13:25:48 -0600 (CST) Received: by alecto.physics.uiuc.edu (940816.SGI.8.6.9/940406.SGI) id NAA17448; Fri, 19 Dec 1997 13:23:47 -0600 From: igor@alecto.physics.uiuc.edu (Igor Roshchin) Message-Id: <199712191923.NAA17448@alecto.physics.uiuc.edu> Subject: Re: fsck problem at boot time To: scot@poptart.org (Scot Elliott) Date: Fri, 19 Dec 1997 13:23:46 -0600 (CST) Cc: iang@digs.iafrica.com, stable@FreeBSD.ORG In-Reply-To: from "Scot Elliott" at Dec 19, 97 06:18:49 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I personally dislike the practice of setting CPU limits for users. There > really seems very little point in putting a hard limit of CPU time on a > process. There are many situations when users have "run-away" processes. At some point I was sick of manually killing run-away pine-s, ftp processes, etc. which became such after the connection was terminated (e.g. due to a bad connection) but not closed completely. Setting CPU limit for users' processes would provide automatic killing of such "fantoms" (Note, that such pine starts eating lots of CPU cycles for some reason, bringing the load index to 1 (if it was near 0 initially).) IgoR From owner-freebsd-stable Fri Dec 19 12:10:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA14166 for stable-outgoing; Fri, 19 Dec 1997 12:10:39 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from homer.duff-beer.com (mail@homer.duff-beer.com [194.207.51.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA14158 for ; Fri, 19 Dec 1997 12:10:32 -0800 (PST) (envelope-from scot@poptart.org) Received: from localhost (scot@localhost) by homer.duff-beer.com (8.8.5/8.8.5) with SMTP id UAA09092; Fri, 19 Dec 1997 20:09:46 GMT Date: Fri, 19 Dec 1997 20:09:46 +0000 (GMT) From: Scot Elliott To: Igor Roshchin cc: Scot Elliott , iang@digs.iafrica.com, stable@FreeBSD.ORG Subject: Re: fsck problem at boot time In-Reply-To: <199712191923.NAA17448@alecto.physics.uiuc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Dec 1997, Igor Roshchin wrote: > Setting CPU limit for users' processes would provide > automatic killing of such "fantoms" > (Note, that such pine starts eating lots of CPU cycles > for some reason, bringing the load index to 1 (if it was near 0 initially).) > Actually, I find this with Pine all the time too... is this a bug in pine? But my point about limiting daemon's CPU time still applies - you don't very often execute interactive processes as daemon. I hope. Scot ----------------------------------------------------------------------------- Scot Elliott (scot@poptart.org) | Work: +44 (0)1344 899401 PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019 ----------------------------------------------------------------------------- Public key available by finger at: finger scot@poptart.org or at: http://www.poptart.org/pgpkey.html From owner-freebsd-stable Fri Dec 19 12:27:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA15343 for stable-outgoing; Fri, 19 Dec 1997 12:27:28 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA15338 for ; Fri, 19 Dec 1997 12:27:24 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id HAA25528; Sat, 20 Dec 1997 07:22:27 +1100 Date: Sat, 20 Dec 1997 07:22:27 +1100 From: Bruce Evans Message-Id: <199712192022.HAA25528@godzilla.zeta.org.au> To: iang@digs.iafrica.com, tom@uniserve.com Subject: Re: fsck problem at boot time Cc: stable@freebsd.org Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Also remove the "tc" entry from the "daemon" class. Whoever created the Don't do that. The "default" class sets more than limits. >default /etc/login.conf must be on drugs or something, as including the >default entries within each class makes no sense. Basically, this >overrides the settings you have set with the lower settings from >"default" class. No, `@' is used a lot to cancel the lower settings. Many of the settings are still silly. "daemon" is probably the best set up (in -current and -stable, not in 2.2.5) because it has caused the most problems. Bruce From owner-freebsd-stable Fri Dec 19 13:27:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA19723 for stable-outgoing; Fri, 19 Dec 1997 13:27:24 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mailhost.yahoo.com (mailhost.yahoo.com [205.216.162.34]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA19718 for ; Fri, 19 Dec 1997 13:27:20 -0800 (PST) (envelope-from serge@yahoo-inc.com) Received: from borogove.yahoo.com (borogove.yahoo.com [205.216.162.65]) by mailhost.yahoo.com (8.8.8/8.8.8) with ESMTP id NAA01673; Fri, 19 Dec 1997 13:26:42 -0800 (PST) Received: from borogove.yahoo.com (borogove.yahoo.com [205.216.162.65]) by borogove.yahoo.com (8.8.7/8.8.6) with SMTP id NAA00484; Fri, 19 Dec 1997 13:26:25 -0800 (PST) Date: Fri, 19 Dec 1997 13:26:25 -0800 (PST) From: Sergiy Zhuk X-Sender: serge@borogove.yahoo.com To: Scot Elliott cc: Igor Roshchin , iang@digs.iafrica.com, stable@FreeBSD.ORG Subject: Re: fsck problem at boot time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk hi On Fri, 19 Dec 1997, Scot Elliott wrote: > Actually, I find this with Pine all the time too... is this a bug in pine? not only pine, but any process, waiting for user input and diassociated from its control terminal, i.e. processes which are not designed to run as daemons. > But my point about limiting daemon's CPU time still applies - you don't > very often execute interactive processes as daemon. I hope. typical case: home -> (Internet) -> ssh host1 -> destination ssh host2, run pine (emacs, vi, joe). Then drop your dial-up connection at home. Then login again and look at system load as well at ps ax|grep RN pretty amazing... If you close ssh at home, it will work fine, i.e. pine will be terminated, catching SIGHUP (or whatever) from the parent shell. -- rgds, serge From owner-freebsd-stable Fri Dec 19 13:31:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA20118 for stable-outgoing; Fri, 19 Dec 1997 13:31:38 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA20107 for ; Fri, 19 Dec 1997 13:31:32 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xjA0n-0006GO-00; Fri, 19 Dec 1997 13:31:13 -0800 Date: Fri, 19 Dec 1997 13:31:14 -0800 (PST) From: Tom To: Bruce Evans cc: iang@digs.iafrica.com, stable@freebsd.org Subject: Re: fsck problem at boot time In-Reply-To: <199712192022.HAA25528@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 20 Dec 1997, Bruce Evans wrote: > > Also remove the "tc" entry from the "daemon" class. Whoever created the > > Don't do that. The "default" class sets more than limits. I made a new default class that sets things that are really defaults. > >default /etc/login.conf must be on drugs or something, as including the > >default entries within each class makes no sense. Basically, this > >overrides the settings you have set with the lower settings from > >"default" class. > > No, `@' is used a lot to cancel the lower settings. > > Many of the settings are still silly. "daemon" is probably the best set > up (in -current and -stable, not in 2.2.5) because it has caused the most > problems. > > Bruce Tom From owner-freebsd-stable Fri Dec 19 14:26:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA25749 for stable-outgoing; Fri, 19 Dec 1997 14:26:55 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id OAA25744 for ; Fri, 19 Dec 1997 14:26:51 -0800 (PST) (envelope-from richard@pegasus.com) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id MAA28279; Fri, 19 Dec 1997 12:26:29 -1000 Date: Fri, 19 Dec 1997 12:26:29 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199712192226.MAA28279@pegasus.com> In-Reply-To: Sergiy Zhuk "Re: fsck problem at boot time" (Dec 19, 1:26pm) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: stable@freebsd.org Subject: Re: fsck problem at boot time Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk } > Actually, I find this with Pine all the time too... is this a bug in pine? } } not only pine, but any process, waiting for user input and diassociated from } its control terminal, i.e. processes which are not designed to run as } daemons. } } > But my point about limiting daemon's CPU time still applies - you don't } > very often execute interactive processes as daemon. I hope. } } typical case: } home -> (Internet) -> ssh host1 -> destination ssh host2, run pine (emacs, } vi, joe). } Then drop your dial-up connection at home. } Then login again and look at system load as well at ps ax|grep RN } pretty amazing... } If you close ssh at home, it will work fine, i.e. pine will be terminated, } catching SIGHUP (or whatever) from the parent shell. } You may not always get a signal if the connection isn't terminated properly. Exit on input end of file should cover those cases. Richard