From owner-freebsd-current Sun May 14 01:29:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA00207 for current-outgoing; Sun, 14 May 1995 01:29:12 -0700 Received: from colin.muc.de (root@colin.muc.de [193.174.4.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA00198 for ; Sun, 14 May 1995 01:29:00 -0700 Received: from [193.174.4.22] ([193.174.4.22]) by colin.muc.de with SMTP id <25562-2>; Sun, 14 May 1995 10:28:52 +0200 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 14 May 1995 10:28:08 +0200 To: freebsd-current@freefall.cdrom.com From: lutz@muc.de (Lutz Albers) Subject: Current kernel won't boot Sender: current-owner@FreeBSD.org Precedence: bulk Hello, I've a problem with the current kernel (& system): the boot process will stop after displaying the message that 'npx0' has been found. It will boot fine with the 2.0.R and the the latest snap kernel. I have a 2.0.R system with the latest /usr/src tree build (that makes the system a current system, or?) Hardware: AMD 486 DX40, local bus system 16 MBytes RAM Adaptec 2842 VL SCSI card (the reason for updating to current) 3 hard discs (2 x 1GB, 1 x 340 MB) 3COM 509 Ethernet adapter Spea Mirage VL graphics card. Any ideas, why the kernels stops booting ? ciao lutz --------------------------------------------------------------------- Lutz Albers, Luederitzstr. 14 | And you ? You're no one 81929 - Muenchen, FR Germany | And you ? You're falling phone: +49-89-933 404 | And you ? You're travelling fax: +49-89-929 46 75 | Travelling at the speed of light. email: lutz@muc.de | (Laurie Anderson, Strange Angels) http://www.muc.de/~lutz | Do not take life too seriously, you will never get out of it alive. From owner-freebsd-current Sun May 14 02:27:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA01623 for current-outgoing; Sun, 14 May 1995 02:27:43 -0700 Received: from sequent.kiae.su (sequent.kiae.su [144.206.136.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA01617 for ; Sun, 14 May 1995 02:27:37 -0700 Received: by sequent.kiae.su id AA08773 (5.65.kiae-2 ); Sun, 14 May 1995 13:25:26 +0400 Received: by sequent.KIAE.su (UUMAIL/2.0); Sun, 14 May 95 13:25:26 +0400 Received: (from ache@localhost) by astral.msk.su (8.6.8/8.6.6) id NAA00594; Sun, 14 May 1995 13:17:25 +0400 To: bde@zeta.org.au, freebsd-current@FreeBSD.org, terry@cs.weber.edu, uhclem%nemesis@fw.ast.com References: <199505140424.OAA13885@godzilla.zeta.org.au> In-Reply-To: <199505140424.OAA13885@godzilla.zeta.org.au>; from Bruce Evans at Sun, 14 May 1995 14:24:31 +1000 Message-Id: Organization: Olahm Ha-Yetzirah Date: Sun, 14 May 1995 13:17:24 +0400 (MSD) X-Mailer: Mail/@ [v2.35 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Re: Taylor UUCP Lines: 26 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 920 Sender: current-owner@FreeBSD.org Precedence: bulk In message <199505140424.OAA13885@godzilla.zeta.org.au> Bruce Evans writes: >>>uuchk and uuconv, but these are installed in the wrong place >>>/usr/libexec/uucp with the wrong ownership uucp:uucp and the wrong >>>permissions 550. >>Wrong place: agree. >>Mode and permissions: disagree. >>Normal user must not be able to see phones and passwords from >>system configuration. >Phones and passwords are in /etc/uucp, not in libexec/uucp :-). Shure. Both uuchk and uuconv operates in /etc/uucp. >The programs aren't setuid so they can't read /etc/uucp/* unless >run by root. /etc/uucp must be owned by uucp, it doesn't? -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sun May 14 02:57:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA02368 for current-outgoing; Sun, 14 May 1995 02:57:16 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA02360 for ; Sun, 14 May 1995 02:57:03 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id TAA22337; Sun, 14 May 1995 19:56:20 +1000 Date: Sun, 14 May 1995 19:56:20 +1000 From: Bruce Evans Message-Id: <199505140956.TAA22337@godzilla.zeta.org.au> To: ache@astral.msk.su, bde@zeta.org.au, freebsd-current@FreeBSD.org, terry@cs.weber.edu, uhclem%nemesis@fw.ast.com Subject: Re: Taylor UUCP Sender: current-owner@FreeBSD.org Precedence: bulk >>Phones and passwords are in /etc/uucp, not in libexec/uucp :-). >Shure. Both uuchk and uuconv operates in /etc/uucp. >>The programs aren't setuid so they can't read /etc/uucp/* unless >>run by root. >/etc/uucp must be owned by uucp, it doesn't? Yes the protection is in the non-world-readableness of /etc/uucp. It doesn't belong in the programs. uucp.info warns you not to make the programs setuid for this reason. We follow this warning, but give the programs strange ownership and permissions. Programs should be owned by bin.bin and have permissions 555 except when they are setuid. We follow this rule for /usr/bin/uu*. Bruce From owner-freebsd-current Sun May 14 05:52:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA10046 for current-outgoing; Sun, 14 May 1995 05:52:01 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA10039 for ; Sun, 14 May 1995 05:51:46 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id WAA26068; Sun, 14 May 1995 22:48:40 +1000 Date: Sun, 14 May 1995 22:48:40 +1000 From: Bruce Evans Message-Id: <199505141248.WAA26068@godzilla.zeta.org.au> To: wpaul@ctr.columbia.edu Subject: Re: kern/400: fade_saver loadable kernel module crashes system Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>Number: 400 >>Category: kern >>Synopsis: fade_saver loadable kernel module crashes system > The fade_saver loadable screen saver module causes a fatal > kernel trap when it activates. It can be modload'ed just fine, > but as soon as syscons activates it, the system panics. I'll fix this in a few minutes. declares `palette' as char *, but it is actually char []. The first 4 bytes happen of palette[] happen to be 0's, so a null pointer is dereferenced. The declaration has apparently been wrong ever since the savers were lkm'ed so I don't see how the fade saver could have worked recently. > Also note that 'make load' does not seem to work for > for any of the syscons screen saver modules. It should. Is this just because the entry point is wrong? I noticed some other problems (as someone who knows very little about lkms): - bsd.subdir.mk doesn't support the `load' target. This may be a feature. - the output file is in the object directory so writing it fails when the object dir is nfs mounted and `make load' is run by root. modload has to be run by root :-). - the PR reports more than one bug so it is hard to close :-). > I don't suppose it's occured to anyone what could happen if > a clueless user tries to load a syscons saver module into > a kernel that doesn't have the syscons driver in it? It might I think the load will often fail because the entry point is wrong. Another bug that may be a feature! Perhaps entry points should be named DriverName_LkmEntry_RoutineName[_VersionCookie] to exploit this. Bruce From owner-freebsd-current Sun May 14 07:13:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA12880 for current-outgoing; Sun, 14 May 1995 07:13:19 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA12503 for ; Sun, 14 May 1995 07:12:51 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id AAA28510; Mon, 15 May 1995 00:09:02 +1000 Date: Mon, 15 May 1995 00:09:02 +1000 From: Bruce Evans Message-Id: <199505141409.AAA28510@godzilla.zeta.org.au> To: hsu@clinet.fi Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >>Number: 407 >>Category: bin >>Synopsis: tset -I breaks erase character, termcap says xterm kb=^H >The termcap entry for xterm is false, it says that erase key sends ^H, >while most systems send ^?. It has to be right for the configuration actually being used. This probably requires putting the full termcap entry in the environment. I don't know what X does. >If kb definition is removed, tset -I seems to default to ^H, not >CERASE. The behaviour seems weird: Removing kb alone won't work. You would also have to remove bs and maybe bc and os. It's easier to fix kb. I tried setting it to ^? and moving termcap.db out of the way, but cgetstr() doesn't parse ^? right - it gives ('? & 0x1f) = 0x1f. Apparently you are supposed to use \177. \177 is used in dozens of places in termcap.src while ^? is only used in a couple of places. (BTW, the default syscons keymap still doesn't generate anything for ^?.) tset -I prints "backspace" if kb matches the erase character even if the erase character is ^?. Bruce From owner-freebsd-current Sun May 14 09:50:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA16962 for current-outgoing; Sun, 14 May 1995 09:50:04 -0700 Received: from vinkku.hut.fi (vode@vinkku.hut.fi [130.233.245.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA16956 for ; Sun, 14 May 1995 09:50:02 -0700 Received: (from vode@localhost) by vinkku.hut.fi (8.6.11/8.6.7) id TAA20757; Sun, 14 May 1995 19:49:53 +0300 Date: Sun, 14 May 1995 19:49:53 +0300 From: Kai Vorma Message-Id: <199505141649.TAA20757@vinkku.hut.fi> To: current@FreeBSD.org Subject: A few things.. Reply-to: Kai.Vorma@hut.fi Sender: current-owner@FreeBSD.org Precedence: bulk 1) Prototype for madvise() is missing from sys/mman.h 2) rpcgen doesn't set up proc list properly and may crash. Here is a patch: *** rpc_parse.c~ Sun Aug 7 21:01:32 1994 --- rpc_parse.c Sun May 14 18:13:32 1995 *************** *** 165,170 **** --- 165,171 ---- ptailp = &plist->next; peek(&tok); } while (tok.kind != TOK_RBRACE); + *ptailp = NULL; *vtailp = vlist; vtailp = &vlist->next; scan(TOK_RBRACE, &tok); 3) Reboot doesn't always work. The new keyboard controller reset code in cpu_reset() sometimes just hangs my machine (a nameless 486 clone) and I have to push reset button to get it alive again. The old way worked always. 4) This patch teaches info to read gzipped files (emacs info already works) so one can gzip files in /usr/share/info and save a few megabytes diskspace. *** gnu/usr.bin/texinfo/info/filesys.c~ Tue Sep 13 16:51:29 1994 --- gnu/usr.bin/texinfo/info/filesys.c Sun May 14 19:27:52 1995 *************** *** 76,81 **** --- 76,82 ---- static COMPRESSION_ALIST compress_suffixes[] = { { ".Z", "uncompress" }, { ".Y", "unyabba" }, + { ".gz", "gunzip" }, { ".z", "gunzip" }, { (char *)NULL, (char *)NULL } }; ..vode From owner-freebsd-current Sun May 14 10:54:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA18325 for current-outgoing; Sun, 14 May 1995 10:54:54 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA18310 for ; Sun, 14 May 1995 10:54:50 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id KAA03873; Sun, 14 May 1995 10:54:30 -0700 From: "Rodney W. Grimes" Message-Id: <199505141754.KAA03873@gndrsh.aac.dev.com> Subject: Re: A few things.. To: Kai.Vorma@hut.fi Date: Sun, 14 May 1995 10:54:30 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505141649.TAA20757@vinkku.hut.fi> from "Kai Vorma" at May 14, 95 07:49:53 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 931 Sender: current-owner@FreeBSD.org Precedence: bulk This one is mine so I'll respond to it.... > 3) > > Reboot doesn't always work. The new keyboard controller reset code in > cpu_reset() sometimes just hangs my machine (a nameless 486 clone) > and I have to push reset button to get it alive again. The old way > worked always. Before hanging your machine does it manage to output the string: Keyboard reset did not work, attempting CPU shutdown What happens if you change this: outb(IO_KBD + 4, 0xFE); to this: outb(IO_KBD + 4, 0xFC); in file sys/i386/isa/vm_machdep.c in routine cpu_reset? > 4) > > This patch teaches info to read gzipped files (emacs info already > works) so one can gzip files in /usr/share/info and save a few > megabytes diskspace. Thanks, applied and commited! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sun May 14 10:56:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA18353 for current-outgoing; Sun, 14 May 1995 10:56:06 -0700 Received: from deep-thought.demos.su (root@deep-thought.demos.su [192.91.186.133]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA18345 for ; Sun, 14 May 1995 10:56:01 -0700 Received: by deep-thought.demos.su id VAA22583; (8.6.11/D) Sun, 14 May 1995 21:55:42 +0400 To: wosch@cs.tu-berlin.ed Cc: current@FreeBSD.org Message-ID: Organization: DEMOS Date: Sun, 14 May 1995 21:55:42 +0400 X-Mailer: Mail/@ [v2.34 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Error in catman, please fix it Lines: 10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 492 Sender: current-owner@FreeBSD.org Precedence: bulk Hi, Wolfram. You do chdir to subdir before formatting manpage, it is wrong for some non-FreeBSD manpages which commonly use .so man1/page.1 Your chdir cause "file not found" error, please, remove it -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Sun May 14 11:04:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA18462 for current-outgoing; Sun, 14 May 1995 11:04:13 -0700 Received: from eikon.regent.e-technik.tu-muenchen.de (root@eikon.regent.e-technik.tu-muenchen.de [129.187.42.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA18456 for ; Sun, 14 May 1995 11:04:11 -0700 Received: from vector.eikon.e-technik.tu-muenchen.de ([129.187.142.36]) by eikon.regent.e-technik.tu-muenchen.de with SMTP id <43037>; Sun, 14 May 1995 20:03:52 +0200 Received: (from jhs@localhost) by vector.eikon.e-technik.tu-muenchen.de (8.6.11/8.6.9) id MAA06676 for current@freebsd.org; Sat, 13 May 1995 12:22:16 +0200 Date: Sat, 13 May 1995 12:22:16 +0200 From: Julian Howard Stacey Message-Id: <199505131022.MAA06676@vector.eikon.e-technik.tu-muenchen.de> To: current@FreeBSD.org Subject: jhs has lost mail, anyone awaiting a reply should resend Sender: current-owner@FreeBSD.org Precedence: bulk I had a couple of system crashes yesterday on my local host, & lost mail. Anyone who might be awaiting a reply from me should re-mail me, Sorry for the noise. Julian S jhs@freebsd.org From owner-freebsd-current Sun May 14 12:20:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA23322 for current-outgoing; Sun, 14 May 1995 12:20:08 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA23307 for ; Sun, 14 May 1995 12:20:05 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id NAA23633; Sun, 14 May 1995 13:23:54 -0600 Date: Sun, 14 May 1995 13:23:54 -0600 From: Nate Williams Message-Id: <199505141923.NAA23633@trout.sri.MT.net> To: Kai.Vorma@hut.fi Cc: current@FreeBSD.org Subject: Re: A few things.. In-Reply-To: <199505141649.TAA20757@vinkku.hut.fi> References: <199505141649.TAA20757@vinkku.hut.fi> Sender: current-owner@FreeBSD.org Precedence: bulk > 1) > > Prototype for madvise() is missing from sys/mman.h Thanks, I added the proper prototype to sys/mman.h. Nate From owner-freebsd-current Sun May 14 12:42:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA24860 for current-outgoing; Sun, 14 May 1995 12:42:01 -0700 Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.57]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA24854 for ; Sun, 14 May 1995 12:42:00 -0700 Received: from localhost (localhost [127.0.0.1]) by westhill.cdrom.com (8.6.11/8.6.11) with SMTP id MAA05874 for ; Sun, 14 May 1995 12:41:59 -0700 X-Authentication-Warning: westhill.cdrom.com: Host localhost didn't use HELO protocol To: current@FreeBSD.org Subject: share/doc errors/warnings during make world Date: Sun, 14 May 1995 12:41:59 -0700 Message-ID: <5873.800480519@westhill.cdrom.com> From: Gary Palmer Sender: current-owner@FreeBSD.org Precedence: bulk I was just watching a make world progress through share/doc, and was surprised at the numbers of warnings and errors (?) that were generated. Could some doc expert go through these and fix them? It would be nice to have docs that actually a) worked and b) didn't throw out several hundred messages in the process of trying to work! Thanks Gary From owner-freebsd-current Sun May 14 12:47:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA25280 for current-outgoing; Sun, 14 May 1995 12:47:57 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA25274 for ; Sun, 14 May 1995 12:47:55 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA04352; Sun, 14 May 1995 12:47:44 -0700 From: "Rodney W. Grimes" Message-Id: <199505141947.MAA04352@gndrsh.aac.dev.com> Subject: Re: share/doc errors/warnings during make world To: gpalmer@westhill.cdrom.com (Gary Palmer) Date: Sun, 14 May 1995 12:47:44 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <5873.800480519@westhill.cdrom.com> from "Gary Palmer" at May 14, 95 12:41:59 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 676 Sender: current-owner@FreeBSD.org Precedence: bulk > > > I was just watching a make world progress through share/doc, and was > surprised at the numbers of warnings and errors (?) that were > generated. Could some doc expert go through these and fix them? It > would be nice to have docs that actually a) worked and b) didn't throw > out several hundred messages in the process of trying to work! This is a massive rework required, it would mean bringing back to life the BSD 4.4 macros that someone though we did not need. This work needs to wait until after 2.0.5. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sun May 14 12:55:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA25741 for current-outgoing; Sun, 14 May 1995 12:55:34 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA25722 for ; Sun, 14 May 1995 12:55:29 -0700 Received: from jsdinc.root.com (uucp@localhost) by Root.COM (8.6.8/8.6.5) with UUCP id MAA02187 for freebsd.org!current; Sun, 14 May 1995 12:58:33 -0700 Received: (root@localhost) by localhost (8.6.11/8.6.5) id OAA09678 for current@freebsd.org; Sun, 14 May 1995 14:56:16 GMT Date: Sun, 14 May 1995 14:56:16 GMT From: "John S. Dyson" Message-Id: <199505141456.OAA09678@localhost> To: current@FreeBSD.org Subject: Updated notes on the VFS/VM system Sender: current-owner@FreeBSD.org Precedence: bulk Hey gang -- I thought that it would be nice to talk about the improvements to the FreeBSD VFS/VM for the 2.0.5 release. This is a follow-on to the notes that I released a few months ago. There is more additional background information in this version of the notes. By no means is this complete, but just wanted to let you know about some of the VM/VFS improvements that you are getting. I reiterate my original comments: I really believe that low level kernel things such as this are only enabling technology. Most of these things were changed to allow people to use the system for more and bigger applications, and hopefully, some day some of us will get together and write a FreeBSD kernel manual. :-). Things fixed in the VM/VFS system since 4.4-Lite by various FreeBSD contributors 1) Collapse problem fully eliminated Fairly complex code has been added to eliminate the growing swap space problem intrinsic in the MACH VM system used in 4.4-Lite. You will notice that the system uses much less swap space than it used to. (Earlier versions of FreeBSD had mods to help the situation, but the code in 2.0.5 contains a complete fix.) The problem is that when a parent creates a child by the fork(2) system call -- the address space is "cloned" through a copy-on-write (COW) mechanism. If both the parent and child modify their address spaces -- each will create their own copy of the modified memory owned by the parent before the fork(2) system call. Each process continues to hold a reference to the original memory residing in the parent. This reference is kept, because the original memory still contains pages that can be shared. The problem appears when the child exits, the reference count to the original memory does drop to one -- that is good. But there is no mechanism to properly merge the memory originally in the parent back into the parent if paging has occured on the original memory from the parent. This causes "orphan" memory (that can eventually get paged out) on some systems. In the original 4.4Lite code (and most 4.4Lite implementations that we know of, except for FreeBSD) there is no way to reclaim this swap-space or memory. On a heavily loaded system with significant paging this will eventually necessitate a reboot. 2) The pageout daemon is now very efficient The original pageout daemon was waken up gratuitously. When physical memory started being overcommited, the system would thrash. Also, the new FreeBSD pageout daemon does significant statistics on page usage, so that it doesn't free pages that are likely to be re-used. (The old one was too simple.) The clock algorithm (or a variation thereof) was originally used in 4.4Lite. The new algorithm is a most-often-used with an LRU component followed by a pure LRU. The most-often-used portion of the algorithm is used to select candidates for pages to be deactivated or placed onto the cache queue. The cache queue and inactive queue are "last chance" type queues. Whenever a page on a "last chance" queue is used, it is placed back onto the active queue. It is now much less likely that the pageout daemon will get rid of a page that is actively being used. Also, the pageout daemon does not need to be waken up nearly as often. 3) Pages are not freed as often A new page queue that has pages that can be easily re-used by user processes was added. The identities of the pages on the queue are not lost until they are reused. We still keep a free queue for interrupt code use and for pages that have lost their identity. This technique is used in other operating systems, and this gives the FreeBSD VM system more time to keep a page in memory. 4) The VM system now no longer gratuitiously wipes the page tables. When COW pages are created, previous usage is tracked at the VM level, making sure that gratuitious page protection is not done. This fix really helps large systems, where there was an O(n^2) type degradation. This degradation has been minimized. On large systems such as "wcarchive AKA: ftp.freebsd.org", the continued forking and execing of processes caused much unnecessary protection of the pages in read-only and COW sections of memory. The process of scanning the page tables and protecting them wiped the cache and in some circumstances, cause all processes that are sharing the memory to fault on next access. This enhancement should significantly improve the performance of WEB servers and other sites where there are many short-lived processes. Originally, we tried to help the situation by including some tightly crafted code in the pmap (machine dependent layer). We noticed some speed-ups but it took further analysis to determine the root-cause of the problem. It is a good thing to improve the pmap code, but the real problem lies in the upper layers of the VM system. There is now better tracking of page and object usage so that the lower level code is used much less often. 5) The VM system and buffer cache has been merged. Now mmap is fully coherent with the read/write system calls. This is an initial implementation, and the VOP_GETPAGE and VOP_PUTPAGE will be compatibly added soon (Probably V2.2). For example, a write to a file immediately causes the data to change immediately in the address space of a process that might have the file mapped. FreeBSD uses a scheme that is minimally invasive into the filesystems themselves. Gradually, there will be improvements in the interface that will require more changes in the lower-layers of the filesystems, for example to support VOP_GETPAGE and VOP_PUTPAGE. This will afford an improvement in efficiency in some circumstances, and support a much cleaner way than current methods of swapping onto files. 6) Dynamic sized buffer cache Along with the merged VM/buffer cache, the buffer cache now uses otherwise unused memory. It does not compete with memory that is likely to be needed in the near future. Additionally, the new code does not create dirty pages not associated with buffers, thereby limiting the number of dirty vfs created pages to the size of the buffer cache. Future enhancements will likely include page-flipping for normal read(2) system calls in certain circumstances. The way the buffer cache is now implemented -- this is very feasible. 7) The system now swaps. Swapping has historically been an unpleasant thing in UNIX-like OSes. Not only has FreeBSD implemented swapping, but has an intelligent policy as to the swappability of processes. Older UNIX-like OSes did not properly choose the correct processes to swap out. This caused problems with process scheduling. One effect of this is that once swapping occurs, processes would appear to go-to-sleep and system utilization would suffer. FreeBSD has an improved algorithm to significantly minimize this effect of processes appearing to go-to-sleep. An example of this is that you can run a program that gobbles memory. Older systems would swap out that process!!! FreeBSD resists that temptation. 8) The VM code does many fewer copies. Unfortunately, the standard 4.4Lite VM code copies all data paged in from files. FreeBSD copies very little of the RO data paged in from files, the only time that the system copies paged-in pages is for COW. The original behavior is a result of the buffer-cache orientation for filesystem I/O. With the advent of mmap and friends, this becomes a problem. The FreeBSD buffer-cache subsystem does not use additional anonymous memory for its buffers, it uses the memory that would have been originally mmaped, thereby eliminating the unnecessary copy. 9) Soft RSS limiting has been added. The system allows the system administrator to limit the RSS of processes. Originally, we had an implementation of hard limiting also. It is within an hour or two of work-time to make functional again... But, it's effect is not pleasant at all to the process being limited, and it was not considered very useful at the time. 10) The FreeBSD VM intelligently clusters pageins. Pageins are clustered VM-intelligent -- not limited to the VFS (I/O optimized) clustering methods. The VFS style clustering is not as useful for pageins because of the likelihood of pages needing to be faulted in reverse order. It definitely does help to use the VFS style clustering, but the VM style clustering helps more. 11) Vastly improved the flushing of dirty vnode-backed pages Since mmap is more likely to be used now, it was necessary to create a more efficient pageout of dirty pages. The current (and still being used) scheme of managing the pages in vm objects is not friendly to many operations needed by the vm system. Prefaulting and vnode pageouts could be done much more efficiently than current code allows. Modifications have already been made to FreeBSD V2.0.5 to help this situation, but further work is being done to fix the access methods to the vm page data structures. 12) VFS_BIO bounce buffering has been added. A fairly architecture-neutral, non-invasive bounce-buffer scheme has been added to vfs_bio (actually vm_machdep for now.) Note that in general 1-3 lines of code needs to be added to each block device driver that needs bouncing. Machines such as ISA based iX86's have problems addressing certain regions of memory with dma devices. Rather than segmenting memory into dmaable/non-dmaable segments, and because of the significant complications that arise when implementing such schemes, the FreeBSD scheme of managing non-dmaable memory is to "bounce" data though the dma-able memory regions. The current scheme is mostly usable for strategy routines for block devices, but there are entry points available for other types of memory needs. Examples can be found in the SCSI code. One major goal of the FreeBSD bounce code is to minimize the effect on existing and future device drivers. 13) More efficient ordering of buffers in the vnode dirty list Makes sync work better if there are lots of delayed write buffers. This is mostly helpful if one modifies the ufs_readwrite to retain delayed write buffers as opposed to immediately queueing async writes. 14) Much better vfs name caching. A hashing scheme was added to vastly improve the performance on large systems. 15) New VFS cluster code. The original cluster code, although working, appeared to violate some layering and depended on a large kva space for the clustered I/O buffers. So for a large number of buffers, too much kva was required. Special buffers are now used to support clustering, thereby minimizing kva space requirements. This helps both CISC and some RISC architectures (such as R3000/R4000), where each 2MB or 4MB costs something significant (like page table pages or TLB entries.) In the original 4.4Lite scheme, much more kva was need to support a given number of buffers than what appears to be necessary. In order to support a cluster size of 64K, each buffer in the buffer cache needed to have 64K of kva allocated to it. Of course, this does not take up real memory directly, but it does take up other fairly scarce resources, and those are kernel virtual memory and page tables. 1000 buffers takes up 64MB of kernel space, for perhaps only 8MB of buffer space!!!! Ouch! The FreeBSD scheme uses a limited number of buffers that have pre-assigned kernel virtual memory for clustering (and certain other) purposes. This allows the FreeBSD buffer size to be 8KB or 16KB, instead of 64KB, and still perform clustering effectively. 16) Reusable page-table memory. The original 4.4Lite implementation did not afford pageable (really reusable memory) page-tables for X86 architectures. This can be very problematical, causing much unnecessary memory usage. In fact, the original code did not free unused page tables for a running process at all. So if the page tables were allocated, they were wired permanently into memory until the process exited. FreeBSD can free unused page tables as needed. John dyson@root.com From owner-freebsd-current Sun May 14 15:05:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA01994 for current-outgoing; Sun, 14 May 1995 15:05:26 -0700 Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA01932 for ; Sun, 14 May 1995 15:04:14 -0700 Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id WAA14963 for current@freebsd.org; Sun, 14 May 1995 22:57:47 +0100 Date: Sun, 14 May 1995 22:57:47 +0100 From: Mark Valentine Message-Id: <199505142157.WAA14963@linus.demon.co.uk> X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: current@FreeBSD.org Subject: MAKEDEV and device permissions Sender: current-owner@FreeBSD.org Precedence: bulk MAKEDEV seems to be a bit confused about how to set the permissions on several devices (e.g. fd*). It temporarily uses a less restrictive umask than the one it starts off with, but then chmods the devices to be more restricted anyway. In the case of joy*, it doesn't set the umask back. (Apart from this last bit, the problem is only one of internal consistency.) Suggested fix: (policy) decide which one is right. Make the chmod calls agree, and remove the umask adjustments. (Personally, I prefer devices such as floppy and tape to be operator-writeable, but rc.local can handle non-default policy.) To be consistent, modify the parts which rely only on the umask to use chmod instead. The enclosed patch is one way to go about it. I've also removed the umask calls around the invocation of MAKEDEV.local, since the default MAKEDEV.local sets the umask explicitly anyway. The worst case where "local" isn't the last argument to MAKEDEV and MAKEDEV.local leaves an inappropriate umask is pretty obscure, expecially if MAKEDEV no longer relies on the umask. The labpc* stuff could probably be a bit more explicit, since the devices are group writeable, but the group is defaulted. In the case of the audio devices, perhaps we need a hook into the login process to enable at least these to be readable/writeable by whoever logs in on the "console". (I've left them relying on umask here.) This patch is against: # $Id: MAKEDEV,v 1.91 1995/05/07 23:04:03 ache Exp $ It also fixes a minor complaint when creating the matcd devices. Mark. --- /dev/MAKEDEV Tue May 9 23:08:39 1995 +++ /tmp/MAKEDEV Sun May 14 22:32:52 1995 @@ -198,7 +198,7 @@ # Create device files for new Archive/Wangtek QIC-02 tape driver (vak) wt*) - umask 7 ; u=`expr $i : '..\(.*\)'` + u=`expr $i : '..\(.*\)'` if [ x$u = x ]; then u=0; fi rm -f r[Ww]t$u nr[Ww]t$u r[Ww]t$u[a-f] nr[Ww]t$u[a-f] mknod rwt${u} c 10 `expr 0 + $u` # default density, 512b blocks @@ -216,11 +216,11 @@ # mknod rwt${u}f c 10 `expr 48 + $u` # 600 megabytes? # mknod nrwt${u}f c 10 `expr 52 + $u` chown root.operator r[Ww]t$u nr[Ww]t$u r[Ww]t$u[a-f] nr[Ww]t$u[a-f] - umask 77 + chmod 600 r[Ww]t$u nr[Ww]t$u r[Ww]t$u[a-f] nr[Ww]t$u[a-f] ;; fd*) - umask 2 ; unit=`expr $i : '..\(.*\)'` + unit=`expr $i : '..\(.*\)'` name=fd; blk=2; chr=9; rm -f $name$unit* r$name$unit* case $unit in @@ -300,12 +300,11 @@ echo bad unit for disk in: $i ;; esac - umask 77 ;; ft*) - umask 2 ; unit=`expr $i : '..\(.*\)'` + unit=`expr $i : '..\(.*\)'` name=ft; blk=2; chr=9; rm -f $name$unit* r$name$unit* case $unit in @@ -321,12 +320,10 @@ echo bad unit for tape in: $i ;; esac - umask 77 ;; # Individual slices. sd*s*|vn*s*|wd*s*) - umask 37 case $i in sd*s*) name=sd; blk=4; chr=13;; wd*s*) name=wd; blk=0; chr=3;; @@ -369,6 +366,7 @@ esac chgrp operator $name$unit$slicename* \ r$name$unit$slicename* + chmod 640 $name$unit$slicename* r$name$unit$slicename ;; *) echo bad slice for disk in: $i @@ -379,11 +377,9 @@ echo bad unit for disk in: $i "(unit=$unit, slice=$slice, part=$part)" ;; esac - umask 77 ;; sd*|vn*|wd*) - umask 37 case $i in sd*) name=sd; blk=4; chr=13;; wd*) name=wd; blk=0; chr=3;; @@ -408,13 +404,14 @@ echo bad unit for disk in: $i ;; esac - umask 77 ;; uk*) unit=`expr $i : 'uk\(.*\)'` rm -f uk$unit mknod uk$unit c 31 $unit + chgrp operator uk$unit + chmod 640 uk$unit ;; worm*) @@ -426,6 +423,7 @@ name=worm rm -f r${name}${unit} mknod r${name}${unit} c $chr ${unit} + chmod 600 r${name}${unit} rm -f r${name}${unit}.ctl mknod r${name}${unit}.ctl c $chr `expr $unit + $scsictl ` chmod 600 r${name}${unit}.ctl @@ -442,6 +440,7 @@ unit=`expr $unit + 1 - 1` rm -f ${name}${unit} mknod ${name}${unit} c $chr $unit + chmod 600 ${name}${unit} rm -f ${name}${unit}.ctl mknod ${name}${unit}.ctl c $chr `expr $unit + $scsictl ` chmod 600 ${name}${unit}.ctl @@ -464,27 +463,27 @@ esac case $class in 0|1|2|3|4|5|6|7) - umask 0 eval `echo $offset $name | awk ' { b=$1; n=$2 } END { \ for (i = 0; i < 32; i++) { c = substr("0123456789abcdefghijklmnopqrstuv", i + 1, 1); \ printf("rm -f tty%s%s pty%s%s; \ mknod tty%s%s c 5 %d; \ mknod pty%s%s c 6 %d; \ - chown root.wheel tty%s%s pty%s%s;", \ + chown root.wheel tty%s%s pty%s%s; \ + chmod 666 tty%s%s pty%s%s;", \ n, c, n, c, \ n, c, b+i, \ n, c, b+i, \ + n, c, n, c, \ n, c, n, c); \ } \ }'` - umask 77 ;; esac ;; st*) - umask 2 ; unit=`expr $i : '..\(.*\)'` + unit=`expr $i : '..\(.*\)'` chr=14; #remove old stype names @@ -524,11 +523,10 @@ echo bad unit for tape in: $i ;; esac - umask 77 ;; ch*) - umask 2 ; unit=`expr $i : '..\(.*\)'` + unit=`expr $i : '..\(.*\)'` case $i in ch*) name=ch; chr=17;; esac @@ -546,11 +544,9 @@ echo bad unit for media changer in: $i ;; esac - umask 77 ;; cd*|mcd*|scd*) - umask 2 ; case $i in cd*) unit=`expr $i : '..\(.*\)'`; name=cd; blk=6; chr=15;; mcd*) unit=`expr $i : '...\(.*\)'`; name=mcd; blk=7; chr=29;; @@ -577,15 +573,14 @@ echo bad unit for disk in: $i ;; esac - umask 77 ;; matcd*) - umask 2 ; case $i in matcd*) unit=`expr $i : '.....\(.*\)'`; name=matcd; blk=17; chr=46;; esac rm -f $name$unit? r$name$unit? + rm -f $name${unit}l? r$name${unit}l? case $unit in 0|1|2|3|4|5|6|7|8|9|10|11|12|13|14|15) mknod ${name}${unit}a b $blk `expr $unit '*' 8 + 0` @@ -606,7 +601,6 @@ echo bad unit for disk in: $i ;; esac - umask 77 ;; lpt*) @@ -617,6 +611,8 @@ mknod lpctl$unit c 16 `expr $unit + 128` chown root.wheel lpt$unit chown root.wheel lpctl$unit + chmod 600 lpt$unit + chmod 600 lpctl$unit ;; tw*) @@ -624,6 +620,7 @@ rm -f tw$unit mknod tw$unit c 19 $unit chown root.operator tw$unit + chmod 600 tw$unit ;; # Use this to create virtual consoles for syscons, pcvt or codrv @@ -635,8 +632,9 @@ eval `echo ${chr} ${units} | awk ' { c=$1; n=$2 } END { for (i = 0; i < n; i++) printf("rm -f ttyv%01x; mknod ttyv%01x c %d %d; \ - chown root.wheel ttyv%01x;", \ - i, i, c, i, i); }'` + chown root.wheel ttyv%01x; \ + chmod 600 ttyv%01x;", \ + i, i, c, i, i, i, i); }'` ln -fs ttyv0 vga # XXX X still needs this pccons relic ;; @@ -645,16 +643,17 @@ rm -f bpf$unit mknod bpf$unit c 23 $unit chown root.wheel bpf$unit + chmod 600 bpf$unit ;; speaker) rm -f speaker mknod speaker c 26 0 chown root.wheel speaker + chmod 600 speaker ;; cuaa?|cua?) - umask 7 unit=`expr $i : 'cua.*\(.\)$'` rm -f cua*a$unit m=`ttyminor $unit` @@ -662,7 +661,7 @@ mknod cuaia$unit c 28 `expr $m + 32 + 128` mknod cuala$unit c 28 `expr $m + 64 + 128` chown uucp.dialer cua*a$unit - umask 77 + chmod 660 cua*a$unit ;; tty0?|ttyd?|tty?) @@ -673,10 +672,10 @@ mknod ttyid$unit c 28 `expr $m + 32` mknod ttyld$unit c 28 `expr $m + 64` chown root.wheel tty*d$unit + chmod 600 tty*d$unit ;; cuac?) - umask 7 unit=`expr $i : 'cua.*\(.\)$'` rm -f cua*c$unit m=`ttyminor $unit` @@ -684,7 +683,7 @@ mknod cuaic$unit c 48 `expr $m + 32 + 128` mknod cualc$unit c 48 `expr $m + 64 + 128` chown uucp.dialer cua*c$unit - umask 77 + chmod 660 cua*c$unit ;; ttyc?) @@ -695,18 +694,18 @@ mknod ttyic$unit c 48 `expr $m + 32` mknod ttylc$unit c 48 `expr $m + 64` chown root.wheel tty*c$unit + chmod 600 tty*c$unit ;; # RISCom8 'rc' driver entries cuam?) - umask 7 unit=`expr $i : 'cua.*\(.\)$'` rm -f cuam$unit m=`ttyminor $unit` mknod cuam$unit c 63 `expr $m + 128` chown uucp.dialer cuam$unit - umask 77 + chmod 660 cuam$unit ;; ttym?) @@ -715,6 +714,7 @@ m=`ttyminor $unit` mknod ttym$unit c 63 $m chown root.wheel ttym$unit + chmod 600 ttym$unit ;; mse*) @@ -723,6 +723,7 @@ rm -f mse$unit mknod mse$unit c $chr `expr $unit '*' 2 + 1` # non-blocking for X11 chown root.wheel mse$unit + chmod 600 mse$unit ;; psm*) @@ -731,6 +732,7 @@ rm -f psm$unit mknod psm$unit c $chr `expr $unit '*' 2 + 1` # non-blocking for X11 chown root.wheel psm$unit + chmod 600 psm$unit ;; mouse*) @@ -747,6 +749,7 @@ mknod pcaudio c 24 0 mknod pcaudioctl c 24 128 chown root.wheel pcaudio pcaudioctl + chmod 600 pcaudio pcaudioctl ;; socksys) @@ -837,16 +840,17 @@ rm -f $i mknod $i c 42 $unit chown uucp.wheel $i + chmod 600 $i ;; cronyx) rm -f cronyx mknod cronyx c 42 63 chown root.wheel cronyx + chmod 600 cronyx ;; joy) - umask 2 rm -f joy0 joy1 mknod joy0 c 51 0 mknod joy1 c 51 1 @@ -865,6 +869,7 @@ rm -f tun$unit mknod tun$unit c 52 $unit chown uucp.dialer tun$unit + chmod 600 tun$unit ;; snp?) @@ -937,7 +942,6 @@ # labpcdio: Digital in and Digital out. # labpc*) - umask 7 case $i in labpcaio*) name=labpcaio @@ -963,25 +967,24 @@ 0|1|2|3|4|5|6|7) rm -f $name$unit mknod $name$unit c 66 `expr $offset + $unit ` + chmod 660 $name$unit ;; all) for i in $all do rm -f $name$i mknod $name$i c 66 `expr $offset + $i ` + chmod 660 $name$i done ;; *) echo "No such LabPC unit: $unit" ;; esac - umask 77 ;; local) - umask 0 # XXX should be elsewhere sh MAKEDEV.local - umask 77 ;; *) From owner-freebsd-current Sun May 14 16:11:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA03589 for current-outgoing; Sun, 14 May 1995 16:11:47 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA03583 for ; Sun, 14 May 1995 16:11:43 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id JAA07026; Mon, 15 May 1995 09:09:19 +1000 Date: Mon, 15 May 1995 09:09:19 +1000 From: Bruce Evans Message-Id: <199505142309.JAA07026@godzilla.zeta.org.au> To: current@FreeBSD.org, mark@linus.demon.co.uk Subject: Re: MAKEDEV and device permissions Sender: current-owner@FreeBSD.org Precedence: bulk >MAKEDEV seems to be a bit confused about how to set the permissions >on several devices (e.g. fd*). It temporarily uses a less restrictive >umask than the one it starts off with, but then chmods the devices >to be more restricted anyway. In the case of joy*, it doesn't set >the umask back. (Apart from this last bit, the problem is only one >of internal consistency.) >Suggested fix: (policy) decide which one is right. Make the chmod >calls agree, and remove the umask adjustments. I've been changing it the other way, to use umask consistently. MAKEDEV is very slow, and umask is much faster than chmod. >(Personally, I prefer >devices such as floppy and tape to be operator-writeable, but rc.local >can handle non-default policy.) To be consistent, modify the parts Tapes were always supposed to be operator-writeable. This will be fixed in 2.0.5. I have the raw floppy operator-writeable locally too, but I don't think it is right for general use because floppies can be mounted. Bruce From owner-freebsd-current Sun May 14 23:07:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA18087 for current-outgoing; Sun, 14 May 1995 23:07:06 -0700 Received: from vinkku.hut.fi (vode@vinkku.hut.fi [130.233.245.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA18074 for ; Sun, 14 May 1995 23:07:04 -0700 Received: (from vode@localhost) by vinkku.hut.fi (8.6.11/8.6.7) id JAA05957; Mon, 15 May 1995 09:06:33 +0300 Date: Mon, 15 May 1995 09:06:33 +0300 From: Kai Vorma Message-Id: <199505150606.JAA05957@vinkku.hut.fi> To: "Rodney W. Grimes" Cc: current@FreeBSD.org Subject: Re: A few things.. In-Reply-To: <199505141754.KAA03873@gndrsh.aac.dev.com> References: <199505141649.TAA20757@vinkku.hut.fi> <199505141754.KAA03873@gndrsh.aac.dev.com> Reply-To: Kai.Vorma@hut.fi Sender: current-owner@FreeBSD.org Precedence: bulk Rodney W. Grimes writes: > > Before hanging your machine does it manage to output the string: > > Keyboard reset did not work, attempting CPU shutdown No, it prints "Rebooting.." and then hangs. > What happens if you change this: > outb(IO_KBD + 4, 0xFE); > > to this: > outb(IO_KBD + 4, 0xFC); Didn't help - it still hangs sometimes. ..vode From owner-freebsd-current Mon May 15 00:29:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA20538 for current-outgoing; Mon, 15 May 1995 00:29:24 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA20532 for ; Mon, 15 May 1995 00:29:20 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id AAA05374; Mon, 15 May 1995 00:26:26 -0700 From: "Rodney W. Grimes" Message-Id: <199505150726.AAA05374@gndrsh.aac.dev.com> Subject: Re: A few things.. To: Kai.Vorma@hut.fi Date: Mon, 15 May 1995 00:26:25 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505150606.JAA05957@vinkku.hut.fi> from "Kai Vorma" at May 15, 95 09:06:33 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 623 Sender: current-owner@FreeBSD.org Precedence: bulk > > Rodney W. Grimes writes: > > > > Before hanging your machine does it manage to output the string: > > > > Keyboard reset did not work, attempting CPU shutdown > > No, it prints "Rebooting.." and then hangs. > > > What happens if you change this: > > outb(IO_KBD + 4, 0xFE); > > > > to this: > > outb(IO_KBD + 4, 0xFC); > > Didn't help - it still hangs sometimes. > And if you completely remove it, then it reboots every time without hanging? -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Mon May 15 02:56:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA24129 for current-outgoing; Mon, 15 May 1995 02:56:09 -0700 Received: from easynet.com (easyr.easynet.net [198.67.38.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA24121 for ; Mon, 15 May 1995 02:56:05 -0700 Received: by easynet.com (Smail3.1.28.1 #7) id m0sAwsd-000rdbC; Mon, 15 May 95 02:56 WET DST Message-Id: From: brian@mediacity.com (Brian Litzinger) Subject: keyboard troubles To: freebsd-current@FreeBSD.org Date: Mon, 15 May 1995 02:56:03 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 745 Sender: current-owner@FreeBSD.org Precedence: bulk On about a 2 day old -current, I've run into a little problem. The power went out on a system, and when it rebooted one of the filesystems was corrupted in a way that the auto fsck gave up and I got the 'blah blah or press enter for shell:' prompt. Unfortuntely, the keyboard did not respond. Not even the numlock light would change. Before that point the keyboard had worked fine, including typing '/kernel -s'. I tried a different keyboard and when the system got to the same spot and lights on the keyboard starting blinking on and off and spurious garbage key strokes we being generated all by themselves. I then rebooted with a kernel that was approximately a week older and everything worked fine. Brian Litzinger brian@easynet.com From owner-freebsd-current Mon May 15 03:05:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA24575 for current-outgoing; Mon, 15 May 1995 03:05:54 -0700 Received: from jabba.fdn.org (jabba.fdn.org [193.55.4.70]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA24569 ; Mon, 15 May 1995 03:05:48 -0700 Received: (from uucp@localhost) by jabba.fdn.org (8.6.8/8.6.9) with UUCP id MAA06686; Mon, 15 May 1995 12:05:39 +0200 Received: (pb@localhost) by fasterix.frmug.fr.net (8.6.11/fasterix-941011) id LAA05342; Mon, 15 May 1995 08:31:52 +0200 From: Pierre Beyssac Message-Id: <199505150631.LAA05342@fasterix.frmug.fr.net> Subject: panic in rtfree(): even more info To: freebsd-bugs@freefall.cdrom.com Date: Mon, 15 May 1995 08:31:51 +0200 (MET DST) Cc: freebsd-current@freefall.cdrom.com X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 2394 Sender: current-owner@FreeBSD.org Precedence: bulk More info on the rtfree() panic. The problems seem due to Friday's patch to rtsock.c. I reversed part of this patch and the problems went away. Here are the diffs between the "official" current rtsock.c and the one I use. This is not actually a fix, rather a patch to reverse most of Friday's change. Certainly not all of this is necessary, I provide this merely for info and will slowly reintegrate the -current rtsock.c to see when the rtfree panic reappears. --- rtsock.c.ctm Thu May 11 09:39:37 1995 +++ rtsock.c Mon May 15 00:23:43 1995 @@ -185,38 +185,64 @@ if (error == 0 && saved_nrt) { rt_setmetrics(rtm->rtm_inits, &rtm->rtm_rmx, &saved_nrt->rt_rmx); saved_nrt->rt_refcnt--; saved_nrt->rt_genmask = genmask; } break; case RTM_DELETE: error = rtrequest(RTM_DELETE, dst, gate, netmask, +#if 1 + rtm->rtm_flags, (struct rtentry **)0); +#else /* RTFREE_BUG */ rtm->rtm_flags, &saved_nrt); if (error == 0) { if ((rt = saved_nrt)->rt_refcnt <= 0) rt->rt_refcnt++; goto report; } +#endif /* RTFREE_BUG */ break; case RTM_GET: case RTM_CHANGE: case RTM_LOCK: +#if 1 + rt = rtalloc1(dst, 0, 0UL); + if (rt == 0) +#else /* RTFREE_BUG */ if ((rnh = rt_tables[dst->sa_family]) == 0) { senderr(EAFNOSUPPORT); } else if (rt = (struct rtentry *) rnh->rnh_lookup(dst, netmask, rnh)) rt->rt_refcnt++; else +#endif /* RTFREE_BUG */ senderr(ESRCH); +#if 1 + if (rtm->rtm_type != RTM_GET) {/* XXX: too grotty */ + struct radix_node *rn; + + if (Bcmp(dst, rt_key(rt), dst->sa_len) != 0) + senderr(ESRCH); + if (netmask && (rn = rn_search(netmask, + mask_rnhead->rnh_treetop))) + netmask = (struct sockaddr *)rn->rn_key; + for (rn = rt->rt_nodes; rn; rn = rn->rn_dupedkey) + if (netmask == (struct sockaddr *)rn->rn_mask) + break; + if (rn == 0) + senderr(ETOOMANYREFS); + rt = (struct rtentry *)rn; + } +#endif /* not RTFREE_BUG */ switch(rtm->rtm_type) { case RTM_GET: report: dst = rt_key(rt); gate = rt->rt_gateway; netmask = rt_mask(rt); genmask = rt->rt_genmask; if (rtm->rtm_addrs & (RTA_IFP | RTA_IFA)) { ifp = rt->rt_ifp; -- Pierre Beyssac pb@fasterix.frmug.fr.net pb@fasterix.fdn.fr FreeBSD, NetBSD, Linux -- Il y a moins bien, mais c'est plus cher. You can also get less bang for more bucks. (translation F. Berjon) From owner-freebsd-current Mon May 15 08:37:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA04947 for current-outgoing; Mon, 15 May 1995 08:37:56 -0700 Received: from ns1.win.net (NS1.WIN.NET [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA04941 for ; Mon, 15 May 1995 08:37:54 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id LAA17284 for current@freebsd.org; Mon, 15 May 1995 11:41:27 -0400 From: Mark Hittinger Message-Id: <199505151541.LAA17284@ns1.win.net> Subject: _swdevt (multiply defined) To: current@FreeBSD.org Date: Mon, 15 May 1995 11:41:25 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 58 Sender: current-owner@FreeBSD.org Precedence: bulk _swdevt (multiply defined) in vm_swap and swapkernel FYI From owner-freebsd-current Mon May 15 09:39:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA06429 for current-outgoing; Mon, 15 May 1995 09:39:30 -0700 Received: from narnia.hip.berkeley.edu (narnia.HIP.Berkeley.EDU [136.152.64.57]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA06421 for ; Mon, 15 May 1995 09:39:27 -0700 Received: from localhost (localhost [127.0.0.1]) by narnia.hip.berkeley.edu (8.6.11/8.6.9) with SMTP id JAA00195; Mon, 15 May 1995 09:40:14 -0700 Message-Id: <199505151640.JAA00195@narnia.hip.berkeley.edu> X-Authentication-Warning: narnia.hip.berkeley.edu: Host localhost didn't use HELO protocol To: Mark Hittinger cc: current@FreeBSD.org Subject: Re: _swdevt (multiply defined) In-reply-to: Your message of "Mon, 15 May 1995 11:41:25 EDT." <199505151541.LAA17284@ns1.win.net> Date: Mon, 15 May 1995 09:40:14 -0700 From: "Justin T. Gibbs" Sender: current-owner@FreeBSD.org Precedence: bulk >_swdevt (multiply defined) in vm_swap and swapkernel FYI Rebuild config. -- Justin T. Gibbs ============================================== TCS Instructional Group - Programmer/Analyst 1 Cory | Po | Danube | Volga | Parker | Torus ============================================== From owner-freebsd-current Mon May 15 11:17:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA09740 for current-outgoing; Mon, 15 May 1995 11:17:02 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA09733 for ; Mon, 15 May 1995 11:17:01 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA10141; Mon, 15 May 95 12:09:42 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505151809.AA10141@cs.weber.edu> Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H To: bde@zeta.org.au (Bruce Evans) Date: Mon, 15 May 95 12:09:41 MDT Cc: hsu@clinet.fi, current@FreeBSD.org In-Reply-To: <199505141409.AAA28510@godzilla.zeta.org.au> from "Bruce Evans" at May 15, 95 00:09:02 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > >The termcap entry for xterm is false, it says that erase key sends ^H, > >while most systems send ^?. > > It has to be right for the configuration actually being used. This > probably requires putting the full termcap entry in the environment. > I don't know what X does. All systems send XK_BackSpace if the key is labeled "Backspace" and XK_Delete if it's labelled "Delete" and XK_KP_Delete if it's labelled "Delete" and lives on a keypad instead of elsewhere. Most X terminals interpret this as a request to send an ASCII Backspace character (^H, 0x08) to the slave side of the PTY they are using. You can change this interpretation by modifying your .Xdefaults, like follows: xterm*TtyModes: erase ^? Of course, this isn't recommended, since in principle, the key should send the ASCII kvalue that its keycap label implies it sends. Xterm gets it's tty settings from the default device that the X server is run on, which is inherited by the xterms as /dev/tty before they go slave-side. I would say that your console is configured incorrectly by default to send and ASCII 0x7f (delete, ^?) instead of an ASCII backspace for your key labelled "Backspace", and that the default tty modes for your console have also been hacked so that it expects this character as the erase character, either because you are really supposed to be using the "Delete" key, or because rather than fixing the console modes, someone "fixed" the keycode returned by the "Backspace" labelled key to the console input queue. The Telnet and Rlogin arguments don't hold water here because the erase character is a negotiated option. The remote Xterm argument doesn't hold water here because the value would be an interned atom and thus be server specific if you were using xrdb like you are supposed to when running X. Your console tty modes are manages in /etc/gettydefs or /etc/gettytab, depending on if you are running mgetty or the normal (default) getty. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon May 15 11:42:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA10591 for current-outgoing; Mon, 15 May 1995 11:42:36 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA10585 for ; Mon, 15 May 1995 11:42:35 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA18796; Mon, 15 May 1995 14:42:30 -0400 Date: Mon, 15 May 1995 14:42:30 -0400 From: Garrett Wollman Message-Id: <9505151842.AA18796@halloran-eldar.lcs.mit.edu> To: terry@cs.weber.edu (Terry Lambert) Cc: current@FreeBSD.org Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H In-Reply-To: <9505151809.AA10141@cs.weber.edu> References: <199505141409.AAA28510@godzilla.zeta.org.au> <9505151809.AA10141@cs.weber.edu> Sender: current-owner@FreeBSD.org Precedence: bulk < Most X terminals interpret this as a request to send an ASCII Backspace > character (^H, 0x08) to the slave side of the PTY they are using. > You can change this interpretation by modifying your .Xdefaults, like > follows: > xterm*TtyModes: erase ^? > Of course, this isn't recommended, since in principle, the key should > send the ASCII kvalue that its keycap label implies it sends. Of course, not all keyboards are the same. My LK-401 has a keycap labeled ___ / X| \__| and I defy you to state definitively that this symbol implies any ASCII code at all. DEC being typically obnoxious decided to make it send BS; I use this magic to make it send something sensible: xmodmap - << EOF keysym BackSpace = Delete # more stuff goes here EOF -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Mon May 15 11:46:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA10713 for current-outgoing; Mon, 15 May 1995 11:46:47 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA10703 for ; Mon, 15 May 1995 11:46:46 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA17457; Mon, 15 May 1995 11:46:32 -0700 From: Poul-Henning Kamp Message-Id: <199505151846.LAA17457@ref.tfs.com> Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Mon, 15 May 1995 11:46:32 -0700 (PDT) Cc: terry@cs.weber.edu, current@FreeBSD.org In-Reply-To: <9505151842.AA18796@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at May 15, 95 02:42:30 pm Content-Type: text Content-Length: 673 Sender: current-owner@FreeBSD.org Precedence: bulk > > Of course, this isn't recommended, since in principle, the key should > > send the ASCII kvalue that its keycap label implies it sends. > > Of course, not all keyboards are the same. My LK-401 has a keycap > labeled > ___ > / X| > \__| > > and I defy you to state definitively that this symbol implies any > ASCII code at all. DEC being typically obnoxious decided to make it > send BS; I use this magic to make it send something sensible: It should send an 'X' of course :-) -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Mon May 15 12:00:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA11241 for current-outgoing; Mon, 15 May 1995 12:00:14 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA11235 for ; Mon, 15 May 1995 12:00:12 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA04335; Mon, 15 May 95 20:59:33 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id VAA28278 for freebsd-current@freefall.cdrom.com; Mon, 15 May 1995 21:10:50 +0200 Date: Mon, 15 May 1995 21:10:50 +0200 From: "Christoph P. Kukulies" Message-Id: <199505151910.VAA28278@gilberto.physik.rwth-aachen.de> To: freebsd-current@freefall.cdrom.com Subject: reboot probs and keyboard reset Sender: current-owner@FreeBSD.org Precedence: bulk Since my little gateway box had so much trouble rebooting (Hercules, 386-DX25) - it always hung after a sync ; reboot and that's bad for a dial-in machine - I swapped case and MB, put all the cards on the new MB (386/40) and still have this reboot hang problem. But this time I saw a message flash for a short moment, saying that keyboard rest failed (or something). Any clues? --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Mon May 15 12:05:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA11581 for current-outgoing; Mon, 15 May 1995 12:05:59 -0700 Received: from vinkku.hut.fi (vode@vinkku.hut.fi [130.233.245.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA11564 for ; Mon, 15 May 1995 12:05:53 -0700 Received: (from vode@localhost) by vinkku.hut.fi (8.6.11/8.6.7) id WAA12249; Mon, 15 May 1995 22:05:19 +0300 Date: Mon, 15 May 1995 22:05:19 +0300 From: Kai Vorma Message-Id: <199505151905.WAA12249@vinkku.hut.fi> To: "Rodney W. Grimes" Cc: current@FreeBSD.org Subject: Re: A few things.. In-Reply-To: <199505150726.AAA05374@gndrsh.aac.dev.com> References: <199505150606.JAA05957@vinkku.hut.fi> <199505150726.AAA05374@gndrsh.aac.dev.com> Reply-To: Kai.Vorma@hut.fi Sender: current-owner@FreeBSD.org Precedence: bulk Rodney W. Grimes writes: > And if you completely remove it, then it reboots every time without > hanging? Yes. ..vode From owner-freebsd-current Mon May 15 13:42:09 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA15358 for current-outgoing; Mon, 15 May 1995 13:42:09 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA15334 for ; Mon, 15 May 1995 13:41:59 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA09351; Tue, 16 May 1995 06:37:52 +1000 Date: Tue, 16 May 1995 06:37:52 +1000 From: Bruce Evans Message-Id: <199505152037.GAA09351@godzilla.zeta.org.au> To: pst@Shockwave.COM Subject: Re: misc/423: security of sound devices Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >The right model is to do the same thing that we do with /dev/console. If >you're logged in at the console (or local X server), you own the sound devices. >When you logout, they should go back to root.sound ownership, with no world >access. This model applies to other devices physically near the console. Joysticks. Floppies? Scanners. Printers? Bruce From owner-freebsd-current Mon May 15 13:49:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA15694 for current-outgoing; Mon, 15 May 1995 13:49:24 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA15688 for ; Mon, 15 May 1995 13:49:22 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA17968; Mon, 15 May 1995 13:49:05 -0700 From: Poul-Henning Kamp Message-Id: <199505152049.NAA17968@ref.tfs.com> Subject: Re: misc/423: security of sound devices To: bde@zeta.org.au (Bruce Evans) Date: Mon, 15 May 1995 13:49:05 -0700 (PDT) Cc: pst@Shockwave.COM, current@FreeBSD.org In-Reply-To: <199505152037.GAA09351@godzilla.zeta.org.au> from "Bruce Evans" at May 16, 95 06:37:52 am Content-Type: text Content-Length: 668 Sender: current-owner@FreeBSD.org Precedence: bulk > >The right model is to do the same thing that we do with /dev/console. If > >you're logged in at the console (or local X server), you own the sound devices. > >When you logout, they should go back to root.sound ownership, with no world > >access. > > This model applies to other devices physically near the console. Joysticks. > Floppies? Scanners. Printers? This can be done with devfs I presume, given that we need to make the right kind of hacks^H^H^H^H^H links in the code. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Mon May 15 13:50:43 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA15757 for current-outgoing; Mon, 15 May 1995 13:50:43 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA15751 for ; Mon, 15 May 1995 13:50:39 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA07389; Mon, 15 May 1995 13:49:58 -0700 From: "Rodney W. Grimes" Message-Id: <199505152049.NAA07389@gndrsh.aac.dev.com> Subject: Re: misc/423: security of sound devices To: bde@zeta.org.au (Bruce Evans) Date: Mon, 15 May 1995 13:49:57 -0700 (PDT) Cc: pst@Shockwave.COM, current@FreeBSD.org In-Reply-To: <199505152037.GAA09351@godzilla.zeta.org.au> from "Bruce Evans" at May 16, 95 06:37:52 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 638 Sender: current-owner@FreeBSD.org Precedence: bulk > > >The right model is to do the same thing that we do with /dev/console. If > >you're logged in at the console (or local X server), you own the sound devices. > >When you logout, they should go back to root.sound ownership, with no world > >access. > > This model applies to other devices physically near the console. Joysticks. > Floppies? Scanners. Printers? Not printers, they should be under the control of lpd which already handles the device access issue, or should. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Mon May 15 14:15:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA16636 for current-outgoing; Mon, 15 May 1995 14:15:24 -0700 Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA16622 for ; Mon, 15 May 1995 14:15:12 -0700 Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id WAA02447; Mon, 15 May 1995 22:14:31 +0100 Date: Mon, 15 May 1995 22:14:31 +0100 From: Mark Valentine Message-Id: <199505152114.WAA02447@linus.demon.co.uk> In-Reply-To: Bruce Evans's message of May 15, 9:09am X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bruce Evans , current@FreeBSD.org Subject: Re: MAKEDEV and device permissions Sender: current-owner@FreeBSD.org Precedence: bulk > From: Bruce Evans > Date: Mon 15 May, 1995 > Subject: Re: MAKEDEV and device permissions > >MAKEDEV seems to be a bit confused about how to set the permissions > >on several devices (e.g. fd*). It temporarily uses a less restrictive > >umask than the one it starts off with, but then chmods the devices > >to be more restricted anyway. In the case of joy*, it doesn't set > >the umask back. (Apart from this last bit, the problem is only one > >of internal consistency.) > > >Suggested fix: (policy) decide which one is right. Make the chmod > >calls agree, and remove the umask adjustments. > > I've been changing it the other way, to use umask consistently. > MAKEDEV is very slow, and umask is much faster than chmod. I would agree with the performance argument if it were significant or if there were no other factor involved. However, in my opinion it's more important to make scripts like MAKEDEV as obvious as possible to reduce the chance that security holes creep in. I find it easier to read device modes directly than having to work out octal complements on the fly. Rod showed me a candidate patch which seemed to confuse umasks with modes (in favour of modes :-), which resulted in some calls to "umask 37" and some to "umask 026" to do the same thing... > Tapes were always supposed to be operator-writeable. This will be fixed > in 2.0.5. I have the raw floppy operator-writeable locally too, but I > don't think it is right for general use because floppies can be mounted. I miss the point here. Only root can mount/umount. Is there a problem with the operator writing to a device containing a mounted file system? I thought that type of thing was already prohibited by the kernel. Mark. From owner-freebsd-current Mon May 15 14:47:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA17490 for current-outgoing; Mon, 15 May 1995 14:47:45 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA17484 for ; Mon, 15 May 1995 14:47:39 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA10950; Tue, 16 May 1995 07:45:21 +1000 Date: Tue, 16 May 1995 07:45:21 +1000 From: Bruce Evans Message-Id: <199505152145.HAA10950@godzilla.zeta.org.au> To: bde@zeta.org.au, current@FreeBSD.org, mark@linus.demon.co.uk Subject: Re: MAKEDEV and device permissions Sender: current-owner@FreeBSD.org Precedence: bulk >I would agree with the performance argument if it were significant or >if there were no other factor involved. However, in my opinion it's >more important to make scripts like MAKEDEV as obvious as possible to >reduce the chance that security holes creep in. I find it easier to >read device modes directly than having to work out octal complements >on the fly. You still have to be aware of the umasks unless everything is chmod'ed. I think chmod'ing everything would be too verbose. >Rod showed me a candidate patch which seemed to confuse umasks with >modes (in favour of modes :-), which resulted in some calls to "umask >37" and some to "umask 026" to do the same thing... I started removing the execute bits from the umasks since they are irrelevant for devices (mknod masks them anyway) and wrong for directories. >> Tapes were always supposed to be operator-writeable. This will be fixed >> in 2.0.5. I have the raw floppy operator-writeable locally too, but I >> don't think it is right for general use because floppies can be mounted. >I miss the point here. Only root can mount/umount. Is there a problem >with the operator writing to a device containing a mounted file system? >I thought that type of thing was already prohibited by the kernel. Yes, you write to the device while it is not mounted and wait for root to mount it. Bruce From owner-freebsd-current Mon May 15 15:03:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA17821 for current-outgoing; Mon, 15 May 1995 15:03:57 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA17815 for ; Mon, 15 May 1995 15:03:56 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA11057; Mon, 15 May 95 15:15:29 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505152115.AA11057@cs.weber.edu> Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H To: wollman@halloran-eldar.lcs.mit.edu (Garrett Wollman) Date: Mon, 15 May 95 15:15:28 MDT Cc: current@FreeBSD.org In-Reply-To: <9505151842.AA18796@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at May 15, 95 02:42:30 pm X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > > Of course, this isn't recommended, since in principle, the key should > > send the ASCII kvalue that its keycap label implies it sends. > > Of course, not all keyboards are the same. My LK-401 has a keycap > labeled > ___ > / X| > \__| > > and I defy you to state definitively that this symbol implies any > ASCII code at all. DEC being typically obnoxious decided to make it > send BS; I use this magic to make it send something sensible: > > xmodmap - << EOF > keysym BackSpace = Delete > # more stuff goes here > EOF Serves you right for buying a DEC keyboard... must be hooked to a PC. I always thought that symbol was a registered trademark of DEC or something. 8-) 8-). I'll add a rider that keys labelled with something other than ASCII codes or control code names (with the exception of space) send whatever the heck their manuals say they send. Otherwise, I think you are morally obligated to make the key send nothing at all unless the previous character is an 'X'. Or you could make it shift all 'X' characters on the screen left one. Then you could print out the message "NOW are you sorry you bought a wierd keyboard?". Probably the "Microsoft Natural" ought to send the same message for its little "Windows" keys... or start Windows or something. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Mon May 15 15:08:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA17988 for current-outgoing; Mon, 15 May 1995 15:08:01 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA17982 for ; Mon, 15 May 1995 15:08:00 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id PAA18288; Mon, 15 May 1995 15:07:52 -0700 From: Poul-Henning Kamp Message-Id: <199505152207.PAA18288@ref.tfs.com> Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H To: terry@cs.weber.edu (Terry Lambert) Date: Mon, 15 May 1995 15:07:52 -0700 (PDT) Cc: wollman@halloran-eldar.lcs.mit.edu, current@FreeBSD.org In-Reply-To: <9505152115.AA11057@cs.weber.edu> from "Terry Lambert" at May 15, 95 03:15:28 pm Content-Type: text Content-Length: 427 Sender: current-owner@FreeBSD.org Precedence: bulk > Probably the "Microsoft Natural" ought to send the same message for its > little "Windows" keys... or start Windows or something. > Of course, you have noticed how long time after the "space-cadet" keyboard Bill Gates finally got the drift ? -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Mon May 15 16:10:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA19841 for current-outgoing; Mon, 15 May 1995 16:10:48 -0700 Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA19830 for ; Mon, 15 May 1995 16:10:40 -0700 Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id AAA03909; Tue, 16 May 1995 00:10:16 +0100 Date: Tue, 16 May 1995 00:10:16 +0100 From: Mark Valentine Message-Id: <199505152310.AAA03909@linus.demon.co.uk> In-Reply-To: Bruce Evans's message of May 16, 7:45am X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bruce Evans , current@FreeBSD.org Subject: Re: MAKEDEV and device permissions Sender: current-owner@FreeBSD.org Precedence: bulk > From: Bruce Evans > Date: Tue 16 May, 1995 > Subject: Re: MAKEDEV and device permissions > You still have to be aware of the umasks unless everything is chmod'ed. > I think chmod'ing everything would be too verbose. I like this self-documenting verbosity ;-) . > >Rod showed me a candidate patch which seemed to confuse umasks with > >modes (in favour of modes :-), which resulted in some calls to "umask > >37" and some to "umask 026" to do the same thing... > > I started removing the execute bits from the umasks since they are > irrelevant for devices (mknod masks them anyway) and wrong for directories. Ah, I didn't realise it was deliberate. Consistent use of umask in this way would be reasonable. I still favour chmod'ing, though. I can still think of messy bits such as where control devices are created with different permissions from the standard devices. Do you default the standard devices to rely on the umask, yet use chmod for the control devices? Do you set another temporary umask for the control devices (unlikely)? Without explicit chmods for everything, these places at least need a comment saying "I know what I'm doing here". Mark. From owner-freebsd-current Mon May 15 16:24:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA20367 for current-outgoing; Mon, 15 May 1995 16:24:58 -0700 Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA20358 for ; Mon, 15 May 1995 16:24:53 -0700 Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id AAA04149; Tue, 16 May 1995 00:24:10 +0100 Date: Tue, 16 May 1995 00:24:10 +0100 From: Mark Valentine Message-Id: <199505152324.AAA04149@linus.demon.co.uk> In-Reply-To: Bruce Evans's message of May 16, 6:37am X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bruce Evans , pst@shockwave.com Subject: Re: misc/423: security of sound devices Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > From: Bruce Evans > Date: Tue 16 May, 1995 > Subject: Re: misc/423: security of sound devices > >The right model is to do the same thing that we do with /dev/console. If > >you're logged in at the console (or local X server), you own the sound devices. > >When you logout, they should go back to root.sound ownership, with no world > >access. > > This model applies to other devices physically near the console. Joysticks. > Floppies? Scanners. Printers? It's a difficult line to draw. Usually on a PC, audio devices and joysticks are I/O devices associated with the console (in terms of X, they're part of the display in the same way as the mouse, monitor and keyboard). This isn't necessarily true on multi-headed systems. Scanners and printers, however, are resources not necessarily monopolised by the user at the console. Mark. From owner-freebsd-current Mon May 15 23:02:05 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA29896 for current-outgoing; Mon, 15 May 1995 23:02:05 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA29888 for ; Mon, 15 May 1995 23:02:00 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA23449; Tue, 16 May 1995 15:58:01 +1000 Date: Tue, 16 May 1995 15:58:01 +1000 From: Bruce Evans Message-Id: <199505160558.PAA23449@godzilla.zeta.org.au> To: bde@zeta.org.au, current@FreeBSD.org, mark@linus.demon.co.uk Subject: Re: MAKEDEV and device permissions Sender: current-owner@FreeBSD.org Precedence: bulk >I can still think of messy bits such as where control devices are created >with different permissions from the standard devices. Do you default the >standard devices to rely on the umask, yet use chmod for the control >devices? Do you set another temporary umask for the control devices >(unlikely)? Without explicit chmods for everything, these places at >least need a comment saying "I know what I'm doing here". I want to use chmod only for the special [control] devices (probably including the miscellaneous `std' devices). Use of chmod then acts as a warning that you are doing something special. Do you think it is worth worrying about the following? umask 006 mknod foo c x y <----- window where group can read and write <--, chmod 600 foo |-- window where group may be wrong <--' chgrp baz foo The umask would have to be at least 066 all the time to avoid these holes. The 2.0R MAKEDEV doesn't worry at all about this. It has umask 2's followed by chmod 640's for almost all disk devices. Bruce From owner-freebsd-current Tue May 16 01:16:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA02597 for current-outgoing; Tue, 16 May 1995 01:16:27 -0700 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA02589 for ; Tue, 16 May 1995 01:16:19 -0700 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA14032 (5.65c8/HUTCS-S 1.4 for ); Tue, 16 May 1995 11:16:05 +0300 From: Heikki Suonsivu Received: (hsu@localhost) by shadows.cs.hut.fi (8.6.10/8.6.10) id LAA14553; Tue, 16 May 1995 11:16:04 +0300 Date: Tue, 16 May 1995 11:16:04 +0300 Message-Id: <199505160816.LAA14553@shadows.cs.hut.fi> To: freebsd-current@freefall.cdrom.com In-Reply-To: terry@cs.weber.edu's message of 15 May 1995 21:32:39 +0300 Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H References: <9505151809.AA10141@cs.weber.edu> Organization: Helsinki University of Technology, Otaniemi, Finland Sender: current-owner@FreeBSD.org Precedence: bulk In article <9505151809.AA10141@cs.weber.edu> terry@cs.weber.edu (Terry Lambert) writes: Most X terminals interpret this as a request to send an ASCII Backspace character (^H, 0x08) to the slave side of the PTY they are using. The Tektronics X terminals here send ^? and have the key most people talk about as "Backspace" labelled with left-arrow. Ditto for all workstations here, though they are mostly Suns or Linux PC's. I would say that your console is configured incorrectly by default to send and ASCII 0x7f (delete, ^?) instead of an ASCII backspace for your key labelled "Backspace", and that the default tty modes for I don't care about the damn labels, but the function of the keys. I expect the big key above enter/return/whatever to erase the previously typed character, and thus it needs to send ^? unless ANSI has changed its mind (I have only seen a quote from the standard, though). I'm willing to pay for related standards from ANSI for FreeBSD group so that we can get rid of this confusion. There are at least three standards related to ASCII, X3.4, X3.41 and X3.32, I don't know which one is the one which specifies the correct usage but I can pay them all, it should be less than $200 in total including shipping, probably less, $100-$150. Which snail address I should order them to in case ANSI agrees to ship them directly even when order comes from abroad? The Telnet and Rlogin arguments don't hold water here because the erase character is a negotiated option. rlogin doesn't negotiate this, just the terminal type (but rlogin "protocol" is high in brokeness scale anyway). Telnet we don't use much as it keeps asking stupid passwords sent as cleartext over network. rlogin will be replaced RSN by a better method :) -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN From owner-freebsd-current Tue May 16 05:17:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA08720 for current-outgoing; Tue, 16 May 1995 05:17:34 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA08710 for ; Tue, 16 May 1995 05:17:29 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id IAA24599; Tue, 16 May 1995 08:18:07 -0400 From: Peter Dufault Message-Id: <199505161218.IAA24599@hda.com> Subject: Re: big files written to scsi harddisk got corrupted To: davidg@Root.COM Date: Tue, 16 May 1995 08:18:07 -0400 (EDT) Cc: current@FreeBSD.org In-Reply-To: <199505161039.DAA01603@corbin.Root.COM> from "David Greenman" at May 16, 95 03:39:18 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1253 Sender: current-owner@FreeBSD.org Precedence: bulk David Greenman writes: > > >as on the Syquest. I presume this is a bug in FreeBSD as the drive is > >new and the controller is known to have worked flawlessly in another machine. > >In case you need it here is my configuration: > > > >Adaptec 1542 A SCSI controller (I use its floppy disk controller, too) > > The Adaptec 1542A is known to corrupt data for DMA's that are larger than > 16Kbytes. FreeBSD uses I/O clustering both in the file I/O system and in the > VM system and DMA's are frequently larger than 16Kbytes. There are apparantly > some versions of the 1542A that don't have this problem, but every one that > I've tested does. If you upgrade the controller to a 1542B, the problems > should go away. > Can we just put in a minphys for 16K for the 1542A? It is easy to tell when an adapter says it is a 1542A. We can add a flag argument to disable it if you have a known working board or a clone of some sort that says it is a 1542A. This is what I plan to do once I get a computer I can actually test it on. I don't like making changes I can't test. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Tue May 16 05:43:01 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA09047 for current-outgoing; Tue, 16 May 1995 05:43:01 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA09041 for ; Tue, 16 May 1995 05:42:58 -0700 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id FAA07656; Tue, 16 May 1995 05:46:02 -0700 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id FAA01807; Tue, 16 May 1995 05:43:00 -0700 Message-Id: <199505161243.FAA01807@corbin.Root.COM> To: Peter Dufault cc: current@FreeBSD.org Subject: Re: big files written to scsi harddisk got corrupted In-reply-to: Your message of "Tue, 16 May 95 08:18:07 EDT." <199505161218.IAA24599@hda.com> From: David Greenman Reply-To: davidg@Root.COM Date: Tue, 16 May 1995 05:42:59 -0700 Sender: current-owner@FreeBSD.org Precedence: bulk >> The Adaptec 1542A is known to corrupt data for DMA's that are larger than >> 16Kbytes. FreeBSD uses I/O clustering both in the file I/O system and in the >> VM system and DMA's are frequently larger than 16Kbytes. There are apparantly >> some versions of the 1542A that don't have this problem, but every one that >> I've tested does. If you upgrade the controller to a 1542B, the problems >> should go away. >> > >Can we just put in a minphys for 16K for the 1542A? I'm not sure I grok your question. Do you mean add something to limit the maximum DMA transfer size to 16K? If so, yes, this would be a good idea - we need some sort of mechanism to limit the maximum transfer size. It would be nice if the SCSI code could break up requests that exceed it and do then do the I/O in smaller chunks. This doesn't sound very easy to implement, however. I was able to work around the problem back in 1.1.5 by modifying the kernel in various places to limit the I/O clustering to 16K or less, but with the 4.4 VFS layer clustering, this becomes more difficult. -DG From owner-freebsd-current Tue May 16 06:24:17 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA09595 for current-outgoing; Tue, 16 May 1995 06:24:17 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id GAA09589 for ; Tue, 16 May 1995 06:24:15 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id JAA24817; Tue, 16 May 1995 09:25:00 -0400 From: Peter Dufault Message-Id: <199505161325.JAA24817@hda.com> Subject: Re: Strange LKM problems To: current@FreeBSD.org Date: Tue, 16 May 1995 09:24:59 -0400 (EDT) In-Reply-To: <199505131826.OAA15099@hda.com> from "Peter Dufault" at May 13, 95 02:26:07 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1084 Sender: current-owner@FreeBSD.org Precedence: bulk Got one. It is some kind of NFS problem. I started doing this: > modload -v -A /kernel -e sermux_init -o /tmp/sermux.out sermux_mod.o > cp /tmp/sermux.out ./sermux.out Though I have been loading and unloading this code frequently, I haven't been rebooting often and I haven't seen the problem for a few days. Then this morning, first time after a boot, it failed. The two files are the same length except that the file that was copied over NFS is all 0 at the start: NFS mounted (./sermux.out): > 0000000 0000 0000 0000 0000 0000 0000 0000 0000 > * > 0300000 7164 6572 0066 735f 6177 5f70 6170 6567 Local (/tmp/sermux.out): (...) > 0277740 7274 7061 6f2e 5f00 7262 6d65 7266 6565 > 0277760 5f00 6374 5f70 756f 6674 616c 7367 5f00 > 0300000 7164 6572 0066 735f 6177 5f70 6170 6567 -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Tue May 16 07:04:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA10179 for current-outgoing; Tue, 16 May 1995 07:04:51 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id HAA10171 for ; Tue, 16 May 1995 07:04:47 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA19919; Tue, 16 May 1995 10:04:43 -0400 Date: Tue, 16 May 1995 10:04:43 -0400 From: Garrett Wollman Message-Id: <9505161404.AA19919@halloran-eldar.lcs.mit.edu> To: terry@cs.weber.edu (Terry Lambert) Cc: current@FreeBSD.org Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H In-Reply-To: <9505152115.AA11057@cs.weber.edu> References: <9505151842.AA18796@halloran-eldar.lcs.mit.edu> <9505152115.AA11057@cs.weber.edu> Sender: current-owner@FreeBSD.org Precedence: bulk < Serves you right for buying a DEC keyboard... must be hooked to a PC. > I always thought that symbol was a registered trademark of DEC or > something. 8-) 8-). No, actually, it's hooked to my model PE40A-A9 (aka DEC 3000/400) Alpha. My Intel Premiere OEM PC has a generic crufto Thai-made keyboard where the same key is labeled: <-- Which doesn't exactly suggest an ASCII code, either. (In fact, it's identical to the cursor-left key.) Both of them will result in a DEL so long as they're under my control. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Tue May 16 09:06:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA13414 for current-outgoing; Tue, 16 May 1995 09:06:23 -0700 Received: from macs.mxim.com (macs.mxim.com [204.17.143.130]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA13408 for ; Tue, 16 May 1995 09:06:21 -0700 Received: (from michaele@localhost) by macs.mxim.com (8.6.11/8.6.9) id JAA00471; Tue, 16 May 1995 09:08:07 -0700 Date: Tue, 16 May 1995 09:08:07 -0700 (PDT) From: Michael Enkelis To: current@FreeBSD.org Subject: New "config" program Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk There is a oversight in the new config program, it no longer "reminds" you to do a "make depend". The man page says it should, and unless someone is VERY sure now about include files "make depend" still should be done. I know this is a very small oversight, but for anyone new it is important. A side note. What about a automatic make "depend" like SUN does? you could have a -n switch to disable this feature. _ _ _ __ michaele@mxim.com ' ) ) ) / /) / ` / /) Michael Enkelis / / / o _. /_ __. _ // /-- __ /_ _ // o _ (503) 641 - 3737 x2245 / ' (_(_(__/ /_(_(_(<_(/_ (___, /) )_/ <_(<_(/_(_/_)_ From owner-freebsd-current Tue May 16 09:47:59 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA14184 for current-outgoing; Tue, 16 May 1995 09:47:59 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA14173 for ; Tue, 16 May 1995 09:47:47 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA20148; Tue, 16 May 1995 12:47:13 -0400 Date: Tue, 16 May 1995 12:47:13 -0400 From: Garrett Wollman Message-Id: <9505161647.AA20148@halloran-eldar.lcs.mit.edu> To: Michael Enkelis Cc: current@FreeBSD.org Subject: New "config" program In-Reply-To: References: Sender: current-owner@FreeBSD.org Precedence: bulk < said: > A side note. What about a automatic make "depend" like SUN does? > you could have a -n switch to disable this feature. It would be far less obnoxious to have a shell script that handled all aspects of kernel generation. The only part of this that doesn't work is the automatic generation of a new kernel from GENERIC: #!/bin/sh doclean=true autoinstall=false kernelname='' for arg; do case $arg in -n*) doclean=false;; -i*) autoinstall=true;; -*) usage;; *) kernelname=$arg;; esac done if [ -z "$kernelname" ]; then kernelname=`hostname -s | tr a-z A-Z` fi cd /sys/`uname -m`/conf if [ ! -e $kernelname ]; then echo "$0: kernel configuration file $kernelname does not exist" echo -n 'Create one from GENERIC [n]?' if read ans && expr $ans : 'y*' >/dev/null; then sed '/^#SED0/,$d' < GENERIC > $kernelname lsdev -c >> $kernelname echo '#SED0' >> $kernelname sed '1,/^#SED0/d' < GENERIC >> $kernelname else exit 1 fi fi set -e config -n $kernelname cd /sys/compile/$kernelname if $doclean; then make clean fi make depend make all if $autoinstall; then make install fi exit 0 From owner-freebsd-current Tue May 16 11:05:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA15958 for current-outgoing; Tue, 16 May 1995 11:05:23 -0700 Received: from emerald.oz.net (emerald.oz.net [198.68.184.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA15941 for ; Tue, 16 May 1995 11:05:21 -0700 Received: from wsantee.oz.net by emerald.oz.net via SMTP (931110.SGI/930416.SGI) for freebsd-current@freebsd.org id AA14150; Tue, 16 May 95 11:03:10 -0700 Received: (from wsantee@localhost) by wsantee.oz.net (8.6.11/8.6.9) id LAA05961; Tue, 16 May 1995 11:03:16 -0700 From: Wes Santee Message-Id: <199505161803.LAA05961@wsantee.oz.net> Subject: Re: New "config" program To: michaele@mxim.com (Michael Enkelis) Date: Tue, 16 May 1995 11:03:15 -0700 (PDT) Cc: freebsd-current@FreeBSD.org In-Reply-To: from "Michael Enkelis" at May 16, 95 09:08:07 am X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 744 Sender: current-owner@FreeBSD.org Precedence: bulk > > There is a oversight in the new config program, it no longer "reminds" > you to do a "make depend". > > The man page says it should, and unless someone is VERY sure now about > include files "make depend" still should be done. This brings up an interesting question. In the FreeBSD FAQ it says that to rebuild the kernel one does: 6.0.1: cd /usr/src/sys/i386/conf 6.0.2: cp GENERIC MYKERNEL 6.0.3: vi MYKERNEL 6.0.4: config MYKERNEL 6.0.5: cd ../../compile/MYKERNEL 6.0.6: make all 6.0.7: make install 6.0.8: reboot Does this mean that no make depend is necessary, or that make depend is implied as part of step 6.0.4? Maybe an update to the FAQ is necessary, or else the new config program is correct. Cheers, -Wes From owner-freebsd-current Tue May 16 11:14:16 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA16227 for current-outgoing; Tue, 16 May 1995 11:14:16 -0700 Received: from lirmm.lirmm.fr (lirmm.lirmm.fr [193.49.104.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA16221 for ; Tue, 16 May 1995 11:14:12 -0700 Received: from lirmm.fr (baobab.lirmm.fr [193.49.106.14]) by lirmm.lirmm.fr (8.6.10/8.6.4) with ESMTP id UAA06161 for ; Tue, 16 May 1995 20:14:07 +0200 Message-Id: <199505161814.UAA06161@lirmm.lirmm.fr> To: current@FreeBSD.org Subject: wrong release number Date: Tue, 16 May 1995 20:13:01 +0200 From: "Philippe Charnier" Sender: current-owner@FreeBSD.org Precedence: bulk Hello, the screen saver ``snake'' uses the string FreeBSD-2.1. -------- -------- Philippe Charnier charnier@lirmm.fr LIRMM, 161 rue Ada, 34392 Montpellier cedex 5 -- France ------------------------------------------------------------------------ From owner-freebsd-current Tue May 16 11:30:51 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA16629 for current-outgoing; Tue, 16 May 1995 11:30:51 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA16622 ; Tue, 16 May 1995 11:30:50 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: Michael Enkelis cc: current@FreeBSD.org Subject: Re: New "config" program In-reply-to: Your message of "Tue, 16 May 95 09:08:07 PDT." Date: Tue, 16 May 1995 11:30:50 -0700 Message-ID: <16621.800649050@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > There is a oversight in the new config program, it no longer "reminds" > you to do a "make depend". Not an oversight at all. The make depend was of dubious value as it still didn't actually function properly - it would catch very simplistic dependencies but not more complex ones, resulting in kernels which failed in weird and interesting ways. I think anyone using `make depend' in /sys/compile/FOO and expecting it to work across multiple configs/changes is just asking for trouble, and I have ample evidence to prove it! Note that I'm not saying that this _shouldn't_ work, simply that it does not currently do so reliably enough to be counted upon. Jordan From owner-freebsd-current Tue May 16 13:02:00 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA18839 for current-outgoing; Tue, 16 May 1995 13:02:00 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA18830 for ; Tue, 16 May 1995 13:01:55 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA09071; Tue, 16 May 1995 13:01:17 -0700 From: "Rodney W. Grimes" Message-Id: <199505162001.NAA09071@gndrsh.aac.dev.com> Subject: Re: New "config" program To: wsantee@wsantee.oz.net (Wes Santee) Date: Tue, 16 May 1995 13:01:17 -0700 (PDT) Cc: michaele@mxim.com, freebsd-current@FreeBSD.org In-Reply-To: <199505161803.LAA05961@wsantee.oz.net> from "Wes Santee" at May 16, 95 11:03:15 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1138 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > There is a oversight in the new config program, it no longer "reminds" > > you to do a "make depend". > > > > The man page says it should, and unless someone is VERY sure now about > > include files "make depend" still should be done. > > This brings up an interesting question. In the FreeBSD FAQ it says > that to rebuild the kernel one does: > > 6.0.1: cd /usr/src/sys/i386/conf > 6.0.2: cp GENERIC MYKERNEL > 6.0.3: vi MYKERNEL > 6.0.4: config MYKERNEL > 6.0.5: cd ../../compile/MYKERNEL > 6.0.6: make all 6.0.6 make depend all > 6.0.7: make install > 6.0.8: reboot > > Does this mean that no make depend is necessary, or that make depend > is implied as part of step 6.0.4? Maybe an update to the FAQ is > necessary, or else the new config program is correct. The faq is wrong, though the above will work, it is probably the #1 reason that caused Jordan to do what he did to config to rm -r the compile directory. > > Cheers, > -Wes > > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue May 16 13:03:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA18886 for current-outgoing; Tue, 16 May 1995 13:03:49 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA18876 ; Tue, 16 May 1995 13:03:42 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA09081; Tue, 16 May 1995 13:03:29 -0700 From: "Rodney W. Grimes" Message-Id: <199505162003.NAA09081@gndrsh.aac.dev.com> Subject: Re: New "config" program To: jkh@freefall.cdrom.com (Jordan K. Hubbard) Date: Tue, 16 May 1995 13:03:29 -0700 (PDT) Cc: michaele@mxim.com, current@FreeBSD.org In-Reply-To: <16621.800649050@freefall.cdrom.com> from "Jordan K. Hubbard" at May 16, 95 11:30:50 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1290 Sender: current-owner@FreeBSD.org Precedence: bulk > > > There is a oversight in the new config program, it no longer "reminds" > > you to do a "make depend". > > Not an oversight at all. The make depend was of dubious value as it > still didn't actually function properly - it would catch very > simplistic dependencies but not more complex ones, resulting in > kernels which failed in weird and interesting ways. > > I think anyone using `make depend' in /sys/compile/FOO and expecting > it to work across multiple configs/changes is just asking for trouble, > and I have ample evidence to prove it! The most common mode of failure here was when running config again on the same kernel most people did not rerun make depend since they had already run it once before. Since the header files had been rewritten by config you need to rerun make depend. It should still give this message if I say config -n FOOBAR!!! > Note that I'm not saying that this _shouldn't_ work, simply that it > does not currently do so reliably enough to be counted upon. Also many dependcies missing on Makefile due to proliferation of compile time options that are in CFLAGS rather than .h files. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue May 16 13:36:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA19748 for current-outgoing; Tue, 16 May 1995 13:36:32 -0700 Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA19741 for ; Tue, 16 May 1995 13:36:28 -0700 Received: from gilberto.physik.rwth-aachen.de by campino.informatik.rwth-aachen.de (4.1/campino-7) id AA21511; Tue, 16 May 95 22:36:06 +0200 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.8/8.6.9) id WAA01236 for freebsd-current@freefall.cdrom.com; Tue, 16 May 1995 22:47:20 +0200 Message-Id: <199505162047.WAA01236@gilberto.physik.rwth-aachen.de> Subject: world build fails (libdialog) To: freebsd-current@freefall.cdrom.com (user alias) Date: Tue, 16 May 1995 22:47:20 +0200 (MET DST) From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 612 Sender: current-owner@FreeBSD.org Precedence: bulk cc -O2 -I/usr/src/gnu/lib/libdialog -Wall -Wstrict-prototypes -DLOCALE -c /usr/src/gnu/lib/libdialog/notify.c -o notify.o /usr/src/gnu/lib/libdialog/notify.c: In function `dialog_notify': /usr/src/gnu/lib/libdialog/notify.c:41: too many arguments to function `dialog_mesgbox' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de FreeBSD blues.physik.rwth-aachen.de 2.0-BUILT-19950507 FreeBSD 2.0-BUILT-1995 0507 #0: Sun May 7 18:08:05 MET DST 1995 root@blues.physik.rwth-aachen.d e:/usr/src/sys/compile/BLUESGUS i386 From owner-freebsd-current Tue May 16 14:10:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA20644 for current-outgoing; Tue, 16 May 1995 14:10:34 -0700 Received: (from dima@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA20634 ; Tue, 16 May 1995 14:10:31 -0700 Message-Id: <199505162110.OAA20634@freefall.cdrom.com> Subject: Re: New "config" program To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Tue, 16 May 1995 14:10:31 -0700 (PDT) Cc: wsantee@wsantee.oz.net, michaele@mxim.com, freebsd-current@FreeBSD.org In-Reply-To: <199505162001.NAA09071@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 16, 95 01:01:17 pm From: dima@FreeBSD.org (Dima Ruban) X-Class: Fast Organization: HackerDome X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1298 Sender: current-owner@FreeBSD.org Precedence: bulk Rodney W. Grimes writes: > > > > > > > > > There is a oversight in the new config program, it no longer "reminds" > > > you to do a "make depend". > > > > > > The man page says it should, and unless someone is VERY sure now about > > > include files "make depend" still should be done. > > > > This brings up an interesting question. In the FreeBSD FAQ it says > > that to rebuild the kernel one does: > > > > 6.0.1: cd /usr/src/sys/i386/conf > > 6.0.2: cp GENERIC MYKERNEL > > 6.0.3: vi MYKERNEL > > 6.0.4: config MYKERNEL > > 6.0.5: cd ../../compile/MYKERNEL > > 6.0.6: make all > 6.0.6 make depend all Why not just make depend all install? > > > 6.0.7: make install > > 6.0.8: reboot > > > > Does this mean that no make depend is necessary, or that make depend > > is implied as part of step 6.0.4? Maybe an update to the FAQ is > > necessary, or else the new config program is correct. > > The faq is wrong, though the above will work, it is probably the > #1 reason that caused Jordan to do what he did to config to rm -r > the compile directory. > > > > > Cheers, > > -Wes > > > > > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation Company Custom computers for FreeBSD > -- dima From owner-freebsd-current Tue May 16 14:14:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA20768 for current-outgoing; Tue, 16 May 1995 14:14:47 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA20758 ; Tue, 16 May 1995 14:14:42 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id OAA09252; Tue, 16 May 1995 14:14:27 -0700 From: "Rodney W. Grimes" Message-Id: <199505162114.OAA09252@gndrsh.aac.dev.com> Subject: Re: New "config" program To: dima@FreeBSD.org (Dima Ruban) Date: Tue, 16 May 1995 14:14:27 -0700 (PDT) Cc: wsantee@wsantee.oz.net, michaele@mxim.com, freebsd-current@FreeBSD.org In-Reply-To: <199505162110.OAA20634@freefall.cdrom.com> from "Dima Ruban" at May 16, 95 02:10:31 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1744 Sender: current-owner@FreeBSD.org Precedence: bulk > > Rodney W. Grimes writes: > > > > > > > > > > > > > There is a oversight in the new config program, it no longer "reminds" > > > > you to do a "make depend". > > > > > > > > The man page says it should, and unless someone is VERY sure now about > > > > include files "make depend" still should be done. > > > > > > This brings up an interesting question. In the FreeBSD FAQ it says > > > that to rebuild the kernel one does: > > > > > > 6.0.1: cd /usr/src/sys/i386/conf > > > 6.0.2: cp GENERIC MYKERNEL > > > 6.0.3: vi MYKERNEL > > > 6.0.4: config MYKERNEL > > > 6.0.5: cd ../../compile/MYKERNEL > > > 6.0.6: make all > > 6.0.6 make depend all > > Why not just make depend all install? Probably safe, but I like to run make install as a seprate command, it's not nice to replace /kernel and not do a reboot right away. You could do: make depend all install && reboot :-) > > > > > > 6.0.7: make install > > > 6.0.8: reboot > > > > > > Does this mean that no make depend is necessary, or that make depend > > > is implied as part of step 6.0.4? Maybe an update to the FAQ is > > > necessary, or else the new config program is correct. > > > > The faq is wrong, though the above will work, it is probably the > > #1 reason that caused Jordan to do what he did to config to rm -r > > the compile directory. > > > > > > > > Cheers, > > > -Wes > > > > > > > > > > > > -- > > Rod Grimes rgrimes@gndrsh.aac.dev.com > > Accurate Automation Company Custom computers for FreeBSD > > > > -- dima > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Tue May 16 14:33:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA21817 for current-outgoing; Tue, 16 May 1995 14:33:18 -0700 Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA21803 for ; Tue, 16 May 1995 14:33:16 -0700 Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14406(2)>; Tue, 16 May 1995 14:32:37 PDT Received: by crevenia.parc.xerox.com id <49859>; Tue, 16 May 1995 14:32:32 -0700 From: Bill Fenner To: current@FreeBSD.org Subject: "savecore" causes panic Message-Id: <95May16.143232pdt.49859@crevenia.parc.xerox.com> Date: Tue, 16 May 1995 14:32:26 PDT Sender: current-owner@FreeBSD.org Precedence: bulk I have an old '486 with 32 megs of memory and a new AHA1542FC, running SNAP-950412. I panicked and dumped core and wanted to check out the core dump. There are two devices on the SCSI bus: aha0 is a 154xCF-2.01-VE.0: enabling mailbox and residuals aha0: reading board settings, dma=5 int=11 (bus speed defaulted) aha0 at 0x330-0x333 irq 11 drq 5 on isa (aha0:0:0): "QUANTUM P105S 910-10-94x A.3" is a type 0 fixed SCSI 1 sd0(aha0:0:0): Direct-Access 100MB (205075 512 byte sectors) (aha0:1:0): "CDC 94171-9 0045" is a type 0 fixed SCSI 1 sd1(aha0:1:0): Direct-Access 312MB (640584 512 byte sectors) Swap (aka dump) was on sd0b, I was trying to savecore to /home/fenner, which is on sd1f. The first time I tried, I got a few messages like May 16 13:51:08 baobab /kernel: aha0: DMA beyond end Of ISA May 16 13:51:09 baobab /kernel: sd1: oops not queued May 16 13:51:09 baobab /kernel: biodone: buffer already done May 16 13:51:10 baobab /kernel: aha0: DMA beyond end Of ISA May 16 13:51:11 baobab /kernel: sd1: oops not queued May 16 13:51:11 baobab /kernel: biodone: buffer already done and presumably panicked, although since I have ddb configured and was running X, I couldn't tell. The second time, I ran fron the console, and didn't get any of the DMA errors, but did get: panic: vm_bounce_page_free: invalid bounce buffer (manually copied traceback follows) _vm_bounce_page_free(37f000,1) at _vm_bounce_page_free+0x50 _vm_bounce_free(f26d0b50) at _vm_bounce_free+0xa0 _biodone(f26d0b50,f0a22000,f08b0980,1,f0a22000) at _biodone+0x7f _scsi_done() _aha_done() _ahaintr() I would offer to provide a core file, but that might be difficult =) Any suggestions? (Hopefully it won't swap before I get this core file off of there.. mebbe I should just debug with the core file in swap space...) Note that I can "dd if=/dev/sd0b of=/home/fenner/corefile" just fine, but savecore very quickly causes this panic. Bill From owner-freebsd-current Tue May 16 15:39:48 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA24882 for current-outgoing; Tue, 16 May 1995 15:39:48 -0700 Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA24838 for ; Tue, 16 May 1995 15:39:23 -0700 Received: (from mark@localhost) by linus.demon.co.uk (8.6.11/8.6.9) id XAA02840; Tue, 16 May 1995 23:35:47 +0100 Date: Tue, 16 May 1995 23:35:47 +0100 From: Mark Valentine Message-Id: <199505162235.XAA02840@linus.demon.co.uk> In-Reply-To: Bruce Evans's message of May 16, 3:58pm X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bruce Evans , current@FreeBSD.org Subject: Re: MAKEDEV and device permissions Sender: current-owner@FreeBSD.org Precedence: bulk > From: Bruce Evans > Date: Tue 16 May, 1995 > Subject: Re: MAKEDEV and device permissions > Do you think it is worth worrying about the following? > > umask 006 > mknod foo c x y > <----- window where group can read and write > <--, > chmod 600 foo |-- window where group may be wrong > <--' > chgrp baz foo It's probably more annoying that the window is there than any real risk. In my scheme with chmods for everything, you just set a suitably restrictive umask at the top of the script to close all these! I find it a good rule of thumb to stick to the order mknod/chown/chmod (and for a lot more than just MAKEDEV). (OK, I'll stop pushing my argument now... maybe. ;-) Mark. From owner-freebsd-current Tue May 16 17:02:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA26057 for current-outgoing; Tue, 16 May 1995 17:02:39 -0700 Received: from jabba.fdn.org (jabba.fdn.org [193.55.4.70]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA26050 for ; Tue, 16 May 1995 17:02:33 -0700 Received: (from uucp@localhost) by jabba.fdn.org (8.6.8/8.6.9) with UUCP id CAA26194 for freebsd-current@freefall.cdrom.com; Wed, 17 May 1995 02:01:52 +0200 Received: (pb@localhost) by fasterix.frmug.fr.net (8.6.11/fasterix-941011) id BAA01001 for freebsd-current@freefall.cdrom.com; Wed, 17 May 1995 01:58:03 +0200 From: Pierre Beyssac Message-Id: <199505162358.BAA01001@fasterix.frmug.fr.net> Subject: NFS swap for diskless machines To: freebsd-current@freefall.cdrom.com Date: Wed, 17 May 1995 01:58:02 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 755 Sender: current-owner@FreeBSD.org Precedence: bulk I'm currently trying to boot a diskless PC under FreeBSD. Everything works fine, except when I try to add NFS swap in the /tftpboot/cfg.xxx file. The system panics in the pager during boot. The lines I added are : swapfs :/export/swap swapsize 20000 If I remove these lines, I can boot the system fine with no swap. Is there something special to do, in addition to the creation of the file /export/swap/swap. ? Maybe a special kernel config option ? The documentation about diskless configuration does not say anything special. -- Pierre Beyssac pb@fasterix.frmug.fr.net pb@fasterix.fdn.fr FreeBSD, NetBSD, Linux -- Il y a moins bien, mais c'est plus cher. You can also get less bang for more bucks. (translation F. Berjon) From owner-freebsd-current Tue May 16 17:07:20 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA26116 for current-outgoing; Tue, 16 May 1995 17:07:20 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA26110 for ; Tue, 16 May 1995 17:07:19 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id RAA22574; Tue, 16 May 1995 17:07:06 -0700 From: Poul-Henning Kamp Message-Id: <199505170007.RAA22574@ref.tfs.com> Subject: Re: NFS swap for diskless machines To: pb@fasterix.freenix.fr (Pierre Beyssac) Date: Tue, 16 May 1995 17:07:06 -0700 (PDT) Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199505162358.BAA01001@fasterix.frmug.fr.net> from "Pierre Beyssac" at May 17, 95 01:58:02 am Content-Type: text Content-Length: 417 Sender: current-owner@FreeBSD.org Precedence: bulk > I'm currently trying to boot a diskless PC under FreeBSD. > > Everything works fine, except when I try to add NFS swap in the > /tftpboot/cfg.xxx file. The system panics in the pager during boot. Uhm, what version are you running ? -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Tue May 16 17:11:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id RAA26158 for current-outgoing; Tue, 16 May 1995 17:11:27 -0700 Received: from jabba.fdn.org (jabba.fdn.org [193.55.4.70]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id RAA26152 for ; Tue, 16 May 1995 17:11:24 -0700 Received: (from uucp@localhost) by jabba.fdn.org (8.6.8/8.6.9) with UUCP id CAA26443; Wed, 17 May 1995 02:11:12 +0200 Received: (pb@localhost) by fasterix.frmug.fr.net (8.6.11/fasterix-941011) id CAA01310; Wed, 17 May 1995 02:10:35 +0200 From: Pierre Beyssac Message-Id: <199505170010.CAA01310@fasterix.frmug.fr.net> Subject: Re: NFS swap for diskless machines To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 17 May 1995 02:10:34 +0200 (MET DST) Cc: pb@fasterix.freenix.fr, freebsd-current@freefall.cdrom.com In-Reply-To: <199505170007.RAA22574@ref.tfs.com> from "Poul-Henning Kamp" at May 16, 95 05:07:06 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 499 Sender: current-owner@FreeBSD.org Precedence: bulk Poul-Henning Kamp writes: > > Everything works fine, except when I try to add NFS swap in the > > /tftpboot/cfg.xxx file. The system panics in the pager during boot. > > Uhm, what version are you running ? Both the server and the diskless client are -current kernels compiled from today's sources. -- Pierre Beyssac pb@fasterix.frmug.fr.net pb@fasterix.fdn.fr FreeBSD, NetBSD, Linux -- Il y a moins bien, mais c'est plus cher. You can also get less bang for more bucks. (translation F. Berjon) From owner-freebsd-current Wed May 17 00:29:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA25666 for current-outgoing; Wed, 17 May 1995 00:29:42 -0700 Received: from lirmm.lirmm.fr (lirmm.lirmm.fr [193.49.104.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA25659 for ; Wed, 17 May 1995 00:29:37 -0700 Received: from lirmm.fr (baobab.lirmm.fr [193.49.106.14]) by lirmm.lirmm.fr (8.6.10/8.6.4) with ESMTP id JAA11413 for ; Wed, 17 May 1995 09:29:25 +0200 Message-Id: <199505170729.JAA11413@lirmm.lirmm.fr> To: current@FreeBSD.org Subject: swfree() Date: Wed, 17 May 1995 09:29:22 +0200 From: "Philippe Charnier" Sender: current-owner@FreeBSD.org Precedence: bulk Hello, After a make world (so including config) and removing swap on .... in the kernel config file before building a new kernel, I get panic : swfree when booting. note that boot is on wd1 and swap is in wd0 and sd0. -------- -------- Philippe Charnier charnier@lirmm.fr LIRMM, 161 rue Ada, 34392 Montpellier cedex 5 -- France ------------------------------------------------------------------------ From owner-freebsd-current Wed May 17 00:56:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA27294 for current-outgoing; Wed, 17 May 1995 00:56:12 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA27286 for ; Wed, 17 May 1995 00:56:11 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <16835-0@bunyip.cc.uq.oz.au>; Wed, 17 May 1995 17:54:36 +1000 Received: from netfl15a.devetir.qld.gov.au by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP id RAA15079 for ; Wed, 17 May 1995 17:58:21 +1000 Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) id HAA04081 for ; Wed, 17 May 1995 07:55:18 GMT Message-Id: <199505170755.HAA04081@netfl15a.devetir.qld.gov.au> X-Mailer: exmh version 1.6 4/21/95 To: current@FreeBSD.org Subject: Some speedups noticed Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 May 1995 17:55:17 +1000 From: Stephen Hocking Sender: current-owner@FreeBSD.org Precedence: bulk On my memory deprived machine, I've noticed a slight change (for the better!) in the way interactive processes are being handled during times of heavy mem. usage by other processes. E.G. a make world is in progress (and has been for the past 24 hours!) and I start typing at a shell prompt. Once the shell is swapped back in, it continues to respond quite well. Even small pauses between commands don't seem to be seen as an excuse to push it out to swap again. My memory suggests that this was not always the case. Some of the commit messages I've seen for the vm system suggest that some enhancement has been taking place, so I'll blame them. Stephen I do not speak for the Worker's Compensation Board of Queensland - They don't pay me enough for that! From owner-freebsd-current Wed May 17 01:28:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA00713 for current-outgoing; Wed, 17 May 1995 01:28:24 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA00670 for ; Wed, 17 May 1995 01:28:06 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id SAA06582; Wed, 17 May 1995 18:22:05 +1000 Date: Wed, 17 May 1995 18:22:05 +1000 From: Bruce Evans Message-Id: <199505170822.SAA06582@godzilla.zeta.org.au> To: davidg@Root.COM Subject: fork bombs Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk When I left my nfs server turned off overnight, my nfs client forked about 150 running crons and ran out of swap space. This situation was not recoverable. ps in ddb showed the crons waiting for swap space and the nfs server. The vm system printed a few messages about killing process due to lack of swap space. When the server started, the vm system looped printing messages about killing the same process. After a little while and several more ps's in ddb, the system spontaneously rebooted. The client has 8MB memory and 16MB swap. I then tried a program doing `for (;;) { write(1, ".", 1); fork(); }'. The system paniced. I forget the details and can't reproduce the panic. I then tried running the same program after noting the environment more carefully. I was non-root on the client. There was no problem with a process limit of 40 (swap isn't activated in this case). I ran the program in /tmp so nfs is probably irrelevant. I then tried running the program as root. The system hung. I forget the details. I then tried running the program as non-root with the process limit set to the maximum (179). The system started swapping and never stopped. ^C and ^Z had no effect and root logins were impossible (getty didn't even echo). ps in ddb showed most processes runnable and a varying number of processes were sleeping on "vmwait". The swapper process was always sleeping on "schedm". New process were not being forked. The vm system didn't print any messages about killing processes. This situation was easy to reproduce. Bruce From owner-freebsd-current Wed May 17 01:47:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA03005 for current-outgoing; Wed, 17 May 1995 01:47:02 -0700 Received: from easynet.com (easyr.easynet.net [198.67.38.6]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA02997 for ; Wed, 17 May 1995 01:46:59 -0700 Received: by easynet.com (Smail3.1.28.1 #7) id m0sBel3-000rdwC; Wed, 17 May 95 01:47 WET DST Message-Id: From: brian@mediacity.com (Brian Litzinger) Subject: statics needed in lnc driver To: freebsd-current@FreeBSD.org Date: Wed, 17 May 1995 01:47:09 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 397 Sender: current-owner@FreeBSD.org Precedence: bulk Would it not be wise to static if_lnc.o: Definition of symbol `_write_csr' (multiply defined) if_lnc.o: Definition of symbol `_read_csr' (multiply defined) The collision is happening with ethdlc.o: Definition of symbol `_write_csr' (multiply defined) ethdlc.o: Definition of symbol `_read_csr' (multiply defined) I've chided the author of ethdlc.o. Brian Litzinger brian@easynet.com From owner-freebsd-current Wed May 17 02:29:46 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA05834 for current-outgoing; Wed, 17 May 1995 02:29:46 -0700 Received: from bunyip.cc.uq.oz.au (bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id CAA05828 for ; Wed, 17 May 1995 02:29:41 -0700 Received: from cc.uq.oz.au by bunyip.cc.uq.oz.au id <25648-0@bunyip.cc.uq.oz.au>; Wed, 17 May 1995 19:29:33 +1000 Received: by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) id TAA15908; Wed, 17 May 1995 19:32:34 +1000 From: Stephen McKay Message-Id: <199505170932.TAA15908@pandora.devetir.qld.gov.au> To: freebsd-current@FreeBSD.org cc: syssgm@devetir.qld.gov.au Subject: Enthusiasm boost: make world works on 386SX16 4Mb Date: Wed, 17 May 95 19:32:34 EST Sender: current-owner@FreeBSD.org Precedence: bulk Feeling down because your Pentium 90 complains about syntax errors in the latest sysinstall? Worried about your slow Internet connection? Fooey! Gain a special warmth from the knowledge that FreeBSD-current (as of 1995-05-09 20:57) compiles from scratch in a mere 6 days non-stop on a 386SX16 with 4Mb ram, IDE disk, vnconfig'd swap space and NFS mounted /usr/src and /usr/obj. We're talking 140 hours, give or take a few. Be happy to know that every type of swap-in/swap-out/page-in/page-out/vm-fault code sequence was exercised thousands of times in a memory starved environment. Be not indifferent to the fact that it still ran well enough while compiling to allow a few vmstats and pstats and the occasional 'man vnconfig'. Key echo was fine, most of the time. :-) 2.0.5 is looking really solid to me! No hangs, glitches or weird things, and all my swap space stayed usable. Prepare for pats on the back all round! Stephen. PS. Those of you with a trivia fixation can enjoy the following: 'make world' caused 60 million wdc0 interrupts and 6 million ed0 interrupts. From owner-freebsd-current Wed May 17 02:50:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA06823 for current-outgoing; Wed, 17 May 1995 02:50:15 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA06816 for ; Wed, 17 May 1995 02:50:09 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id CAA11165; Wed, 17 May 1995 02:49:39 -0700 From: "Rodney W. Grimes" Message-Id: <199505170949.CAA11165@gndrsh.aac.dev.com> Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb To: syssgm@devetir.qld.gov.au (Stephen McKay) Date: Wed, 17 May 1995 02:49:39 -0700 (PDT) Cc: freebsd-current@FreeBSD.org, syssgm@devetir.qld.gov.au In-Reply-To: <199505170932.TAA15908@pandora.devetir.qld.gov.au> from "Stephen McKay" at May 17, 95 07:32:34 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1625 Sender: current-owner@FreeBSD.org Precedence: bulk > > Feeling down because your Pentium 90 complains about syntax errors in > the latest sysinstall? Worried about your slow Internet connection? Fooey! > > Gain a special warmth from the knowledge that FreeBSD-current (as of > 1995-05-09 20:57) compiles from scratch in a mere 6 days non-stop on > a 386SX16 with 4Mb ram, IDE disk, vnconfig'd swap space and NFS mounted > /usr/src and /usr/obj. We're talking 140 hours, give or take a few. Only 32 times slower than a P54C-90 with fast local disks and 32MB of memory. Wonder what you payed for that SX16 system 5 years ago when you got it :-) :-). > Be happy to know that every type of swap-in/swap-out/page-in/page-out/vm-fault > code sequence was exercised thousands of times in a memory starved environment. > > Be not indifferent to the fact that it still ran well enough while compiling > to allow a few vmstats and pstats and the occasional 'man vnconfig'. Key > echo was fine, most of the time. :-) > > 2.0.5 is looking really solid to me! No hangs, glitches or weird things, and > all my swap space stayed usable. Prepare for pats on the back all round! Glad to here that you like it!!! > Stephen. > > PS. Those of you with a trivia fixation can enjoy the following: > 'make world' caused 60 million wdc0 interrupts and 6 million ed0 interrupts. Humm.. to bad the PCI code is broken in this area, it would be interesting to compare the number of interrupts to a scsi system running make world. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Wed May 17 03:24:30 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA10652 for current-outgoing; Wed, 17 May 1995 03:24:30 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id DAA10642 for ; Wed, 17 May 1995 03:24:26 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA24316 (5.67b/IDA-1.5 for current@freebsd.org); Wed, 17 May 1995 12:23:46 +0200 Message-Id: <199505171023.AA24316@FileServ1.MI.Uni-Koeln.DE> From: esser@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Wed, 17 May 1995 12:23:45 +0200 In-Reply-To: "Rodney W. Grimes" "Re: Enthusiasm boost: make world works on 386SX16 4Mb" (May 17, 2:49) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Rodney W. Grimes" Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk On May 17, 2:49, "Rodney W. Grimes" wrote: } Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb } } Humm.. to bad the PCI code is broken in this area, it would be interesting } to compare the number of interrupts to a scsi system running make world. I've been **extremely** busy lately. And I guess it's too late for 2.0.5 anyway. Will make sure it is in -current as soon as possible, after the code freeze is over ... Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706017 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Wed May 17 08:22:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA06452 for current-outgoing; Wed, 17 May 1995 08:22:31 -0700 Received: from ns1.win.net (NS1.WIN.NET [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA06446 for ; Wed, 17 May 1995 08:22:29 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id LAA20369 for current@freebsd.org; Wed, 17 May 1995 11:24:29 -0400 From: Mark Hittinger Message-Id: <199505171524.LAA20369@ns1.win.net> Subject: -cur boot hangs since may 1 To: current@FreeBSD.org Date: Wed, 17 May 1995 11:24:26 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 740 Sender: current-owner@FreeBSD.org Precedence: bulk Hi My plate was emptier than usual today and I had a chance to do a little DDB'n. Here is the scoop: If you have a 3com etherlink-III card (ep0) and you try to boot a generic style kernel it hangs in various places during the boot. This, of course, sends one on various wild goose chases. I've seen this problem since May 1 but really haven't had time to roll up my sleeves and chase it till now. If you disable ie0 during a '-c' boot dialog (or build a kernel without ie0) then things work great. All my boxes have ep0 cards so I have been an unhappy boy for many days. I am looking at the probe technique in the ie0 driver to see what has been changed. It may be confusing the 3c509 card. Regards, Mark Hittinger bugs@win.net From owner-freebsd-current Wed May 17 08:28:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA06538 for current-outgoing; Wed, 17 May 1995 08:28:39 -0700 Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA06532 for ; Wed, 17 May 1995 08:28:38 -0700 Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.10/8.6.9) with SMTP id KAA16368 for ; Wed, 17 May 1995 10:28:36 -0500 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Wed, 17 May 95 10:28 CDT Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Wed, 17 May 95 10:28 CDT Message-Id: Subject: mtree incomplete To: current@FreeBSD.org Date: Wed, 17 May 1995 10:28:34 -0500 (CDT) From: "Lars Fredriksen" X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 382 Sender: current-owner@FreeBSD.org Precedence: bulk Hi, It seems like the mtree is incomplete when it comes to /usr/share/sgml/xxx where xxx is drd and rpt or some such. make install failes when it tries to drop files into these directories. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks.pr.mcs.net (home-home) fredriks@asiago.cs.wisc.edu From owner-freebsd-current Wed May 17 10:00:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA08876 for current-outgoing; Wed, 17 May 1995 10:00:02 -0700 Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA08864 for ; Wed, 17 May 1995 09:59:59 -0700 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.11/8.6.9) id JAA00176 for freebsd-current@freefall.cdrom.com; Wed, 17 May 1995 09:55:45 -0700 From: Steven G Kargl Message-Id: <199505171655.JAA00176@troutmask.apl.washington.edu> Subject: panic: swfree To: freebsd-current@freefall.cdrom.com (FreeBSD Current) Date: Wed, 17 May 1995 09:55:44 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 564 Sender: current-owner@FreeBSD.org Precedence: bulk I got this panic from a kernel built from sources that were last updated this morning at 0600 pst. The system dumped, but I did not save the dump file. If needed I can successfully repeat this panic:( BTW, during `shutdown -r now', I got the following message: keyboard reset did not work, attempting CPU shutdown. Any suggestions? -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.1-current | Seattle, WA 98105 |---------------------| From owner-freebsd-current Wed May 17 11:10:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA10536 for current-outgoing; Wed, 17 May 1995 11:10:19 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA10530 for ; Wed, 17 May 1995 11:10:15 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id LAA25818 for current@freebsd.org; Wed, 17 May 1995 11:10:14 -0700 From: Poul-Henning Kamp Message-Id: <199505171810.LAA25818@ref.tfs.com> Subject: please test this patch for panic("swfree") To: current@FreeBSD.org Date: Wed, 17 May 1995 11:10:14 -0700 (PDT) Content-Type: text Content-Length: 1026 Sender: current-owner@FreeBSD.org Precedence: bulk A typical "one off" error. Please test this patch. (David, Rod & John please review.) Poul-Henning Index: vm_swap.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_swap.c,v retrieving revision 1.17 diff -u -r1.17 vm_swap.c --- 1.17 1995/05/14 03:00:10 +++ vm_swap.c 1995/05/17 18:08:26 @@ -241,15 +241,11 @@ sp->sw_nblks = nblks; if (nblks * nswdev > nswap) - nswap = nblks * nswdev; + nswap = (nblks+1) * nswdev; for (dvbase = dmmax; dvbase < nblks; dvbase += dmmax) { blk = nblks - dvbase; - if ((vsbase = index * dmmax + dvbase * nswdev) >= nswap) - panic("swfree"); - if (blk > dmmax) - blk = dmmax; /* XXX -- we need to exclude the first cluster as above */ /* but for now, this will work fine... */ rlist_free(&swaplist, vsbase, vsbase + blk - 1); -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Wed May 17 12:37:32 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA12205 for current-outgoing; Wed, 17 May 1995 12:37:32 -0700 Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA12199 for ; Wed, 17 May 1995 12:37:29 -0700 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.11/8.6.9) id MAA00176; Wed, 17 May 1995 12:33:15 -0700 From: Steven G Kargl Message-Id: <199505171933.MAA00176@troutmask.apl.washington.edu> Subject: RE: panic: swfree To: freebsd-current@freefall.cdrom.com (FreeBSD Current) Date: Wed, 17 May 1995 12:33:15 -0700 (PDT) Cc: phk@ref.tfs.com X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1243 Sender: current-owner@FreeBSD.org Precedence: bulk >A typical "one off" error. Please test this patch. > >(David, Rod & John please review.) >Poul-Henning >Index: vm_swap.c >=================================================================== >RCS file: /home/ncvs/src/sys/vm/vm_swap.c,v >retrieving revision 1.17 >diff -u -r1.17 vm_swap.c >--- 1.17 1995/05/14 03:00:10 >+++ vm_swap.c 1995/05/17 18:08:26 >@@ -241,15 +241,11 @@ > sp->sw_nblks = nblks; > > if (nblks * nswdev > nswap) >- nswap = nblks * nswdev; >+ nswap = (nblks+1) * nswdev; > > for (dvbase = dmmax; dvbase < nblks; dvbase += dmmax) { > blk = nblks - dvbase; > >- if ((vsbase = index * dmmax + dvbase * nswdev) >= nswap) >- panic("swfree"); >- if (blk > dmmax) >- blk = dmmax; > /* XXX -- we need to exclude the first cluster as above */ > /* but for now, this will work fine... */ > rlist_free(&swaplist, vsbase, vsbase + blk - 1); > This patch gets rid of the swfree panic, but introduced a new one: panic: rlist_free: free start overlaps already freed area at list tail -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.1-current | Seattle, WA 98105 |---------------------| From owner-freebsd-current Wed May 17 12:53:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA12464 for current-outgoing; Wed, 17 May 1995 12:53:35 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA12456 for ; Wed, 17 May 1995 12:53:32 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA12236; Wed, 17 May 1995 12:52:56 -0700 From: "Rodney W. Grimes" Message-Id: <199505171952.MAA12236@gndrsh.aac.dev.com> Subject: Re: mtree incomplete To: fredriks@mcs.com (Lars Fredriksen) Date: Wed, 17 May 1995 12:52:56 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: from "Lars Fredriksen" at May 17, 95 10:28:34 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 468 Sender: current-owner@FreeBSD.org Precedence: bulk > > Hi, > It seems like the mtree is incomplete when it comes to > /usr/share/sgml/xxx where xxx is drd and rpt or some such. make install > failes when it tries to drop files into these directories. I just committed the fix to the mtree files last night, resup and try again. Almost 120 lines got added!!! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Wed May 17 12:55:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA12516 for current-outgoing; Wed, 17 May 1995 12:55:11 -0700 Received: from jukebox.MI.Uni-Koeln.DE (jukebox.MI.Uni-Koeln.DE [134.95.212.11]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA12510 for ; Wed, 17 May 1995 12:55:08 -0700 Received: by jukebox.MI.Uni-Koeln.DE id AA14186 (5.67b/IDA-1.5 for current@freebsd.org); Wed, 17 May 1995 21:54:16 +0200 Message-Id: <199505171954.AA14186@jukebox.MI.Uni-Koeln.DE> From: esser@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Wed, 17 May 1995 21:54:16 +0200 In-Reply-To: "Rodney W. Grimes" "Re: Enthusiasm boost: make world works on 386SX16 4Mb" (May 17, 2:49) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "Rodney W. Grimes" Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk On May 17, 2:49, "Rodney W. Grimes" wrote: } Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb } > PS. Those of you with a trivia fixation can enjoy the following: } > 'make world' caused 60 million wdc0 interrupts and 6 million ed0 interrupts. } } Humm.. to bad the PCI code is broken in this area, it would be interesting } to compare the number of interrupts to a scsi system running make world. Well, I looked into this. The problem is, that the current interrupt statistics scheme is tightly bound to ISA. The register_intr() function gets a device_id, which is used to initialise the intr_countp[] and intrnames[] arrays. Since device_id is an index into an ISA specific data structure (which doesn't make much sense for a PCI device), there is no valid device_id for any PCI device. The easy solution to this problem would be to make register_intr() less specific to ISA by passing an &intrcnt and an intrname parameter instead of the ISA device id. This would require (very simple) changes to: /sys/i386/isa/isa_device.h (prototype) /sys/i386/isa/isa.c (definition + a few calls) /sys/i386/isa/clock.c (2 calls) /sys/i386/isa/pcibus.c (1 call) /sys/i386/eisa/eisaconf.c (1 call) Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706017 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Wed May 17 13:09:12 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA12793 for current-outgoing; Wed, 17 May 1995 13:09:12 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA12787 for ; Wed, 17 May 1995 13:09:06 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA12294; Wed, 17 May 1995 13:08:43 -0700 From: "Rodney W. Grimes" Message-Id: <199505172008.NAA12294@gndrsh.aac.dev.com> Subject: Re: please test this patch for panic("swfree") To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 17 May 1995 13:08:43 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505171810.LAA25818@ref.tfs.com> from "Poul-Henning Kamp" at May 17, 95 11:10:14 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1408 Sender: current-owner@FreeBSD.org Precedence: bulk > > A typical "one off" error. Please test this patch. > > (David, Rod & John please review.) > > Poul-Henning > > Index: vm_swap.c > =================================================================== > RCS file: /home/ncvs/src/sys/vm/vm_swap.c,v > retrieving revision 1.17 > diff -u -r1.17 vm_swap.c > --- 1.17 1995/05/14 03:00:10 > +++ vm_swap.c 1995/05/17 18:08:26 > @@ -241,15 +241,11 @@ > sp->sw_nblks = nblks; > > if (nblks * nswdev > nswap) > - nswap = nblks * nswdev; > + nswap = (nblks+1) * nswdev; Okay! > > for (dvbase = dmmax; dvbase < nblks; dvbase += dmmax) { > blk = nblks - dvbase; > > - if ((vsbase = index * dmmax + dvbase * nswdev) >= nswap) > - panic("swfree"); Not Okay, please correct the calculation to do the right check, not eliminate the sanify check. > - if (blk > dmmax) > - blk = dmmax; Should this be another panic condition??? > /* XXX -- we need to exclude the first cluster as above */ > /* but for now, this will work fine... */ > rlist_free(&swaplist, vsbase, vsbase + blk - 1); > > -- > Poul-Henning Kamp -- TRW Financial Systems, Inc. > 'All relevant people are pertinent' && 'All rude people are impertinent' > => 'no rude people are relevant' > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Wed May 17 13:15:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA13001 for current-outgoing; Wed, 17 May 1995 13:15:47 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA12995 for ; Wed, 17 May 1995 13:15:43 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA26175; Wed, 17 May 1995 13:15:36 -0700 From: Poul-Henning Kamp Message-Id: <199505172015.NAA26175@ref.tfs.com> Subject: Re: please test this patch for panic("swfree") To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Wed, 17 May 1995 13:15:36 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505172008.NAA12294@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 17, 95 01:08:43 pm Content-Type: text Content-Length: 802 Sender: current-owner@FreeBSD.org Precedence: bulk > > @@ -241,15 +241,11 @@ > > sp->sw_nblks = nblks; > > > > if (nblks * nswdev > nswap) > > - nswap = nblks * nswdev; > > + nswap = (nblks+1) * nswdev; > > Okay! > > > > > for (dvbase = dmmax; dvbase < nblks; dvbase += dmmax) { > > blk = nblks - dvbase; > > > > - if ((vsbase = index * dmmax + dvbase * nswdev) >= nswap) > > - panic("swfree"); > > Not Okay, please correct the calculation to do the right check, not > eliminate the sanify check. > Rod, if you do your math, you will see that this cannot fail. > > - blk = dmmax; > > Should this be another panic condition??? See other email. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Wed May 17 13:23:36 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA13272 for current-outgoing; Wed, 17 May 1995 13:23:36 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA13266 for ; Wed, 17 May 1995 13:23:25 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA12370; Wed, 17 May 1995 13:23:03 -0700 From: "Rodney W. Grimes" Message-Id: <199505172023.NAA12370@gndrsh.aac.dev.com> Subject: Re: please test this patch for panic("swfree") To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 17 May 1995 13:23:03 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505172015.NAA26175@ref.tfs.com> from "Poul-Henning Kamp" at May 17, 95 01:15:36 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1078 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > @@ -241,15 +241,11 @@ > > > sp->sw_nblks = nblks; > > > > > > if (nblks * nswdev > nswap) > > > - nswap = nblks * nswdev; > > > + nswap = (nblks+1) * nswdev; > > > > Okay! > > > > > > > > for (dvbase = dmmax; dvbase < nblks; dvbase += dmmax) { > > > blk = nblks - dvbase; > > > > > > - if ((vsbase = index * dmmax + dvbase * nswdev) >= nswap) > > > - panic("swfree"); > > > > Not Okay, please correct the calculation to do the right check, not > > eliminate the sanify check. > > > Rod, if you do your math, you will see that this cannot fail. It can fail if any of the values for some other off by one error goes out of range! > > > > - blk = dmmax; > > > > Should this be another panic condition??? > > See other email. See other mail, some one is now panicing in the call right after this. ARGHHH!!! This is not the time to have to start in on debugging this type of problem! -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Wed May 17 13:27:15 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA13422 for current-outgoing; Wed, 17 May 1995 13:27:15 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA13415 for ; Wed, 17 May 1995 13:27:14 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id NAA26237; Wed, 17 May 1995 13:27:09 -0700 From: Poul-Henning Kamp Message-Id: <199505172027.NAA26237@ref.tfs.com> Subject: Re: please test this patch for panic("swfree") To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Wed, 17 May 1995 13:27:09 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505172023.NAA12370@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 17, 95 01:23:03 pm Content-Type: text Content-Length: 599 Sender: current-owner@FreeBSD.org Precedence: bulk > > > Should this be another panic condition??? > > > > See other email. > > See other mail, some one is now panicing in the call right after this. > > ARGHHH!!! This is not the time to have to start in on debugging this > type of problem! Rod, I'm trying to resolve this problem as fast as I can. I don't exactly think that your screaming and yelling facilitates the process. so if you don't mind: GET LOST ! -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Wed May 17 13:32:47 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA13605 for current-outgoing; Wed, 17 May 1995 13:32:47 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA13590 for ; Wed, 17 May 1995 13:32:38 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id GAA28969; Thu, 18 May 1995 06:31:33 +1000 Date: Thu, 18 May 1995 06:31:33 +1000 From: Bruce Evans Message-Id: <199505172031.GAA28969@godzilla.zeta.org.au> To: bugs@ns1.win.net, current@FreeBSD.org Subject: Re: -cur boot hangs since may 1 Sender: current-owner@FreeBSD.org Precedence: bulk >If you disable ie0 during a '-c' boot dialog (or build a kernel without ie0) >then things work great. >All my boxes have ep0 cards so I have been an unhappy boy for many days. >I am looking at the probe technique in the ie0 driver to see what has >been changed. It may be confusing the 3c509 card. This is a known bug and was worked around in revision 1.20 (1994/11/18) of GENERIC. Log: Put ie0 above ep0. Otherwise, the ie0 probe clobbers it. The work around was broken by sorting the devices in revision 1.38 (1995/04/08). The conflict is probably because if_ie.c uses port ELINK_ID_PORT which is defined in elink.h as 0x100 and if_ep.c uses port EP_ID_PORT which is defined in if_epreg.h as 0x100. The conflict is not detected because use of these ports is not recorded in the config file (there is no room for it) and the base ports don't conflict. The conflict is not obvious in isa.h because few or no network ports are recorded there. Bruce From owner-freebsd-current Wed May 17 13:51:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA14157 for current-outgoing; Wed, 17 May 1995 13:51:25 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA14151 for ; Wed, 17 May 1995 13:51:21 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id NAA12426; Wed, 17 May 1995 13:50:59 -0700 From: "Rodney W. Grimes" Message-Id: <199505172050.NAA12426@gndrsh.aac.dev.com> Subject: Re: please test this patch for panic("swfree") To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 17 May 1995 13:50:59 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505172027.NAA26237@ref.tfs.com> from "Poul-Henning Kamp" at May 17, 95 01:27:09 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1029 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > > Should this be another panic condition??? > > > > > > See other email. > > > > See other mail, some one is now panicing in the call right after this. > > > > ARGHHH!!! This is not the time to have to start in on debugging this > > type of problem! > > Rod, I'm trying to resolve this problem as fast as I can. > > I don't exactly think that your screaming and yelling facilitates the process. > You don't get it do you Poul, I was rather strongly against makeing these swap changes to support some new install mode, now that the other over rode me on it we are sitting at day 4 of code freeze with a rather critical class bug that did not exist at the start of code freeze :-(. Well, so much for following the rules, we never do seem to do it. > so if you don't mind: GET LOST ! BUGGER OFF with that attitude, we don't need it right now :-) :-) :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Wed May 17 13:55:45 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA14373 for current-outgoing; Wed, 17 May 1995 13:55:45 -0700 Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.97.216]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA14367 for ; Wed, 17 May 1995 13:55:43 -0700 Received: (from kargl@localhost) by troutmask.apl.washington.edu (8.6.11/8.6.9) id NAA00355; Wed, 17 May 1995 13:51:20 -0700 From: Steven G Kargl Message-Id: <199505172051.NAA00355@troutmask.apl.washington.edu> Subject: Re: please test this patch for panic("swfree") To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Wed, 17 May 1995 13:51:20 -0700 (PDT) Cc: phk@ref.tfs.com, current@FreeBSD.org In-Reply-To: <199505172008.NAA12294@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 17, 95 01:08:43 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 929 Sender: current-owner@FreeBSD.org Precedence: bulk According to Rodney W. Grimes: > > > > > for (dvbase = dmmax; dvbase < nblks; dvbase += dmmax) { > > blk = nblks - dvbase; > > > > - if ((vsbase = index * dmmax + dvbase * nswdev) >= nswap) > > - panic("swfree"); > > Not Okay, please correct the calculation to do the right check, not > eliminate the sanify check. > > > - if (blk > dmmax) > > - blk = dmmax; > > Should this be another panic condition??? > > > /* XXX -- we need to exclude the first cluster as above */ > > /* but for now, this will work fine... */ > > rlist_free(&swaplist, vsbase, vsbase + blk - 1); > > Yes, you get another panic. panic: rlist_free: free start overlaps already freed area at list tail -- Steven G. Kargl | Phone: 206-685-4677 | Applied Physics Lab | Fax: 206-543-6785 | Univ. of Washington |---------------------| 1013 NE 40th St | FreeBSD 2.1-current | Seattle, WA 98105 |---------------------| From owner-freebsd-current Wed May 17 14:05:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA14644 for current-outgoing; Wed, 17 May 1995 14:05:25 -0700 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA14638 for ; Wed, 17 May 1995 14:05:22 -0700 Received: (dyson@localhost) by Root.COM (8.6.8/8.6.5) id OAA10795; Wed, 17 May 1995 14:08:18 -0700 Date: Wed, 17 May 1995 14:08:18 -0700 From: John Dyson Message-Id: <199505172108.OAA10795@Root.COM> To: kargl@troutmask.apl.washington.edu, rgrimes@gndrsh.aac.dev.com Subject: Re: please test this patch for panic("swfree") Cc: current@FreeBSD.org, phk@ref.tfs.com Sender: current-owner@FreeBSD.org Precedence: bulk I replied in private email to phk that you need to keep the check: if( blk > dmmax) blk = dmmax; That is part of the algorithm -- not just a bogus safety check :-). I think that the rlist_free problem will go-away. Sorry I did not respond earlier, but I am at work and dont have very good net access right now :-(. John dyson@root.com From owner-freebsd-current Wed May 17 14:17:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA14846 for current-outgoing; Wed, 17 May 1995 14:17:14 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id OAA14839 for ; Wed, 17 May 1995 14:17:07 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id HAA29877; Thu, 18 May 1995 07:12:33 +1000 Date: Thu, 18 May 1995 07:12:33 +1000 From: Bruce Evans Message-Id: <199505172112.HAA29877@godzilla.zeta.org.au> To: esser@ZPR.Uni-Koeln.DE, rgrimes@gndrsh.aac.dev.com Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >The problem is, that the current interrupt statistics scheme is >tightly bound to ISA. >The register_intr() function gets a device_id, which is used to >initialise the intr_countp[] and intrnames[] arrays. Urk. You currently use device_id 0, so all pci interrupts get counted as clock interrupts. >Since device_id is an index into an ISA specific data structure >(which doesn't make much sense for a PCI device), there is no >valid device_id for any PCI device. It's actually only an index into intr_countp[] and intrnames[]. Config is supposed to fill in all device tables with suitable indexes and build a string table to match. You can fake this now using dummy isa devices: device PCI0 at isa? ... device PCI15 at isa? Use a trivial failing probe routine to copy the ids to a pci-specific place. >The easy solution to this problem would be to make register_intr() >less specific to ISA by passing an &intrcnt and an intrname >parameter instead of the ISA device id. >This would require (very simple) changes to: >/sys/i386/isa/isa_device.h (prototype) >/sys/i386/isa/isa.c (definition + a few calls) >/sys/i386/isa/clock.c (2 calls) >/sys/i386/isa/pcibus.c (1 call) >/sys/i386/eisa/eisaconf.c (1 call) It would also require changing intrnames[] from a string table to an array and changing systat etc. to expect an array. This should be done someday. Bruce From owner-freebsd-current Wed May 17 14:31:13 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA15035 for current-outgoing; Wed, 17 May 1995 14:31:13 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA15028 for ; Wed, 17 May 1995 14:31:11 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA05623 (5.67b/IDA-1.5 for current@freebsd.org); Wed, 17 May 1995 23:30:53 +0200 Message-Id: <199505172130.AA05623@FileServ1.MI.Uni-Koeln.DE> From: esser@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Wed, 17 May 1995 23:30:52 +0200 In-Reply-To: Bruce Evans "Re: Enthusiasm boost: make world works on 386SX16 4Mb" (May 18, 7:12) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bruce Evans Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk On May 18, 7:12, Bruce Evans wrote: } Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb } >The problem is, that the current interrupt statistics scheme is } >tightly bound to ISA. } } >The register_intr() function gets a device_id, which is used to } >initialise the intr_countp[] and intrnames[] arrays. } } Urk. You currently use device_id 0, so all pci interrupts get } counted as clock interrupts. Well, this particular line is Wolfgang's code, not mine :) Yes. I noticed the same when I looked for a way to tally PCI interrupts ... Calling "register_intr() with an device_id argument of -1 would fix this without introducing further problems, but I didn't want to apply such a fix before 2.0.5 is out. (It's a local change without any bad consequences, perhaps it should be made just now, though ???) } >Since device_id is an index into an ISA specific data structure } >(which doesn't make much sense for a PCI device), there is no } >valid device_id for any PCI device. } } It's actually only an index into intr_countp[] and intrnames[]. } Config is supposed to fill in all device tables with suitable } indexes and build a string table to match. You can fake this } now using dummy isa devices: } } device PCI0 at isa? } ... } device PCI15 at isa? } } Use a trivial failing probe routine to copy the ids to a pci-specific } place. Yes. Know this. But this would be to much of a hack IMHO ! } >The easy solution to this problem would be to make register_intr() } >less specific to ISA by passing an &intrcnt and an intrname } >parameter instead of the ISA device id. } } >This would require (very simple) changes to: } } >/sys/i386/isa/isa_device.h (prototype) } >/sys/i386/isa/isa.c (definition + a few calls) } >/sys/i386/isa/clock.c (2 calls) } >/sys/i386/isa/pcibus.c (1 call) } >/sys/i386/eisa/eisaconf.c (1 call) } } It would also require changing intrnames[] from a string table to an } array and changing systat etc. to expect an array. This should be Not necessarily ... I've locally patched "config" to put pci devices into "vector.h". This makes the names appear in the intrnames array, it just can't be located by the register_intr() code. By having an explicit intrcnt address and another name parameter, register_intr() could match the name in the intrnames array as build by the modified config. All statistic tools could then stay unchanged for now. Later register_intr() could use the same parameters to initialise an array of char pointers, and systat etc be patched to expect such an array ... Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706017 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Wed May 17 14:45:52 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA15253 for current-outgoing; Wed, 17 May 1995 14:45:52 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA15247 for ; Wed, 17 May 1995 14:45:48 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA19931; Tue, 16 May 95 11:27:41 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9505161727.AA19931@cs.weber.edu> Subject: Re: bin/407: Odd tset -I behaviour, termcap says xterm kb=^H To: hsu@cs.hut.fi (Heikki Suonsivu) Date: Tue, 16 May 95 11:27:41 MDT Cc: freebsd-current@freefall.cdrom.com In-Reply-To: <199505160816.LAA14553@shadows.cs.hut.fi> from "Heikki Suonsivu" at May 16, 95 11:16:04 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > Most X terminals interpret this as a request to send an ASCII Backspace > character (^H, 0x08) to the slave side of the PTY they are using. > > The Tektronics X terminals here send ^? and have the key most people talk > about as "Backspace" labelled with left-arrow. Ditto for all workstations > here, though they are mostly Suns or Linux PC's. The Xterminals send no such thing. They send an X keycode -- they don't talk ASCII at all, they talk X. It is your Xterm program that you are running against your X terminal that is putting the ASCII value out based on the keycode it gets in the XKeyPressEvent. In other words, it is a configuration issue for your xterm. Since the xterm stuffs its termcap into the environment for the child program on the slave side of the pty (usually your shell), the issue is making it provide the correct termcap 'le' capability to identify the left arrow so that tset (which you should run) can set the tty erase character correctly. Alternately, you can change the keycode for the erase character on the X terminal globally (or leave it as whatever it is), and then use xrdb to intern an atom for the xterm TtyModes capability to match the xterm. This should be done as part of running xdm on the terminal and causing a login (see the xdm documentation), or as part of the user's .xinitrc if the X server is started from a command line instead of from xdm by init (see the xdm documentation). Either way, any xterm program that runs against the X server is going to prefer the interned atom (which it is your job as system administrator to ensure matches the keycode on a per X terminal basis) to the user's .Xdefaults value (which could be correct only for one terminal) or the xterm defaults compiled into the program. This would resolve the issue entirely for all xterms consuming the display services of your X server, regardless of origin. > I would say that your console is configured incorrectly by default > to send and ASCII 0x7f (delete, ^?) instead of an ASCII backspace for > your key labelled "Backspace", and that the default tty modes for > > I don't care about the damn labels, but the function of the keys. I expect > the big key above enter/return/whatever to erase the previously typed > character, and thus it needs to send ^? unless ANSI has changed its mind (I > have only seen a quote from the standard, though). The conclusion "thus it needs to send ^?" is incorrect, and is based on what you presume are the default tty modes for the terminal. It would be more correct to say that the value that that key sends should be encoded on a per terminal type basis in the /etc/termcap file as the 'le' capability, and the terminal type should be specified on the getty line in the /etc/ttys file so that getty can do the correct thing by initializing the correct erase character. For logins not through getty (or through mgetty, which has not been sufficiently BSDized), the users shell initialization is expected to invoke "tset", which is expected to cause the 'le' capability to be loaded as the tty erase character. > I'm willing to pay for > related standards from ANSI for FreeBSD group so that we can get rid of > this confusion. There are at least three standards related to ASCII, X3.4, > X3.41 and X3.32, I don't know which one is the one which specifies the > correct usage but I can pay them all, it should be less than $200 in total > including shipping, probably less, $100-$150. Which snail address I should > order them to in case ANSI agrees to ship them directly even when order > comes from abroad? I believe the standard you want is X3.64, which covers key codes sent, and escape sequences processed, by ANSI compliant terminals. I believe since the console software presumes to VTxxx series compliance that you will want the 1977 version of this standard. I'd send you a copy of mine, but I'm reluctant to violate copyright. ANSI standards *do not specify* key arrangement vs. ASCII code returned. > The Telnet and Rlogin arguments don't hold water here because the > erase character is a negotiated option. > > rlogin doesn't negotiate this, just the terminal type (but rlogin > "protocol" is high in brokeness scale anyway). Telnet we don't use much as > it keeps asking stupid passwords sent as cleartext over network. rlogin > will be replaced RSN by a better method :) Negotiation of the terminal type is sufficient to provide an 'le' capability to the tset program, which is expected to be run in your .login or .profile depending on your shell choice. Regards, Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed May 17 15:04:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA15521 for current-outgoing; Wed, 17 May 1995 15:04:35 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id PAA15515 for ; Wed, 17 May 1995 15:04:27 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA06012 (5.67b/IDA-1.5 for current@freebsd.org); Thu, 18 May 1995 00:04:24 +0200 Message-Id: <199505172204.AA06012@FileServ1.MI.Uni-Koeln.DE> From: esser@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Thu, 18 May 1995 00:04:24 +0200 X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: current@FreeBSD.org Subject: EATA SCSI driver Cc: neuffer@trudi.zdv.uni-mainz.de Sender: current-owner@FreeBSD.org Precedence: bulk This seems to be an interesting offer: I've got mail from Michael Neuffer, wrote a driver for DPT SCSI controllers that has been part of Linux for quite some time now. He says there have been some requests to port this driver directed at him via e-mail, and he now wants to make sure, that currently nobody else is working on support for that controller family. If you know of anything with regard to a DPT SCSI driver written for *BSD, please send mail to Michael Neuffer . (And in case you know that nobody else ever offered to write or port such a driver, this would be interesting news, too). Regards, STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706017 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Wed May 17 15:12:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA15698 for current-outgoing; Wed, 17 May 1995 15:12:27 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA15692 for ; Wed, 17 May 1995 15:12:26 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id PAA26695; Wed, 17 May 1995 15:12:20 -0700 From: Poul-Henning Kamp Message-Id: <199505172212.PAA26695@ref.tfs.com> Subject: Re: please test this patch for panic("swfree") To: rgrimes@gndrsh.aac.dev.com (Rodney W. Grimes) Date: Wed, 17 May 1995 15:12:20 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505172050.NAA12426@gndrsh.aac.dev.com> from "Rodney W. Grimes" at May 17, 95 01:50:59 pm Content-Type: text Content-Length: 903 Sender: current-owner@FreeBSD.org Precedence: bulk > > Rod, I'm trying to resolve this problem as fast as I can. > > > > I don't exactly think that your screaming and yelling facilitates the process. > > > > You don't get it do you Poul, I was rather strongly against makeing these > swap changes to support some new install mode, now that the other over > rode me on it we are sitting at day 4 of code freeze with a rather > critical class bug that did not exist at the start of code freeze :-(. You don't get it, do you Rod ? Sysinstall would fail without these changes. > Well, so much for following the rules, we never do seem to do it. > > > so if you don't mind: GET LOST ! > > BUGGER OFF with that attitude, we don't need it right now :-) :-) :-) Exactly. -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Wed May 17 15:17:54 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA15834 for current-outgoing; Wed, 17 May 1995 15:17:54 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA15828 for ; Wed, 17 May 1995 15:17:53 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id PAA26749; Wed, 17 May 1995 15:17:34 -0700 From: Poul-Henning Kamp Message-Id: <199505172217.PAA26749@ref.tfs.com> Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb To: esser@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Wed, 17 May 1995 15:17:33 -0700 (PDT) Cc: bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199505172130.AA05623@FileServ1.MI.Uni-Koeln.DE> from "Stefan Esser" at May 17, 95 11:30:52 pm Content-Type: text Content-Length: 883 Sender: current-owner@FreeBSD.org Precedence: bulk > On May 18, 7:12, Bruce Evans wrote: > } Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb > } >The problem is, that the current interrupt statistics scheme is > } >tightly bound to ISA. > } > } >The register_intr() function gets a device_id, which is used to > } >initialise the intr_countp[] and intrnames[] arrays. > } > } Urk. You currently use device_id 0, so all pci interrupts get > } counted as clock interrupts. > > Well, this particular line is Wolfgang's code, not mine :) > > Yes. I noticed the same when I looked for a way to tally > PCI interrupts ... I can't belive that we found a serious statistical problem in the PCI code by running make world on a 386SX :-) -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Wed May 17 15:21:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA15889 for current-outgoing; Wed, 17 May 1995 15:21:24 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA15883 for ; Wed, 17 May 1995 15:21:21 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id PAA12752; Wed, 17 May 1995 15:20:59 -0700 From: "Rodney W. Grimes" Message-Id: <199505172220.PAA12752@gndrsh.aac.dev.com> Subject: Re: please test this patch for panic("swfree") To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 17 May 1995 15:20:59 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505172212.PAA26695@ref.tfs.com> from "Poul-Henning Kamp" at May 17, 95 03:12:20 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 840 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > Rod, I'm trying to resolve this problem as fast as I can. > > > > > > I don't exactly think that your screaming and yelling facilitates the process. > > > > > > > You don't get it do you Poul, I was rather strongly against makeing these > > swap changes to support some new install mode, now that the other over > > rode me on it we are sitting at day 4 of code freeze with a rather > > critical class bug that did not exist at the start of code freeze :-(. > > You don't get it, do you Rod ? Sysinstall would fail without these > changes. Bull SHIT! It just would have required a reboot, gee, we traded a reboot for a kernel bug.. not nice. New feature, new bug :-(. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Wed May 17 15:22:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id PAA15901 for current-outgoing; Wed, 17 May 1995 15:22:42 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id PAA15895 for ; Wed, 17 May 1995 15:22:39 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id PAA12762; Wed, 17 May 1995 15:21:43 -0700 From: "Rodney W. Grimes" Message-Id: <199505172221.PAA12762@gndrsh.aac.dev.com> Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb To: phk@ref.tfs.com (Poul-Henning Kamp) Date: Wed, 17 May 1995 15:21:43 -0700 (PDT) Cc: esser@ZPR.Uni-Koeln.DE, bde@zeta.org.au, current@FreeBSD.org In-Reply-To: <199505172217.PAA26749@ref.tfs.com> from "Poul-Henning Kamp" at May 17, 95 03:17:33 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1014 Sender: current-owner@FreeBSD.org Precedence: bulk > > > On May 18, 7:12, Bruce Evans wrote: > > } Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb > > } >The problem is, that the current interrupt statistics scheme is > > } >tightly bound to ISA. > > } > > } >The register_intr() function gets a device_id, which is used to > > } >initialise the intr_countp[] and intrnames[] arrays. > > } > > } Urk. You currently use device_id 0, so all pci interrupts get > > } counted as clock interrupts. > > > > Well, this particular line is Wolfgang's code, not mine :) > > > > Yes. I noticed the same when I looked for a way to tally > > PCI interrupts ... > > I can't belive that we found a serious statistical problem in the PCI > code by running make world on a 386SX :-) I've known about the statistical bug for over 2 months, and knew that it was counting them on the clock interrupt. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Thu May 18 00:01:14 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA27067 for current-outgoing; Thu, 18 May 1995 00:01:14 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id AAA27060 ; Thu, 18 May 1995 00:01:13 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: "Rodney W. Grimes" cc: phk@ref.tfs.com (Poul-Henning Kamp), current@FreeBSD.org Subject: Re: please test this patch for panic("swfree") In-reply-to: Your message of "Wed, 17 May 95 15:20:59 PDT." <199505172220.PAA12752@gndrsh.aac.dev.com> Date: Thu, 18 May 1995 00:01:13 -0700 Message-ID: <27058.800780473@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk Boys, boys! Take this OFFLINE, please! You're both looking like prize idiots from where I'm standing. Jordan From owner-freebsd-current Thu May 18 03:27:58 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id DAA04875 for current-outgoing; Thu, 18 May 1995 03:27:58 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA04869 for ; Thu, 18 May 1995 03:27:46 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA19723; Thu, 18 May 1995 20:20:00 +1000 Date: Thu, 18 May 1995 20:20:00 +1000 From: Bruce Evans Message-Id: <199505181020.UAA19723@godzilla.zeta.org.au> To: bde@zeta.org.au, esser@ZPR.Uni-Koeln.DE Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >} It's actually only an index into intr_countp[] and intrnames[]. >} Config is supposed to fill in all device tables with suitable >} indexes and build a string table to match. You can fake this >} now using dummy isa devices: >} >} device PCI0 at isa? >} ... >} device PCI15 at isa? >} >} Use a trivial failing probe routine to copy the ids to a pci-specific >} place. >Yes. Know this. But this would be to much of a hack IMHO ! It seems reasonable to have a real to have a real isa device behind the glue routines in isa/pcibus.c. >I've locally patched "config" to put pci devices into >"vector.h". This makes the names appear in the intrnames >array, it just can't be located by the register_intr() >code. >By having an explicit intrcnt address and another name >parameter, register_intr() could match the name in the >intrnames array as build by the modified config. OK. Put all the controller names in the string table so that you don't have to decide which. Bruce From owner-freebsd-current Thu May 18 04:17:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA06239 for current-outgoing; Thu, 18 May 1995 04:17:57 -0700 Received: from veda.is (veda.is [193.4.230.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA06230 ; Thu, 18 May 1995 04:17:25 -0700 Received: (from adam@localhost) by veda.is (8.6.8/8.6.6) id LAA01093; Thu, 18 May 1995 11:20:23 GMT From: Adam David Message-Id: <199505181120.LAA01093@veda.is> Subject: spurious EOF To: thud-users@FreeBSD.org Date: Thu, 18 May 1995 11:20:22 +0000 (GMT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Content-Length: 234 Sender: current-owner@FreeBSD.org Precedence: bulk This error occured while building on thud today (NFS mounted from freefall)... ld: swap.o: read_strings: premature end of file in strings I removed swap.o and rebuilt without error. What happened here? -- Adam David From owner-freebsd-current Thu May 18 04:40:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA06627 for current-outgoing; Thu, 18 May 1995 04:40:27 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA06621 for ; Thu, 18 May 1995 04:40:25 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id HAA04517; Thu, 18 May 1995 07:40:12 -0400 From: Peter Dufault Message-Id: <199505181140.HAA04517@hda.com> Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb To: bde@zeta.org.au (Bruce Evans) Date: Thu, 18 May 1995 07:40:12 -0400 (EDT) Cc: bde@zeta.org.au, esser@ZPR.Uni-Koeln.DE, current@FreeBSD.org In-Reply-To: <199505181020.UAA19723@godzilla.zeta.org.au> from "Bruce Evans" at May 18, 95 08:20:00 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 532 Sender: current-owner@FreeBSD.org Precedence: bulk Bruce Evans writes: > > OK. Put all the controller names in the string table so > that you don't have to decide which. > While you're looking at this think a little about the issues involved with LKM's adding interrupts. At least a little. The last time I looked there was no way to add to the name table and no complete way to add your interrupts. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Thu May 18 05:39:39 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id FAA07093 for current-outgoing; Thu, 18 May 1995 05:39:39 -0700 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id FAA07085 ; Thu, 18 May 1995 05:39:27 -0700 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id IAA04678; Thu, 18 May 1995 08:39:35 -0400 From: Peter Dufault Message-Id: <199505181239.IAA04678@hda.com> Subject: Re: spurious EOF To: adam@veda.is (Adam David) Date: Thu, 18 May 1995 08:39:35 -0400 (EDT) Cc: thud-users@FreeBSD.org, current@FreeBSD.org In-Reply-To: <199505181120.LAA01093@veda.is> from "Adam David" at May 18, 95 11:20:22 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 648 Sender: current-owner@FreeBSD.org Precedence: bulk Adam David writes: > > This error occured while building on thud today (NFS mounted from freefall)... > > ld: swap.o: read_strings: premature end of file in strings > > I removed swap.o and rebuilt without error. What happened here? I don't know, but I've had similar ld error messages with those "strange LKM" problems that I've mentioned. If it happens again save the .o file and then cmp it against the working one to see if you have blocks of zeros in the file. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-current Thu May 18 05:43:44 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA05618 for current-outgoing; Thu, 18 May 1995 04:01:40 -0700 Received: from wc.cdrom.com (wc.cdrom.com [192.216.223.37]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA05612 for ; Thu, 18 May 1995 04:01:38 -0700 Received: from FileServ1.MI.Uni-Koeln.DE (FileServ1.MI.Uni-Koeln.DE [134.95.212.1]) by wc.cdrom.com (8.6.12/8.6.12) with SMTP id EAA21057 for ; Thu, 18 May 1995 04:01:43 -0700 Received: by FileServ1.MI.Uni-Koeln.DE id AA14966 (5.67b/IDA-1.5 for current@freebsd.org); Thu, 18 May 1995 12:55:57 +0200 Message-Id: <199505181055.AA14966@FileServ1.MI.Uni-Koeln.DE> From: esser@ZPR.Uni-Koeln.DE (Stefan Esser) Date: Thu, 18 May 1995 12:55:57 +0200 In-Reply-To: Bruce Evans "Re: Enthusiasm boost: make world works on 386SX16 4Mb" (May 18, 20:20) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Bruce Evans Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb Cc: current@freebsd.org Sender: current-owner@freebsd.org Precedence: bulk On May 18, 20:20, Bruce Evans wrote: } Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb I've got one new idea regarding tallying PCI interrupts. Not a solution, but an easy workaround for now: How about reserving the "0" entry in intrcnt[] and the intrnames list for PCI ? Having "config" generate "vector.h" accordingly, if a "controller pci0" entry was found would be trivial. This would make the device_id of 0 do the right thing, though there was only one combined counter for all PCI interrupts for now. } >} It's actually only an index into intr_countp[] and intrnames[]. } >} Config is supposed to fill in all device tables with suitable } >} indexes and build a string table to match. You can fake this } >} now using dummy isa devices: } >} } >} device PCI0 at isa? } >} ... } >} device PCI15 at isa? } >} } >} Use a trivial failing probe routine to copy the ids to a pci-specific } >} place. } } >Yes. Know this. But this would be to much of a hack IMHO ! } } It seems reasonable to have a real to have a real isa device } behind the glue routines in isa/pcibus.c. Hmm, don't quite understand ... PCI device structures can be dynamically configured. PCI interrupts can be shared (i.e. any number of similar or even totally unrelated devices connected to one IRQ). I don't see PCI as a bus "behind" ISA, even though this is reality in today's predominant PCI system base ... } >I've locally patched "config" to put pci devices into } >"vector.h". This makes the names appear in the intrnames } >array, it just can't be located by the register_intr() } >code. } } >By having an explicit intrcnt address and another name } >parameter, register_intr() could match the name in the } >intrnames array as build by the modified config. } } OK. Put all the controller names in the string table so } that you don't have to decide which. To support PCI devices, I've got to put some number of each into the string table. E.g. the "de" driver can be used with 4channel Ethernet cards, which will all use the same IRQ, but are independent devices and should get private intrcnt values, IMHO. So it might be useful to have some 8 entries for each PCI driver, as long as a fixed string table is used. But this won't do for loadable device drivers and really is no good match for PCI neither. STefan -- Stefan Esser Internet: Zentrum fuer Paralleles Rechnen Tel: +49 221 4706017 Universitaet zu Koeln FAX: +49 221 4705160 Weyertal 80 50931 Koeln From owner-freebsd-current Thu May 18 06:02:28 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id GAA07490 for current-outgoing; Thu, 18 May 1995 06:02:28 -0700 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id GAA07483 for ; Thu, 18 May 1995 06:02:26 -0700 Received: from rks32.pcs.dec.com by inet-gw-1.pa.dec.com (5.65/24Feb95) id AA19603; Thu, 18 May 95 05:58:33 -0700 Received: by rks32.pcs.dec.com (Smail3.1.27.1 #16) id m0sC55a-0005PIC; Thu, 18 May 95 14:54 MSZ Message-Id: To: current%freebsd.org@inet-gw-1.pa.dec.com Subject: bios boot bug ? Reply-To: gj@FreeBSD.org Date: Thu, 18 May 95 12:54:06 GMT From: "gj%pcs.dec.com@inet-gw-1.pa.dec.com" Sender: current-owner@FreeBSD.org Precedence: bulk I tried to boot a newly installed system last night using the new bios boot code (generated on May 13). No matter what values I used in fdisk I always got "partition is out of reach from the bios" Looking at the code, the following fragment from disk.c appears bogus: /* This little trick is for OnTrack DiskManager disks */ boff = dl->d_partitions[part].p_offset - dl->d_partitions[2].p_offset + sector; /* This is a good idea for all disks */ bsize = dl->d_partitions[part].p_size; bend = boff + bsize - 1 ; if (bend / spc > 1024) { printf("partition is out of reach from the bios\n"); return 1; } spc is sectors per cylinder. The problem is that the values in the disklabel are byte values, not sector values. Or has this changed without me noticing ? When I commented out this fragment, I was at least able to load /kernel (then I ran into problems with the f*cking disk slice code...grrr). Seems like this should read /* This little trick is for OnTrack DiskManager disks */ boff = (dl->d_partitions[part].p_offset - dl->d_partitions[2].p_offset) >> 9 + sector; /* This is a good idea for all disks */ bsize = dl->d_partitions[part].p_size; bend = boff + (bsize >> 9) - 1 ; if (bend / spc > 1024) { printf("partition is out of reach from the bios\n"); return 1; } to convert to sectors. Note that I haven't tried out this change, I'm at work. Am I totally fubar here ? Gary J. From owner-freebsd-current Thu May 18 07:38:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA09643 for current-outgoing; Thu, 18 May 1995 07:38:56 -0700 Received: from bigdipper.iagi.net (bigdipper.iagi.net [198.6.14.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA09637 ; Thu, 18 May 1995 07:38:48 -0700 Received: from littledipper.iagi.net (littledipper.iagi.net [198.6.14.11]) by bigdipper.iagi.net (8.6.8/8.6.6) with ESMTP id KAA22060; Thu, 18 May 1995 10:34:45 -0400 Received: (from adhir@localhost) by littledipper.iagi.net (8.6.11/8.6.9) id KAA02482; Thu, 18 May 1995 10:34:45 -0400 Date: Thu, 18 May 1995 10:34:44 -0400 (EDT) From: "Alok K. Dhir" To: hackers@FreeBSD.org, current@FreeBSD.org Subject: Help! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk I've got a news server (INN1.4sec - latest port on freebsd.cdrom.com) running -current (as of yesterday). For the last 2.5 weeks or so, I've been SUPing just about every other day... Why? Because I am waiting for a kernel that doesn't crash every day. Before this, I was running -current as of mid April (roughly), and did not have this crashing problem. I can't seem to pinpoint exactly what went wrong. I'd appreciate if anyone has any idea what may have happened thats causing this. System: 486dx2/66, 32mb RAM, 512k cache, ASUS SP3G motherboard, using onboard NCR PCI SCSI connected to 2 drives totalling 5 gigs. Video is ATI Mach32 PCI w 2mb vram. Crash description: Freezes. No panic messages, just freezes up solid. Following are the last few lines from our lastlog. As you can see, it has been crashing with some regularity over the last couple of days. For some reason, every time there is a crash, "date" seems to be logged in on "}" or on "|"?? Can anyone offer any suggestions? Thanks! adhir ttyp1 138.220.104.9 Thu May 18 10:18 still logged in reboot ~ Thu May 18 08:56 date } Thu May 18 08:56 - crash (00:00) date | Thu May 18 08:40 adhir ttyp1 machine Wed May 17 22:21 - 22:23 (00:01) adhir ftp machine.iagi.net Wed May 17 19:38 - 19:38 (00:00) anand ftp holmes.iagi.net Wed May 17 19:37 - 19:37 (00:00) adhir ttyp1 machine Wed May 17 19:08 - 19:41 (00:33) reboot ~ Wed May 17 19:08 date } Wed May 17 19:08 - crash (00:00) date | Wed May 17 19:07 adhir ttyp1 machine Wed May 17 18:43 - crash (00:24) adhir ttyp1 138.220.104.9 Wed May 17 17:17 - 18:02 (00:44) anand ftp holmes.iagi.net Wed May 17 17:03 - 17:03 (00:00) anand ftp holmes.iagi.net Wed May 17 16:44 - 16:44 (00:00) reboot ~ Wed May 17 15:13 shutdown ~ Wed May 17 15:13 adhir ttyp1 138.220.104.9 Wed May 17 14:53 - shutdown (00:19) reboot ~ Alok K. Dhir Internet Access Group, Inc. adhir@iagi.net (301) 652-0484 Fax: (301) 652-0649 http://www.iagi.net From owner-freebsd-current Thu May 18 07:46:38 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA09825 for current-outgoing; Thu, 18 May 1995 07:46:38 -0700 Received: from bigdipper.iagi.net (bigdipper.iagi.net [198.6.14.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA09819 ; Thu, 18 May 1995 07:46:35 -0700 Received: from littledipper.iagi.net (littledipper.iagi.net [198.6.14.11]) by bigdipper.iagi.net (8.6.8/8.6.6) with ESMTP id KAA22120; Thu, 18 May 1995 10:42:33 -0400 Received: (from adhir@localhost) by littledipper.iagi.net (8.6.11/8.6.9) id KAA02696; Thu, 18 May 1995 10:42:32 -0400 Date: Thu, 18 May 1995 10:42:32 -0400 (EDT) From: "Alok K. Dhir" To: hackers@FreeBSD.org, current@FreeBSD.org Subject: Follow up to my last message Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk Hi sorry to do this in two messages, I forgot to add it to the last one. Re: Hanging -current since mid April. Running news full time. Here's a copy of my kernel config in case someone can glean some info from this. BTW another data point, we added the soundcard to this machine around the same time. I have not tried pulling it yet... # LITTLEDIPPER # # GENERIC,v 1.20 1994/11/18 19:10:25 jkh Exp # machine "i386" cpu "I486_CPU" ident LITTLEDIPPER maxusers 20 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options QUOTA options "COMPAT_43" #Compatible with BSD 4.3 options UCONSOLE #X Console support options "FAT_CURSOR" #block cursor in syscons or pccons options KTRACE options USERCONFIG options "COMPAT_IBCS2" # # Options for `sc': # # HARDFONTS allows the driver to load an ISO-8859-1 font to replace # the default font in your display adapter's memory. # #options HARDFONTS # # MAXCONS is maximum number of virtual consoles, no more than 16 # default value: 12 # #options "MAXCONS=4" options "AUTO_EOI_1" options SYSVSHM options SYSVSEM options SYSVMSG config kernel root on sd0 swap on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 controller ncr0 controller scbus0 device sd0 device sd1 device st0 device cd0 #Only need one of these, the code dynamically grows device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port "IO_LPT1" tty irq 7 vector lptintr device joy0 at isa? port "IO_GAME" device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device opl0 at isa? port 0x388 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 2 pseudo-device pty 32 pseudo-device speaker pseudo-device snp 3 #pseudo-device bpfilter 4 Alok K. Dhir Internet Access Group, Inc. adhir@iagi.net (301) 652-0484 Fax: (301) 652-0649 http://www.iagi.net From owner-freebsd-current Thu May 18 08:50:02 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA11095 for current-outgoing; Thu, 18 May 1995 08:50:02 -0700 Received: from plains.nodak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA11067 ; Thu, 18 May 1995 08:49:34 -0700 Received: (from tinguely@localhost) by plains.nodak.edu (8.6.11/8.6.10) id KAA06162; Thu, 18 May 1995 10:49:06 -0500 Date: Thu, 18 May 1995 10:49:06 -0500 From: Mark Tinguely Message-Id: <199505181549.KAA06162@plains.nodak.edu> To: adhir@iagi.net, current@FreeBSD.org, hackers@FreeBSD.org Subject: Re: Help! Content-Length: 1188 Sender: current-owner@FreeBSD.org Precedence: bulk > System: 486dx2/66, 32mb RAM, 512k cache, ASUS SP3G motherboard, using > onboard NCR PCI SCSI connected to 2 drives totalling 5 gigs. Video is > ATI Mach32 PCI w 2mb vram. > > Crash description: Freezes. No panic messages, just freezes up solid. we just bought a DEC XL590s with NCR SCSI, 16 MB, Seagate 4 GB drive, Diamond Stealth , SMC Ultra, GUS sound card (now taken out), and I have been getting freezes running 2.0-950412-SNAP. I thought it was this machine, since it is easy to lock the keyboard (require a complete power cycle) with or without the PS/2 style mouse enabled. I had it up for over a day with internal and external caches disabled, but it was soooo slow, I would have shipped it back if I have to run it this way. Since I have been leaving it in X when I leave at night, for giggles I left the monitor on and it lasted the night. I enabled the process accounting so I can tell when it locks and it is doing anything important - nothing but atrun is being done. I also ran a simple script that keeps track of output from /usr/sbin/swapinfo to make we are not exceeding swap, but that was of no help. I think the key is in the cache settings. --mark. From owner-freebsd-current Thu May 18 09:29:49 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA11997 for current-outgoing; Thu, 18 May 1995 09:29:49 -0700 Received: from ns1.win.net (NS1.WIN.NET [204.215.209.3]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA11973 ; Thu, 18 May 1995 09:29:33 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id MAA19578; Thu, 18 May 1995 12:31:26 -0400 From: Mark Hittinger Message-Id: <199505181631.MAA19578@ns1.win.net> Subject: re: Help! (in, freezups) To: current@FreeBSD.org, hackers@FreeBSD.org Date: Thu, 18 May 1995 12:31:25 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 2100 Sender: current-owner@FreeBSD.org Precedence: bulk > From: "Alok K. Dhir" > I've got a news server (INN1.4sec - latest port on freebsd.cdrom.com) > running -current (as of yesterday). For the last 2.5 weeks or so, I've > been SUPing just about every other day... Why? Because I am waiting for > a kernel that doesn't crash every day. Before this, I was running > -current as of mid April (roughly), and did not have this crashing > problem. I can't seem to pinpoint exactly what went wrong. I'm not seeing terrible problems but I'm not using MMAP yet :-) Make sure you have this patch installed in your INN: I forget where it came from - may have been direct from rsalz) and patched it on to INN 1.4 here. The relevant area, as kluged, now reads (around line 82 in site.c): if (AmRoot) xchown(name); if (cp) { if (cp->fd >= 0) syslog(L_ERROR, "DEBUG ERROR SITEspool trashed:%d %s:%d", cp->fd, sp->Name, i); WCHANremove(cp); RCHANremove(cp); SCHANremove(cp); close(cp->fd); cp->fd = i; return TRUE; } sp->Channel = CHANcreate(i, CTfile, CSwriting, SITEreader, SITEwritedone); if (sp->Channel == NULL) { ----------------------- That fixes a file descriptor leak in INN. I think you should probably re-compile with MMAP off if it is on, and put this patch in. Then re-install the re-linked images. Just out of paranoia I'd run fsck on your news partition, rebuild your history files, and do an expireover -s if you are using the NOV database. Depending on your load you might also want to consider these options in your kernel config file: MAXUSERS 256 options "CHILD_MAX=128" options "OPEN_MAX=128" options "NMBCLUSTERS=512" But you should pick your own numbers for these. My average uptime is out to 4 days now on my heaviest hit box, the other boxes that have lighter load have very good uptimes. I have also noticed very nice performance improvements over the earlier kernels. The failures that I am seeing are scsi buffer already done freezups. About once a week on my 4 gig news harddrive. Regards, Mark Hittinger bugs@win.net From owner-freebsd-current Thu May 18 09:47:23 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA12519 for current-outgoing; Thu, 18 May 1995 09:47:23 -0700 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA12513 for ; Thu, 18 May 1995 09:47:21 -0700 Received: from ref.tfs.com by inet-gw-1.pa.dec.com (5.65/24Feb95) id AA02316; Thu, 18 May 95 09:42:35 -0700 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id JAA00418; Thu, 18 May 1995 09:42:26 -0700 From: Poul-Henning Kamp Message-Id: <199505181642.JAA00418@ref.tfs.com> Subject: Re: bios boot bug ? To: gj@FreeBSD.org Date: Thu, 18 May 1995 09:42:25 -0700 (PDT) Cc: current%freebsd.org@inet-gw-1.pa.dec.com In-Reply-To: from "gj%pcs.dec.com@inet-gw-1.pa.dec.com" at May 18, 95 12:54:06 pm Content-Type: text Content-Length: 392 Sender: current-owner@FreeBSD.org Precedence: bulk > The problem is that the values in the disklabel are byte values, not sector > values. Or has this changed without me noticing ? Uhm, I have never heard it was... > Am I totally fubar here ? I'm afraid so ... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant' From owner-freebsd-current Thu May 18 11:24:19 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA14983 for current-outgoing; Thu, 18 May 1995 11:24:19 -0700 Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.35.13]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA14955 ; Thu, 18 May 1995 11:24:07 -0700 Received: (from james@localhost) by miller.cs.uwm.edu (8.6.10/8.6.10) id NAA23047; Thu, 18 May 1995 13:24:05 -0500 Date: Thu, 18 May 1995 13:24:05 -0500 From: Jim Lowe Message-Id: <199505181824.NAA23047@miller.cs.uwm.edu> To: adhir@iagi.net, current@FreeBSD.org, hackers@FreeBSD.org, tinguely@plains.NoDak.edu Subject: Re: Help! Sender: current-owner@FreeBSD.org Precedence: bulk > > System: 486dx2/66, 32mb RAM, 512k cache, ASUS SP3G motherboard, using > > onboard NCR PCI SCSI connected to 2 drives totalling 5 gigs. Video is > > ATI Mach32 PCI w 2mb vram. > > > > Crash description: Freezes. No panic messages, just freezes up solid. > > we just bought a DEC XL590s with NCR SCSI, 16 MB, Seagate 4 GB drive, > [...] > I think the key is in the cache settings. > I have had the same problem with a triton mother board P100, S3-964 video, and an NCR disk controller. I swapped out disk controllers with a Adaptec ISA controller and it still hangs. I havn't been able to get through a make world in the src tree since I switched from a 486dx50 - opti chip set to the 100 mhz pentium with the triton chip set. It almost seems pci bus related but I have no idea. I have now disabled the external cache and I am trying the make world again... It is a lot slower... Is there a method of forcing a crash dump in FreeBSD? Once I get a hang I would like to reset and dump the memory to see what it is up to. Is there any way of doing this? -Jim From owner-freebsd-current Thu May 18 12:32:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA16404 for current-outgoing; Thu, 18 May 1995 12:32:56 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA16372 ; Thu, 18 May 1995 12:31:21 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id MAA14977; Thu, 18 May 1995 12:30:06 -0700 From: "Rodney W. Grimes" Message-Id: <199505181930.MAA14977@gndrsh.aac.dev.com> Subject: Re: Help! To: james@miller.cs.uwm.edu (Jim Lowe) Date: Thu, 18 May 1995 12:30:06 -0700 (PDT) Cc: adhir@iagi.net, current@FreeBSD.org, hackers@FreeBSD.org, tinguely@plains.NoDak.edu In-Reply-To: <199505181824.NAA23047@miller.cs.uwm.edu> from "Jim Lowe" at May 18, 95 01:24:05 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1720 Sender: current-owner@FreeBSD.org Precedence: bulk > > > > System: 486dx2/66, 32mb RAM, 512k cache, ASUS SP3G motherboard, using > > > onboard NCR PCI SCSI connected to 2 drives totalling 5 gigs. Video is > > > ATI Mach32 PCI w 2mb vram. > > > > > > Crash description: Freezes. No panic messages, just freezes up solid. > > > > we just bought a DEC XL590s with NCR SCSI, 16 MB, Seagate 4 GB drive, > > [...] > > I think the key is in the cache settings. > > > > I have had the same problem with a triton mother board P100, S3-964 video, > and an NCR disk controller. I swapped out disk controllers with a Adaptec > ISA controller and it still hangs. I havn't been able to get through a > make world in the src tree since I switched from a 486dx50 - opti chip set > to the 100 mhz pentium with the triton chip set. It almost seems pci bus > related but I have no idea. I have now disabled the external cache and I > am trying the make world again... It is a lot slower... If this is not the ASUS board, ignore me!! I have qualified and done extensive testing on the ASUS Triton board, it does work. To this day I have probably completed over 100 make worlds on these boards. I see you are running a 100Mhz CPU chip, are you also running 60nS DRAM as required by the motherboard book. Have you left the BIOS settings on the default values, or have you tried to speed things up by tweaking them?? > Is there a method of forcing a crash dump in FreeBSD? Once I get a hang > I would like to reset and dump the memory to see what it is up to. Is there > any way of doing this? > > -Jim > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Thu May 18 13:00:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA16922 for current-outgoing; Thu, 18 May 1995 13:00:26 -0700 Received: from miller.cs.uwm.edu (miller.cs.uwm.edu [129.89.35.13]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id MAA16840 ; Thu, 18 May 1995 12:58:07 -0700 Received: (from james@localhost) by miller.cs.uwm.edu (8.6.10/8.6.10) id OAA24762; Thu, 18 May 1995 14:58:04 -0500 Date: Thu, 18 May 1995 14:58:04 -0500 From: Jim Lowe Message-Id: <199505181958.OAA24762@miller.cs.uwm.edu> To: rgrimes@gndrsh.aac.dev.com Subject: Re: Help! Cc: adhir@iagi.net, current@FreeBSD.org, hackers@FreeBSD.org, tinguely@plains.NoDak.edu Sender: current-owner@FreeBSD.org Precedence: bulk > > related but I have no idea. I have now disabled the external cache and I > > am trying the make world again... It is a lot slower... > > If this is not the ASUS board, ignore me!! > > I have qualified and done extensive testing on the ASUS Triton board, it > does work. To this day I have probably completed over 100 make worlds > on these boards. I see you are running a 100Mhz CPU chip, are you also > running 60nS DRAM as required by the motherboard book. Have you left > the BIOS settings on the default values, or have you tried to speed > things up by tweaking them?? I am running 32 Meg of 70ns EDO DRAM (this was all that was available a month ago) with 12ns async cache with a SuperMicro mother board and AMI bios. I havn't tweaked much of anything. I think the problem might be the external cache speed in my case. My system has been running for almost 2.5 hrs now with the external cache disabled and make world is just about finished. I talked with some people down in the Electronics shop and they suggested that the cache speed must be 10ns with a 100 Mhz processor and 8ns with a 120Mhz processor (1/Processor Mhz). Do you know if this is correct? Also, do you know if there is anyway of causing a core dump if the system hangs? Thanks. -Jim From owner-freebsd-current Thu May 18 13:29:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA17510 for current-outgoing; Thu, 18 May 1995 13:29:41 -0700 Received: from halloran-eldar.lcs.mit.edu (halloran-eldar.lcs.mit.edu [18.26.0.159]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA17504 for ; Thu, 18 May 1995 13:29:39 -0700 Received: by halloran-eldar.lcs.mit.edu; (5.65/1.1.3.6) id AA23953; Thu, 18 May 1995 16:29:37 -0400 Date: Thu, 18 May 1995 16:29:37 -0400 From: Garrett Wollman Message-Id: <9505182029.AA23953@halloran-eldar.lcs.mit.edu> To: Jim Lowe Cc: current@FreeBSD.org Subject: Re: Help! In-Reply-To: <199505181958.OAA24762@miller.cs.uwm.edu> References: <199505181958.OAA24762@miller.cs.uwm.edu> Sender: current-owner@FreeBSD.org Precedence: bulk < said: > Also, do you know if there is anyway of causing a core dump if the system > hangs? By definition, if the system is truly hung, then there's way to give control to the part of the kernel that takes crash dumps. If this system is only pseudo-hung, you can escape to the debugger and tell it to `call boot(0x104)' and it will attempt to take a crash dump. Often times, the problems that cause a hang are the same ones that may cause a crash dump to fail. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant From owner-freebsd-current Thu May 18 16:28:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA25811 for current-outgoing; Thu, 18 May 1995 16:28:57 -0700 Received: from deep-thought.demos.su (root@deep-thought.demos.su [192.91.186.133]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA25804 for ; Thu, 18 May 1995 16:28:49 -0700 Received: by deep-thought.demos.su id DAA02913; (8.6.11/D) Fri, 19 May 1995 03:28:09 +0400 To: current@FreeBSD.org Cc: S0ren Schmidt Message-ID: Organization: DEMOS Date: Fri, 19 May 1995 03:28:08 +0400 X-Mailer: Mail/@ [v2.34 FreeBSD] From: "Andrey A. Chernov, Black Mage" X-Class: Fast Subject: Syscons critical bugfix for review Lines: 53 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Length: 1594 Sender: current-owner@FreeBSD.org Precedence: bulk Problem: Char cursor is wrong (appearse as small circle) after screen switching from X. Fix: *** syscons.c.old Fri Apr 28 18:27:28 1995 --- syscons.c Fri May 19 03:20:14 1995 *************** *** 843,848 **** --- 843,850 ---- copy_font(LOAD, FONT_14, font_14); if (fonts_loaded & FONT_16) copy_font(LOAD, FONT_16, font_16); + if (configuration & CHAR_CURSOR) + set_destructive_cursor(scp, TRUE); load_palette(); } /* FALL THROUGH */ *************** *** 1312,1317 **** --- 1314,1321 ---- copy_font(LOAD, FONT_14, font_14); if (fonts_loaded & FONT_16) copy_font(LOAD, FONT_16, font_16); + if (configuration & CHAR_CURSOR) + set_destructive_cursor(new_scp, TRUE); load_palette(); } if (old_scp->status & KBD_RAW_MODE || new_scp->status & KBD_RAW_MODE) *************** *** 2892,2898 **** if (!force && (scp->cursor_saveunder & 0xFF) == old_saveunder) return; ! old_saveunder = scp->cursor_saveunder & 0xFF; switch (scp->font) { default: case FONT_8: --- 2896,2902 ---- if (!force && (scp->cursor_saveunder & 0xFF) == old_saveunder) return; ! old_saveunder = force ? DEAD_CHAR : scp->cursor_saveunder & 0xFF; switch (scp->font) { default: case FONT_8: -- Andrey A. Chernov : And I rest so composedly, /Now, in my bed, ache@astral.msk.su : That any beholder /Might fancy me dead - FidoNet: 2:5020/230.3 : Might start at beholding me, /Thinking me dead. RELCOM Team,FreeBSD Team : E.A.Poe From "For Annie" 1849 From owner-freebsd-current Fri May 19 01:03:04 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA15519 for current-outgoing; Fri, 19 May 1995 01:03:04 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA15502 for ; Fri, 19 May 1995 01:02:48 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id RAA23102; Fri, 19 May 1995 17:56:50 +1000 Date: Fri, 19 May 1995 17:56:50 +1000 From: Bruce Evans Message-Id: <199505190756.RAA23102@godzilla.zeta.org.au> To: bde@zeta.org.au, esser@ZPR.Uni-Koeln.DE Subject: Re: Enthusiasm boost: make world works on 386SX16 4Mb Cc: current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk >I've got one new idea regarding tallying PCI interrupts. >Not a solution, but an easy workaround for now: >How about reserving the "0" entry in intrcnt[] and the >intrnames list for PCI ? Ugh. Entries 0 and 1 are already reserved for clk and rtc. That's already 2 too many reservations. Anyway, if you reserve entry 2, then you would only have to change pcibus.c and worry about people using old config binaries so that entry 2 is something else. >} OK. Put all the controller names in the string table so >} that you don't have to decide which. >To support PCI devices, I've got to put some number of each >into the string table. E.g. the "de" driver can be used with >4channel Ethernet cards, which will all use the same IRQ, but >are independent devices and should get private intrcnt values, >IMHO. >So it might be useful to have some 8 entries for each PCI >driver, as long as a fixed string table is used. >But this won't do for loadable device drivers and really >is no good match for PCI neither. The PCI interrupt multiplexor will have to do its own interrupt multiplexing. How about generating device ids and maintaining the string table dynamically using this interface: int register_dev(char const *name, int intr); int unregister_dev(char const *name, int intr); Device ids may live longer than the drivers that generate them and only go away if they have been unregistered and the intrcnt[] or intrnames[] table fills up. The tables should be large enough so that this doesn't normally happen. The same driver may use multiple interrupts (normally at different times, e.g., unloading and reloading may change the interrupt). If the table fills up and there are no unregistered slots to reuse, then a bit bucket id will be returned. The bit bucket id may also be used for multiplexed interrupts so that they don't get counted twice. I think a string table for the names is good enough. intrcnt[] and intrnames[] have to be statically allocated so that systat etc. can find them, but when systat etc. are changed to support the tables changing due to loading and unloading lkm's, they can be changed to support the table addresses changing due to realloc'ing the tables. Bruce From owner-freebsd-current Fri May 19 01:20:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA15896 for current-outgoing; Fri, 19 May 1995 01:20:26 -0700 Received: from ibmmail.COM (ibmmail.com [199.171.26.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id BAA15890 for ; Fri, 19 May 1995 01:20:20 -0700 From: n1epo4tl@ibmmail.com Message-Id: <199505190820.BAA15890@freefall.cdrom.com> Received: from IBMMAIL.COM by ibmmail.COM (IBM VM SMTP V2R3) with BSMTP id 2195; Fri, 19 May 95 04:20:17 EDT Date: Fri, 19 May 1995 04:20:16 EDT To: current@FreeBSD.org, internet@ibmmail.com X-Sender-Info: Stuart J. Arnold ext. 2476 European Patent Office -- Munich N1EPO4TL@IBMMAIL.COM MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: current crashes Sender: current-owner@FreeBSD.org Precedence: bulk Alok.K.Dhir writes: >Crash description: Freezes. No panic messages, just freezes up solid I see the same thing with a current kernel a couple of weeks old. Completely different system - 386DX40, 8MB RAM 500MB IDE disk. No idea what causes it. At the moment i've gone back to the 2.0 kernel, (which means I can't use ppp):-( It's probably completely irrelevant, but for what it's worth i'll mention it. I discovered that the date command under NetBSD freezes the system. It only happens in multi-user mode, and the system sleeps for an amount of time dependent on how much the date is changed - a couple of minutes per year of change. I don't have access to the FreeBSD system at the moment to see if it does the same. Stuart Arnold From owner-freebsd-current Fri May 19 08:46:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA25124 for current-outgoing; Fri, 19 May 1995 08:46:26 -0700 Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA25117 for ; Fri, 19 May 1995 08:46:25 -0700 Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.6.10/8.6.9) with SMTP id KAA13558 for ; Fri, 19 May 1995 10:46:23 -0500 Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 19 May 95 10:37 CDT Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Fri, 19 May 95 10:37 CDT Message-Id: Subject: What is wrong with gdb? To: current@FreeBSD.org Date: Fri, 19 May 1995 10:37:24 -0500 (CDT) From: "Lars Fredriksen" X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 632 Sender: current-owner@FreeBSD.org Precedence: bulk Hi, There seems to be a problem with gdb and breakpoints. If I set a breakpoint in a program, I have to hit (continue) once, which magically stops on the same breakpoint again, before I can step the code. Otherwise the PC gets a stack address, and gdb complains that it cannot set breakpoint 0 at addres 0xe. I'll see if I can come up with an explanation from looking at the code, but I figured the rest of you might want to know too. Lars -- ------------------------------------------------------------------- Lars Fredriksen fredriks@mcs.com (home) lars@fredriks.pr.mcs.net (home-home) fredriks@asiago.cs.wisc.edu From owner-freebsd-current Sat May 20 01:36:08 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id BAA18989 for current-outgoing; Sat, 20 May 1995 01:36:08 -0700 Received: from lirmm.lirmm.fr (lirmm.lirmm.fr [193.49.104.10]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id BAA18982 for ; Sat, 20 May 1995 01:36:04 -0700 Received: from lirmm.fr (baobab.lirmm.fr [193.49.106.14]) by lirmm.lirmm.fr (8.6.10/8.6.4) with ESMTP id KAA00485 for ; Sat, 20 May 1995 10:36:02 +0200 Message-Id: <199505200836.KAA00485@lirmm.lirmm.fr> To: current@FreeBSD.org Subject: typo: sysctl.3 Date: Sat, 20 May 1995 10:35:59 +0200 From: "Philippe Charnier" Sender: current-owner@FreeBSD.org Precedence: bulk Hello, the first change is needed for examples (later in the man page) to compile without problem. Index: sysctl.3 =================================================================== RCS file: /home2h/FreeBSD.cvsroot/src/lib/libc/gen/sysctl.3,v retrieving revision 1.3 diff -u -r1.3 sysctl.3 --- 1.3 1994/10/18 03:42:18 +++ sysctl.3 1995/05/20 00:56:46 @@ -38,6 +38,7 @@ .Nm sysctl .Nd get or set system information .Sh SYNOPSIS +.Fd #include .Fd #include .Ft int .Fn sysctl "int *name" "u_int namelen" "void *oldp" "size_t *oldlenp" "void *newp" "size_t newlen" @@ -51,7 +52,7 @@ consists of integers, strings, and tables. Information may be retrieved and set from the command interface using the -.Xr sysctl 1 +.Xr sysctl 8 utility. .Pp Unless explicitly noted below, -------- -------- Philippe Charnier charnier@lirmm.fr LIRMM, 161 rue Ada, 34392 Montpellier cedex 5 -- France ------------------------------------------------------------------------ From owner-freebsd-current Sat May 20 09:09:26 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA01842 for current-outgoing; Sat, 20 May 1995 09:09:26 -0700 Received: from vmbb.cts.com (vmbb.cts.com [192.188.72.18]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id JAA01836 for ; Sat, 20 May 1995 09:09:25 -0700 Received: from io.cts.com by vmbb.cts.com with smtp (Smail3.1.28.1 #9) id m0sCr5f-0000h9C; Sat, 20 May 95 09:09 PDT Received: (from root@localhost) by io.cts.com (8.6.11/8.6.9) id JAA00142 for current@freebsd.org; Sat, 20 May 1995 09:09:18 -0700 From: Morgan Davis Message-Id: <199505201609.JAA00142@io.cts.com> Subject: 5/19 current sticks on startup To: current@FreeBSD.org Date: Sat, 20 May 1995 09:09:18 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 376 Sender: current-owner@FreeBSD.org Precedence: bulk The 5/19 current, upon rebooting, will start routed, then hang until Control-C is pressed. It looks like this: starting routing daemons: routed. _ ...And the cursor sits there. When I Control-C, I see this: ^Cclearing /tmp ...and it continues to start up correctly. I copied over the latest sysconfig (and edited it), rc, and netstart from /usr/src/etc. Any ideas? From owner-freebsd-current Sat May 20 10:00:06 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA02894 for current-outgoing; Sat, 20 May 1995 10:00:06 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA02888 for ; Sat, 20 May 1995 10:00:03 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA02070; Sat, 20 May 1995 09:59:42 -0700 From: "Rodney W. Grimes" Message-Id: <199505201659.JAA02070@gndrsh.aac.dev.com> Subject: Re: 5/19 current sticks on startup To: root@io.cts.com (Morgan Davis) Date: Sat, 20 May 1995 09:59:42 -0700 (PDT) Cc: current@FreeBSD.org In-Reply-To: <199505201609.JAA00142@io.cts.com> from "Morgan Davis" at May 20, 95 09:09:18 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 887 Sender: current-owner@FreeBSD.org Precedence: bulk > > The 5/19 current, upon rebooting, will start routed, then hang until > Control-C is pressed. It looks like this: > > starting routing daemons: routed. > _ > > ...And the cursor sits there. When I Control-C, I see this: > > ^Cclearing /tmp > > ...and it continues to start up correctly. I copied over the latest > sysconfig (and edited it), rc, and netstart from /usr/src/etc. Any > ideas? Yea, you have nfs mounts in /etc/fstab probably, and some of them are not ready at boot time. I changed the call to mount nfs disks so that it is no longer backgrounded (ie, wait for my /usr to come ready please :-)). If you have mounts that are not critical to booting you should use option bg on them in your /etc/fstab. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD From owner-freebsd-current Sat May 20 12:37:31 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA06861 for current-outgoing; Sat, 20 May 1995 12:37:31 -0700 Received: from wpdis01.wpafb.af.mil (wpdis01.wpafb.af.mil [192.12.64.3]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA06855 for ; Sat, 20 May 1995 12:37:29 -0700 Received: by wpdis01.wpafb.af.mil id AA26582; Sat, 20 May 95 15:37:20 -0400 Message-Id: <9505201937.AA26582@wpdis01.wpafb.af.mil> Date: Sat, 20 May 95 15:37:20 -0400 From: deanj@wpdis01.wpafb.af.mil (SrA Jeffrey Dean SRA) Subject: help To: freebsd-current@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk I have been trying to compile (or get) libc.so.2.1 for the last couple of weeks. I am running FreeBSD 2.0R and have attempted to upgrade with FreeBSD-current --hoping that this upgrade will contain libc.so.2.1??? (does it?) If yes, can anyone send me a quick overview on how to install the current libs via FTP. (if libc.so.2.1 is not part of the FreeBSD-current) Can anyone point me into the right direction to obtain it? I am pretty good with UN*X, but not an expert. I may just be having a problem ftping an entire dirctory tree from "wcarchive.cdrom.com/FreeBSD/FreeBSD-current/ports"????? That is IF that's what I am supposed to do? I would greatly appreciate ANY help!!! Jeffrey D. Dean deanj@wpdis01.wpafb.af.mil From owner-freebsd-current Sat May 20 12:53:10 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id MAA07106 for current-outgoing; Sat, 20 May 1995 12:53:10 -0700 Received: from localhost (localhost [127.0.0.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id MAA07099 ; Sat, 20 May 1995 12:53:09 -0700 X-Authentication-Warning: freefall.cdrom.com: Host localhost didn't use HELO protocol To: deanj@wpdis01.wpafb.af.mil (SrA Jeffrey Dean SRA) cc: freebsd-current@FreeBSD.org Subject: Re: help In-reply-to: Your message of "Sat, 20 May 95 15:37:20 EDT." <9505201937.AA26582@wpdis01.wpafb.af.mil> Date: Sat, 20 May 1995 12:53:09 -0700 Message-ID: <7098.800999589@freefall.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@FreeBSD.org Precedence: bulk > and have attempted to upgrade with FreeBSD-current --hoping > that this upgrade will contain libc.so.2.1??? > > (does it?) It does. > I am pretty good with UN*X, but not an expert. I may > just be having a problem ftping an entire dirctory tree from > "wcarchive.cdrom.com/FreeBSD/FreeBSD-current/ports"????? > That is IF that's what I am supposed to do? % cd /usr % ftp ftp.freebsd.org ftp> binary ftp> cd pub/FreeBSD/FreeBSD-current ftp> get src.tar.gz "|tar xvf -" ftp> get ports.tar.gz "|tar xvf -" ftp> quit % cd src % make world >& make.out & % tail -f make.out Jordan From owner-freebsd-current Sat May 20 16:43:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA12377 for current-outgoing; Sat, 20 May 1995 16:43:29 -0700 Received: from grep.cs.fsu.edu (grep.cs.fsu.edu [128.186.121.152]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA12371 for ; Sat, 20 May 1995 16:43:28 -0700 Received: by grep.cs.fsu.edu (8.6.9/56) id TAA18378; Sat, 20 May 1995 19:43:27 -0400 From: Gang-Ryung Uh Message-Id: <199505202343.TAA18378@grep.cs.fsu.edu> Subject: /usr/src/etc To: current@FreeBSD.org Date: Sat, 20 May 1995 19:43:26 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 245 Sender: current-owner@FreeBSD.org Precedence: bulk Hi, I have upgraded my system to FreeBSD-current. But I belive there are some differences between "/etc" and "/usr/src/etc". What is the best way to incoporate the changes in /usr/src/etc to /etc ? Thanks. Regards, --Uh uh@cs.fsu.edu From owner-freebsd-current Sat May 20 19:42:41 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA20622 for current-outgoing; Sat, 20 May 1995 19:42:41 -0700 Received: from relay1.UU.NET (relay1.UU.NET [192.48.96.5]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA20611 for ; Sat, 20 May 1995 19:42:38 -0700 Received: from ast.com by relay1.UU.NET with SMTP id QQyqpu06804; Sat, 20 May 1995 22:42:35 -0400 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA14562 (5.67b/IDA-1.5 for uunet!freebsd.org!current); Sat, 20 May 1995 19:42:48 -0700 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Sat, 20 May 95 21:42 CDT Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0sD0oX-0004vzC; Sat, 20 May 95 21:32 CDT Message-Id: Date: Sat, 20 May 95 21:32 CDT To: current@FreeBSD.org From: uhclem@nemesis.lonestar.org (Frank Durda IV) Sent: Sat May 20 1995, 21:32:21 CDT Subject: 5/19 current sticks on startup Cc: uhclem@nemesis.lonestar.org Sender: current-owner@FreeBSD.org Precedence: bulk [0]The 5/19 current, upon rebooting, will start routed, then hang until [0]Control-C is pressed. It looks like this: [0] [0] starting routing daemons: routed. [0] _ [0] [0]...And the cursor sits there. When I Control-C, I see this: [0] [0] ^Cclearing /tmp I have also seen this when you boot a kernel not named "kernel". I was using "kernel.exp" on a system to do test work with no NFS active at all and it would routinely hang if the kernel name wasn't "kernel". Hit ^C and it kept going. This started happening (for me anyway) around the 032x SNAP. You might consider that possible cause if you aren't running NFS and can't be having the NFS-related problems. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983 From owner-freebsd-current Sat May 20 23:06:29 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA25155 for current-outgoing; Sat, 20 May 1995 23:06:29 -0700 Received: from leo.ibms.sinica.edu.tw ([140.109.40.249]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA25149 for ; Sat, 20 May 1995 23:06:27 -0700 Received: (from taob@localhost) by leo.ibms.sinica.edu.tw (8.6.11/8.6.9) id OAA17063; Sun, 21 May 1995 14:06:23 +0800 Date: Sun, 21 May 1995 14:06:22 +0800 (CST) From: Brian Tao To: FREEBSD-CURRENT-L cc: Bill Fenner Subject: rwhod bugfix In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: current-owner@FreeBSD.org Precedence: bulk On Thu, 18 May 1995, Bill Fenner wrote: > > In fact, it prints an error to stderr... which daemon() just closed... =) Right. ;-) I've included two small patches below to fix this. The first one patches rwhod.c to print the error to stderr and exit (it just moves daemon() a little further down). The second fixes it to log the error via syslog() instead. I don't know which is better. I would prefer the syslog method, since rwhod is started in /etc/rc and stderr messages may be lost on the console. *** rwhod-orig.c Sun May 21 13:52:00 1995 --- rwhod-stderr.c Sun May 21 13:54:51 1995 *************** *** 127,140 **** fprintf(stderr, "rwhod: udp/who: unknown service\n"); exit(1); } - #ifndef DEBUG - daemon(1, 0); - #endif if (chdir(_PATH_RWHODIR) < 0) { (void)fprintf(stderr, "rwhod: %s: %s\n", _PATH_RWHODIR, strerror(errno)); exit(1); } (void) signal(SIGHUP, getboottime); openlog("rwhod", LOG_PID, LOG_DAEMON); /* --- 127,140 ---- fprintf(stderr, "rwhod: udp/who: unknown service\n"); exit(1); } if (chdir(_PATH_RWHODIR) < 0) { (void)fprintf(stderr, "rwhod: %s: %s\n", _PATH_RWHODIR, strerror(errno)); exit(1); } + #ifndef DEBUG + daemon(1, 0); + #endif (void) signal(SIGHUP, getboottime); openlog("rwhod", LOG_PID, LOG_DAEMON); /* *** rwhod-orig.c Sun May 21 13:52:00 1995 --- rwhod-syslog.c Sun May 21 13:55:49 1995 *************** *** 130,142 **** #ifndef DEBUG daemon(1, 0); #endif if (chdir(_PATH_RWHODIR) < 0) { ! (void)fprintf(stderr, "rwhod: %s: %s\n", _PATH_RWHODIR, strerror(errno)); exit(1); } - (void) signal(SIGHUP, getboottime); - openlog("rwhod", LOG_PID, LOG_DAEMON); /* * Establish host name as returned by system. */ --- 130,142 ---- #ifndef DEBUG daemon(1, 0); #endif + (void) signal(SIGHUP, getboottime); + openlog("rwhod", LOG_PID, LOG_DAEMON); if (chdir(_PATH_RWHODIR) < 0) { ! syslog(LOG_ERR, "%s: %s\n", _PATH_RWHODIR, strerror(errno)); exit(1); } /* * Establish host name as returned by system. */ -- Brian ("Though this be madness, yet there is method in't") Tao taob@gate.sinica.edu.tw <-- work ........ play --> taob@io.org