From owner-freebsd-stable Sun May 4 07:25:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24255 for stable-outgoing; Sun, 4 May 1997 07:25:09 -0700 (PDT) Received: from perseverance.sands.com (dal99.metronet.com [192.245.137.99]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA24243 for ; Sun, 4 May 1997 07:25:01 -0700 (PDT) Received: from localhost.sands.com (localhost.sands.com [127.0.0.1]) by perseverance.sands.com (8.7.5/8.7.3) with SMTP id JAA09338 for ; Sun, 4 May 1997 09:27:26 -0500 (CDT) Message-Id: <199705041427.JAA09338@perseverance.sands.com> X-Authentication-Warning: perseverance.sands.com: Host localhost.sands.com [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.9 8/22/96 To: stable@freebsd.org Subject: BootMgr can't find second IDE disk correctly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 May 1997 09:27:25 -0500 From: Ted Spradley Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I got my long-awaited 2.2 Release CD-ROM and installed it on my desk at work. Since I needed more space, and to avoid any (tiny) risk of leaving the machine down, I got a second IDE disk and installed onto that, leaving the running system (the 8/1/96 Snapshot) untouched. The installation went flawlessly (great work), but when it was all finished and tried to reboot it was unable to mount the root file system, and paniced. This is a generic Pentium 120MHz with two IDE controllers on the motherboard. On the primary IDE controller are an 800Mbyte disk and a CD-ROM drive. I added a second 800Mbyte disk onto the second IDE controller. The first drive is half WinNT-3.51 :-( and half FreeBSD, the second drive is all FreeBSD. At reset, the boot manager offers: F1 DOS F2 BSD F5 other disk So I pick F5, and I get another list with only one choice: F1 BSD This boots wd(1,a)/kernel. It runs along fine until time to mount /, can't find wd1a and panics. If I type in "1:wd(2,a)/kernel" it boots the same kernel and successfully mounts wd2a as /. The bootmanager calls the second drive wd1 but everything else calls it wd2. But the bootmanager also recognizes wd2 as the same as wd1. Is there any way I can get this to reboot unattended? I know, the best way is to swap the cables between the two drives. When I do that, what do I need to fix besides /etc/fstab ? Thanks! Ted Spradley tsprad@metronet.com +1-972-484-5356 Brisco: "...the more I learn the less I know." Bowler: "At the rate we're learning things we won't know nothing in no time." From owner-freebsd-stable Sun May 4 13:35:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA15793 for stable-outgoing; Sun, 4 May 1997 13:35:52 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA15786 for ; Sun, 4 May 1997 13:35:49 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id GAA25301; Mon, 5 May 1997 06:33:11 +1000 Date: Mon, 5 May 1997 06:33:11 +1000 From: Bruce Evans Message-Id: <199705042033.GAA25301@godzilla.zeta.org.au> To: stable@FreeBSD.ORG, tsprad@mail.metronet.com Subject: Re: BootMgr can't find second IDE disk correctly Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >At reset, the boot manager offers: > > F1 DOS > F2 BSD > F5 other disk > >So I pick F5, and I get another list with only one choice: > > F1 BSD > >This boots wd(1,a)/kernel. It runs along fine until time to mount /, can't >find wd1a and panics. If I type in "1:wd(2,a)/kernel" it boots the same >kernel and successfully mounts wd2a as /. > >The bootmanager calls the second drive wd1 but everything else calls it wd2. >But the bootmanager also recognizes wd2 as the same as wd1. The drive really is 1:wd(2,*) (BIOS drive 1 and FreeBSD drive wd2 = first drive on the second IDE controller; wd1 would be the second drive on the first IDE controller). It's probably a bug for the bootmanager to recognise wd2. >Is there any way I can get this to reboot unattended? I know, the best way is >to swap the cables between the two drives. When I do that, what do I need to >fix besides /etc/fstab ? The simplest way is to use -current bootblocks and put "1:wd(2,a)kernel" in /boot.config on the boot drive. Bruce From owner-freebsd-stable Sun May 4 18:42:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA27812 for stable-outgoing; Sun, 4 May 1997 18:42:13 -0700 (PDT) Received: from warrane.connect.com.au (warrane.connect.com.au [192.189.54.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA27801 for ; Sun, 4 May 1997 18:41:52 -0700 (PDT) Received: from gurney.zeta.org.au (d15.syd2.zeta.org.au [203.26.11.15]) by warrane.connect.com.au with ESMTP id LAA16006 (8.8.5/IDA-1.6); Mon, 5 May 1997 11:41:08 +1000 (EST) Received: (from andrew@localhost) by gurney.zeta.org.au (8.7.5/8.7.3) id IAA01503; Mon, 5 May 1997 08:01:41 +1000 (EST) Message-ID: <19970505080141.03345@gurney.zeta.org.au> Date: Mon, 5 May 1997 08:01:41 +1000 From: Andrew Reilly To: John Polstra , freebsd-stable@FreeBSD.ORG Subject: Re: Add LIVE Girls to your website! References: <199705012351.QAA26484@hub.freebsd.org> <5kd3g6$krf@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67e In-Reply-To: <5kd3g6$krf@austin.polstra.com>; from John Polstra on Fri, May 02, 1997 at 09:07:34AM -0700 Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sorry for continuing this thread, but I couldn't resist... On Fri, May 02, 1997 at 09:07:34AM -0700, John Polstra wrote: > In article <199705012351.QAA26484@hub.freebsd.org>, wrote: > > > We will provide a Live Stripshow with chat for your website starting > > at only $500 per month and NEVER more than $1600.00 a month!! > > RTFM, Bozo. We already have that as part of the system. Try "man 1 strip". Kind of puts a different spin on the "FM"... -- Andrew "The steady state of disks is full." -- Ken Thompson From owner-freebsd-stable Mon May 5 07:16:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA26558 for stable-outgoing; Mon, 5 May 1997 07:16:52 -0700 (PDT) Received: from inner.cortx.com (root@inner.cortx.com [207.207.221.8]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA26552 for ; Mon, 5 May 1997 07:16:47 -0700 (PDT) Received: from cman.cortx.com (cman.cortx.com [207.207.221.12]) by inner.cortx.com (8.6.12/8.6.12) with SMTP id KAA18713 for ; Mon, 5 May 1997 10:21:14 GMT Received: by cman.cortx.com with Microsoft Mail id <01BC5A06.02A8ECE0@cman.cortx.com>; Tue, 6 May 1997 10:12:32 -0400 Message-ID: <01BC5A06.02A8ECE0@cman.cortx.com> From: Costa Morris To: "stable@FreeBSD.ORG" Subject: unsubscribe Date: Tue, 6 May 1997 10:12:30 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk unsubscribe ===C=O=R=T=E=X==C=O=M=M=U=N=I=C=A=T=I=O=N=S=== Costa J Morris - Account Exec Full Service Internet Access http://www.cortx.com Interactive CGI Scripting costa@cortx.com Internet Consulting 201-567-2297 Web Design =========================================== From owner-freebsd-stable Mon May 5 18:00:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA03065 for stable-outgoing; Mon, 5 May 1997 18:00:44 -0700 (PDT) Received: from mailhost.anasazi.com (mailhost.anasazi.com [138.113.128.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA03048 for ; Mon, 5 May 1997 18:00:37 -0700 (PDT) Received: from chad.anasazi.com by mailhost.anasazi.com (5.65/3.7) id AA25969; Mon, 5 May 97 18:00:03 -0700 Received: by chad.anasazi.com (5.65/3.7) id AA18202; Mon, 5 May 97 18:00:01 -0700 From: chad@anasazi.com (Chad R. Larson) Message-Id: <9705060100.AA18202@chad.anasazi.com> Subject: 2.1.8 Release To: freebsd-stable@freebsd.org Date: Mon, 5 May 1997 18:00:00 -0700 (MST) Reply-To: chad@anasazi.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I tried to stay out of the discussion about whether a 2.1.8 release was justified, but the last week's flurry of e-mail about lockups, memory leaks and the continuing Adaptec controller adventures persuades me that I'm not yet ready to commit my production machines to a 2.2.x release. I also must admit I have found no use for the "live filesystem" CD-ROM in my subscription. I freely admit that might be different if I didn't have a nice, full time (via MCI) connection to the 'net, but there you have it. That being said, here's what I'd prefer for my CD-ROM buying dollar. Yes, please, make a 2.1.8 release. I'm assuming it would be essentally what I have now on machines using CVSup to track RELENG_2_1_0. Drop the live filesystem from the subscription set. Ship 2.1.x and 2.2.x as the two CDs in the subscription set. When 3.0 graduates to release status, right-shift one on the CDs, and ship 3.0.x and 2.2.x as the subscription. That is, make the subscription be current release, and mature oldie-but-goodie. Let the subscribers decide which they want to install and run. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 From owner-freebsd-stable Mon May 5 18:08:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA03463 for stable-outgoing; Mon, 5 May 1997 18:08:29 -0700 (PDT) Received: from mailhost.anasazi.com (mailhost.anasazi.com [138.113.128.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA03454 for ; Mon, 5 May 1997 18:08:27 -0700 (PDT) Received: from chad.anasazi.com by mailhost.anasazi.com (5.65/3.7) id AA26019; Mon, 5 May 97 18:07:55 -0700 Received: by chad.anasazi.com (5.65/3.7) id AA18210; Mon, 5 May 97 18:07:52 -0700 From: chad@anasazi.com (Chad R. Larson) Message-Id: <9705060107.AA18210@chad.anasazi.com> Subject: INN and mmap() To: freebsd-stable@freebsd.org Date: Mon, 5 May 1997 18:07:51 -0700 (MST) Reply-To: chad@anasazi.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We installed a 2.1.7 machine straight from the ftp server, and loaded the package of INN from there as well. We set it up as our company's internal and external news server. INN regularly complained when trying to install cross-posted articles, saying the the attempt to make the like failed as the target already existed. The INN FAQ said that error is frequently due to a mis-behaving mmap() implementation. We rebuilt INN to not use mmap() and the problem indeed went away. I'm left with a couple of questions. 1) Shouldn't the port/package for the 2.1.x tree not use mmap(), if it doesn't behave the way INN expects? 2) Is the 2.1 mmap() broken, or is there just a misunderstanding between the implementation and INN's expectations? 3) Has mmap() been changed in 2.2 or 3.0? If so, are the changes slated to be rolled into the RELENG_2_1_0 tree? -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 From owner-freebsd-stable Mon May 5 19:12:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA06544 for stable-outgoing; Mon, 5 May 1997 19:12:28 -0700 (PDT) Received: from lithium.maximum.net (x.maximum.net [205.161.109.86]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA06537 for ; Mon, 5 May 1997 19:12:21 -0700 (PDT) Received: from localhost (daleg@localhost) by lithium.maximum.net (8.8.5/8.8.4) with SMTP id WAA10001; Mon, 5 May 1997 22:06:28 -0400 Date: Mon, 5 May 1997 22:06:27 -0400 (EDT) From: Dale Ghent Reply-To: Dale Ghent To: "Chad R. Larson" cc: freebsd-stable@FreeBSD.ORG Subject: Re: INN and mmap() In-Reply-To: <9705060107.AA18210@chad.anasazi.com> Message-ID: X-President-Clinton: On Crack X-LART: Homelite Chainsaw MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 5 May 1997, Chad R. Larson wrote: | We installed a 2.1.7 machine straight from the ftp server, and loaded | the package of INN from there as well. We set it up as our company's | internal and external news server. | | INN regularly complained when trying to install cross-posted articles, | saying the the attempt to make the like failed as the target already | existed. You may be running crosspost. You can either: 1) comment out or remove the crosspost channel entry in the newsfeeds file and ctlinnd reload newsfeeds 2) Run innd with the -L option. -Dale G. From owner-freebsd-stable Mon May 5 21:33:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA13970 for stable-outgoing; Mon, 5 May 1997 21:33:24 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA13964 for ; Mon, 5 May 1997 21:33:22 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id VAA12123; Mon, 5 May 1997 21:33:52 -0700 (PDT) To: chad@anasazi.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: 2.1.8 Release In-reply-to: Your message of "Mon, 05 May 1997 18:00:00 PDT." <9705060100.AA18202@chad.anasazi.com> Date: Mon, 05 May 1997 21:33:52 -0700 Message-ID: <12121.862893232@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I also must admit I have found no use for the "live filesystem" CD-ROM > in my subscription. I freely admit that might be different if I didn't Actually, the live filesystem CDROM is finding more use as: A boot filesystem (yep, believe it or not, you can even sort of do this now with DEVFS) for truly interesting stand-alone configurations. A repair tool. With sysinstall's fixit option, you can now mount the CD as your toolset and basically repair just about anything on a FreeBSD system. You've got *all* the tools available, just as if you had a rescue root+usr filesystem available on a shoebox drive or something. Don't knock it 'till you've needed it at 3am. :-) > That being said, here's what I'd prefer for my CD-ROM buying dollar. > Yes, please, make a 2.1.8 release. I'm assuming it would be essentally That said, I still suppose I could make 2.1.8 a single CD set. If you want to rescue yourself, you can still use your 2nd CD from 2.1.7. Jordan From owner-freebsd-stable Mon May 5 23:33:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA19459 for stable-outgoing; Mon, 5 May 1997 23:33:26 -0700 (PDT) Received: from mercury.uniserve.com (mercury.uniserve.com [204.191.197.248]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA19453 for ; Mon, 5 May 1997 23:33:24 -0700 (PDT) Received: from haven.uniserve.com (shell.uniserve.com [198.53.215.121]) by mercury.uniserve.com with SMTP id XAA01047; Mon, 5 May 1997 23:32:07 -0700 (PDT) Date: Mon, 5 May 1997 23:38:55 -0700 (PDT) From: Tom Samplonius To: "Chad R. Larson" cc: freebsd-stable@FreeBSD.ORG Subject: Re: INN and mmap() In-Reply-To: <9705060107.AA18210@chad.anasazi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 5 May 1997, Chad R. Larson wrote: > We installed a 2.1.7 machine straight from the ftp server, and loaded > the package of INN from there as well. We set it up as our company's > internal and external news server. > > INN regularly complained when trying to install cross-posted articles, > saying the the attempt to make the like failed as the target already > existed. > > The INN FAQ said that error is frequently due to a mis-behaving mmap() > implementation. We rebuilt INN to not use mmap() and the problem indeed > went away. > > I'm left with a couple of questions. > > 1) Shouldn't the port/package for the 2.1.x tree not use mmap(), if > it doesn't behave the way INN expects? There is a mailing list for ports issues. > 2) Is the 2.1 mmap() broken, or is there just a misunderstanding > between the implementation and INN's expectations? Difference of opinion. > 3) Has mmap() been changed in 2.2 or 3.0? If so, are the changes > slated to be rolled into the RELENG_2_1_0 tree? No. Newever versions of INN, have a msync() option that allows mmap() to work properly. Be ware, mmap() may not allows be the speedup it seems. > -crl > -- > Chad R. Larson (CRL22) Brother, can you paradigm? > 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com > Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 > Tom From owner-freebsd-stable Tue May 6 07:07:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA12329 for stable-outgoing; Tue, 6 May 1997 07:07:51 -0700 (PDT) Received: from fgate.flevel.co.uk (root@fgate.flevel.co.uk [194.6.101.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA12270; Tue, 6 May 1997 07:07:39 -0700 (PDT) Received: from localhost (fxhtml@localhost) by fgate.flevel.co.uk (8.8.3/8.6.9) with SMTP id PAA05267; Tue, 6 May 1997 15:07:40 +0100 (BST) Date: Tue, 6 May 1997 15:07:40 +0100 (BST) From: FXHTML User To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, freebsd-chat@freebsd.org Subject: BETA Testers Wanted Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Fourth Level Developments are looking for a number of beta testers for their FXHTML product. If you have a bit of time and a FreeBSD machine running either Apache or Cern WWW server then you would be suitable. FXHTML is a server side extension to HTML that in most cases eliminates the need for cgi scripting. Take a look at: http://www.flevel.co.uk/fxhtml for more details. If you are interested then please email: fxhtml@flevel.co.uk Thankyou. Trefor Southwell. Fourth Level Developments LTD. From owner-freebsd-stable Tue May 6 07:32:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA13556 for stable-outgoing; Tue, 6 May 1997 07:32:45 -0700 (PDT) Received: from clio.rice.edu (clio.rice.edu [128.42.105.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA13551 for ; Tue, 6 May 1997 07:32:41 -0700 (PDT) Received: by clio.rice.edu (AIX 3.2/UCB 5.64/4.03) id AA12817; Tue, 6 May 1997 09:19:12 -0500 Date: Tue, 6 May 1997 09:19:12 -0500 From: keyser@clio.rice.edu (Kevin Keyser) Message-Id: <9705061419.AA12817@clio.rice.edu> To: freebsd-stable@FreeBSD.ORG Subject: frozen virtual terminals on Dell system Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, I sent this note to questions@freebsd.org a few weeks ago and got no replies, so I am trying here. If you have already seen it, please excuse the duplication. I am having a problem with the virtual terminal system on a machine running FreeBSD 2.1.5R. The hardware is: Dell Optiflex GXL 5166 (166MHz P5 PCI/ISA) 32M real memory 3Com 3C509 Etherlink III 16-bit ethernet card Adaptec 1542C SCSI card 1.0G IBM SCSI disk (originally from an RS6000/370) Phoenix S3 Trio64+ video adapter (built into motherboard) IDE controller (in motherboard) w/ Quantum 2.0G (not used by FreeBSD) PS/2 style mouse (have tried booting with and without psm0) 3.5" floppy System Commander is installed (I occasionally need OS/2 or Win95 which reside on the IDE disk). The install went smoothly and the system boots fine and recognizes all the hardware for which I have the kernel configured. At some point (not coincident with any other event I can think of) the system stops responding to all keyboard input, just as if the keyboard had been unplugged. I can still login across the network and everything else seems healthy. I can echo something to /dev/ttyv0 and it shows up there, and I can kill the process at that terminal and init spawns a new getty just fine. The same problem existed before I switched from the GENERIC kernel to one that I customized to my machine. I have included the output of dmesg below in case it would be helpful. Thanks in advance for any help you can give me. Kevin Keyser keyser@clio.rice.edu -------------------------------- bluehen# dmesg FreeBSD 2.1.5-RELEASE #0: Thu Apr 24 14:57:27 CDT 1997 keyser@bluehen.shell.com:/usr/src/sys/compile/BLUEHEN CPU: 166-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30789632 (30068K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 2 on pci0:7:0 chip2 rev 2 on pci0:7:1 vga0 rev 67 int a irq 11 on pci0:16 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0: disabled, not probed. aha0 at 0x334-0x337 irq 10 drq 6 on isa aha0 waiting for scsi devices to settle (aha0:4:0): "IBM 0663L12 s z" type 0 fixed SCSI 2 sd0(aha0:4:0): Direct-Access 958MB (1962030 512 byte sectors) 2 3C5x9 board(s) on ISA found at 0x300 0x210 ep0 at 0x300-0x30f irq 12 on isa ep0: aui/utp/bnc[*AUI*] address 00:60:97:99:1a:66 npx0 on motherboard npx0: INT 16 interface From owner-freebsd-stable Tue May 6 16:18:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12590 for stable-outgoing; Tue, 6 May 1997 16:18:35 -0700 (PDT) Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12585 for ; Tue, 6 May 1997 16:18:30 -0700 (PDT) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by nasu.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id IAA31500; Wed, 7 May 1997 08:18:16 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (2on+wDoH1cBth0q96v1bgL6DWtdU+ekv@zodiac.mech.utsunomiya-u.ac.jp [160.12.33.1]) by outmail.utsunomiya-u.ac.jp (8.8.4+2.7Wbeta4/3.5Wpl3) with ESMTP id IAA30493; Wed, 7 May 1997 08:18:06 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zenith.mech.utsunomiya-u.ac.jp [160.12.33.60]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id IAA04330; Wed, 7 May 1997 08:23:00 +0900 (JST) Message-Id: <199705062323.IAA04330@zodiac.mech.utsunomiya-u.ac.jp> To: keyser@clio.rice.edu (Kevin Keyser) cc: freebsd-stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: frozen virtual terminals on Dell system In-reply-to: Your message of "Tue, 06 May 1997 09:19:12 EST." <9705061419.AA12817@clio.rice.edu> References: <9705061419.AA12817@clio.rice.edu> Date: Wed, 07 May 1997 08:22:59 +0900 From: Kazutaka YOKOTA Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I am having a problem with the virtual terminal system on a machine >running FreeBSD 2.1.5R. The hardware is: [....] >The install went smoothly and the system boots fine and recognizes all >the hardware for which I have the kernel configured. At some point >(not coincident with any other event I can think of) the system stops >responding to all keyboard input, just as if the keyboard had been >unplugged. I can still login across the network and everything else >seems healthy. I can echo something to /dev/ttyv0 and it shows up >there, and I can kill the process at that terminal and init spawns a >new getty just fine. FreeBSD 2.1.X has an annoying habit of occasionally loosing keyboard interrupts. In addition, the conflicting access to the keyboard controller by the console driver and the PS/2 mouse driver is not handled well. All this leads to keyboard lock up or frozen mouse movement. However, the rest of the system is fine even if this happens, as you have discovered. When keyboard lock up occurs next time, login via network and try the following command (you may need to be root to do this). It may just work: kbdcontrol -r fast < /dev/ttyv0 If you try the above command while you are running X, the PS/2 mouse may go wild on your screen after the keyboard is recovered. If that is the case, try switching away from X to any vty and come back to X, and your mouse should be OK. One last comment: >FreeBSD 2.1.5-RELEASE #0: Thu Apr 24 14:57:27 CDT 1997 > keyser@bluehen.shell.com:/usr/src/sys/compile/BLUEHEN >CPU: 166-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) > Origin = "GenuineIntel" Id = 0x52c Stepping=12 > Features=0x1bf >real memory = 33554432 (32768K bytes) >avail memory = 30789632 (30068K bytes) >Probing for devices on PCI bus 0: >chip0 rev 2 on pci0:0 >chip1 rev 2 on pci0:7:0 >chip2 rev 2 on pci0:7:1 >vga0 rev 67 int a irq 11 on pci0:16 >Probing for devices on the ISA bus: >sc0 at 0x60-0x6f irq 1 on motherboard >sc0: VGA color <16 virtual consoles, flags=0x0> >sio0 at 0x3f8-0x3ff irq 4 on isa >sio0: type 16550A >sio1 at 0x2f8-0x2ff irq 3 on isa >sio1: type 16550A >lpt0 at 0x378-0x37f irq 7 on isa >lpt0: Interrupt-driven port >lp0: TCP/IP capable interface >psm0: disabled, not probed. ~~~~~~~~~~~~~~~~~~~~~~~~~~~ When psm0 is enabled, is it recognized? If so you should see: psm0 at 0x60-0x63 irq 12 on motherboard Kazu From owner-freebsd-stable Tue May 6 16:34:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA13358 for stable-outgoing; Tue, 6 May 1997 16:34:13 -0700 (PDT) Received: from perseverance.sands.com (dal99.metronet.com [192.245.137.99]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA13353 for ; Tue, 6 May 1997 16:34:07 -0700 (PDT) Received: from localhost.sands.com (localhost.sands.com [127.0.0.1]) by perseverance.sands.com (8.7.5/8.7.3) with SMTP id SAA12722; Tue, 6 May 1997 18:36:42 -0500 (CDT) Message-Id: <199705062336.SAA12722@perseverance.sands.com> X-Authentication-Warning: perseverance.sands.com: Host localhost.sands.com [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6.9 8/22/96 To: keyser@clio.rice.edu (Kevin Keyser) cc: freebsd-stable@FreeBSD.ORG Subject: Re: frozen virtual terminals on Dell system In-reply-to: Your message of "Tue, 06 May 1997 09:19:12 CDT." <9705061419.AA12817@clio.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 06 May 1997 18:36:41 -0500 From: Ted Spradley Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The install went smoothly and the system boots fine and recognizes all > the hardware for which I have the kernel configured. At some point > (not coincident with any other event I can think of) the system stops > responding to all keyboard input, just as if the keyboard had been ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > unplugged. ^^^^^^^^^ Have you eliminated exactly that? I have a wonderful little IBM keyboard that I was using with a mini-DIN to normal-DIN adapter plus an extension cable, and I got the same symptoms quite often. The connections all seemed fine when I checked them, but if I disconnected and reconnected it, it would immediately start working fine again. Just a flakey connector, I guess. Doesn't hurt to check the really stupid stuff. > Kevin Keyser > keyser@clio.rice.edu Ted Spradley tsprad@metronet.com +1-972-484-5356 Brisco: "...the more I learn the less I know." Bowler: "At the rate we're learning things we won't know nothing in no time." From owner-freebsd-stable Wed May 7 05:49:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA20461 for stable-outgoing; Wed, 7 May 1997 05:49:41 -0700 (PDT) Received: from clio.rice.edu (clio.rice.edu [128.42.105.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id FAA20456 for ; Wed, 7 May 1997 05:49:39 -0700 (PDT) Received: by clio.rice.edu (AIX 3.2/UCB 5.64/4.03) id AA13097; Wed, 7 May 1997 07:36:10 -0500 Date: Wed, 7 May 1997 07:36:10 -0500 From: keyser@clio.rice.edu (Kevin Keyser) Message-Id: <9705071236.AA13097@clio.rice.edu> To: tsprad@mail.metronet.com Subject: Re: frozen virtual terminals on Dell system Cc: freebsd-stable@FreeBSD.ORG Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > (not coincident with any other event I can think of) the system stops > > responding to all keyboard input, just as if the keyboard had been > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > unplugged. > ^^^^^^^^^ > Have you eliminated exactly that? I have a wonderful little IBM keyboard that > I was using with a mini-DIN to normal-DIN adapter plus an extension cable, and > I got the same symptoms quite often. The connections all seemed fine when I > checked them, but if I disconnected and reconnected it, it would immediately > start working fine again. Just a flakey connector, I guess. > > Doesn't hurt to check the really stupid stuff. > > Ted Spradley tsprad@metronet.com +1-972-484-5356 > Brisco: "...the more I learn the less I know." > Bowler: "At the rate we're learning things we won't know nothing in no time." In fact I did check this and it was not the problem. Even tried a different keyboard. Also, things work fine (relatively speaking) when booted into Win95. This makes me think the hardware is OK and I must have some config problem, IRQ conflict (though I don't see one), etc. Kevin Keyser keyser@clio.rice.edu From owner-freebsd-stable Wed May 7 06:18:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA21482 for stable-outgoing; Wed, 7 May 1997 06:18:58 -0700 (PDT) Received: from clio.rice.edu (clio.rice.edu [128.42.105.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA21477 for ; Wed, 7 May 1997 06:18:56 -0700 (PDT) Received: by clio.rice.edu (AIX 3.2/UCB 5.64/4.03) id AA13108; Wed, 7 May 1997 08:05:18 -0500 Date: Wed, 7 May 1997 08:05:18 -0500 From: keyser@clio.rice.edu (Kevin Keyser) Message-Id: <9705071305.AA13108@clio.rice.edu> To: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: frozen virtual terminals on Dell system Cc: freebsd-stable@freebsd.org Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >the hardware for which I have the kernel configured. At some point > >(not coincident with any other event I can think of) the system stops > >responding to all keyboard input, just as if the keyboard had been > >unplugged. I can still login across the network and everything else > >seems healthy. I can echo something to /dev/ttyv0 and it shows up > > FreeBSD 2.1.X has an annoying habit of occasionally loosing keyboard > interrupts. In addition, the conflicting access to the keyboard > controller by the console driver and the PS/2 mouse driver is not > handled well. All this leads to keyboard lock up or frozen mouse > movement. Two questions: Has this improved with 2.2.X? What particular hardware setups cause this problem to show itself? I have a 2.1.0R system (P5/60/PCI/EISA) which has never had this behavior. > However, the rest of the system is fine even if this happens, as you > have discovered. When keyboard lock up occurs next time, login via > network and try the following command (you may need to be root to do > this). It may just work: > > kbdcontrol -r fast < /dev/ttyv0 OK, this is a step in the right direction. I tried it and the problem cleared up briefly only to return again. Sometimes it takes muliple executions of this command to have an effect, but at least I do not have to reboot to have some use of the console. Many thanks. > One last comment: > > >psm0: disabled, not probed. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > When psm0 is enabled, is it recognized? If so you should see: > > psm0 at 0x60-0x63 irq 12 on motherboard Yes, it is recognized when enabled and this is exactly the message I see. > Kazu Kevin Keyser keyser@clio.rice.edu From owner-freebsd-stable Wed May 7 09:44:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA01032 for stable-outgoing; Wed, 7 May 1997 09:44:59 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01025 for ; Wed, 7 May 1997 09:44:56 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id JAA29345; Wed, 7 May 1997 09:44:45 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id JAA05744; Wed, 7 May 1997 09:38:17 -0700 (PDT) Message-Id: <199705071638.JAA05744@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: keyser@clio.rice.edu (Kevin Keyser) cc: tsprad@mail.metronet.com, freebsd-stable@freebsd.org Subject: Re: frozen virtual terminals on Dell system In-reply-to: Your message of Wed, 07 May 97 07:36:10 -0500. <9705071236.AA13097@clio.rice.edu> Date: Wed, 07 May 1997 09:38:01 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> > (not coincident with any other event I can think of) the system stops >> > responding to all keyboard input, just as if the keyboard had been >> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >> > unplugged. >> ^^^^^^^^^ >> Have you eliminated exactly that? I have a wonderful little IBM keyboard that [...] >In fact I did check this and it was not the problem. Even tried a >different keyboard. Also, things work fine (relatively speaking) when >booted into Win95. This makes me think the hardware is OK and I must >have some config problem, IRQ conflict (though I don't see one), etc. I have seen exactly this same problem under NetBSD. I was going through a switch-box, however, and just assumed the switch-box was to blame. Now, I suspect that it's actually the Dell keyboard hardware. Yes, the machines all run Windows NT and 95 fine. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-stable Wed May 7 10:10:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02229 for stable-outgoing; Wed, 7 May 1997 10:10:13 -0700 (PDT) Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02224 for ; Wed, 7 May 1997 10:10:11 -0700 (PDT) Received: from dvl-1.pathlink.com (dvl-1.pathlink.com [204.30.237.241]) by dopey.pathlink.com (8.8.5/8.8.5) with SMTP id KAA22752 for ; Wed, 7 May 1997 10:20:38 -0700 (PDT) Message-Id: <1.5.4.32.19970507101001.006db218@dopey.pathlink.com> X-Sender: kachun@dopey.pathlink.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 07 May 1997 10:10:01 +0000 To: freebsd-stable@freebsd.org From: Kachun Lee Subject: kern malloc leak in 2.2X ? Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk After upgrading to 2.2 (2.2beta thru 2.2-releng-970422), some of our systems would panic with 'kmem_map too small' every ~30 hours - clockwork. Per suggestion of Mr. Greenman, I increased VM_KMEM_SIZE from 32M to 48M. The systems still panic, but now about every 2.5days. That leads me to believe there may be a memory leak in 2.2X. Those systems are all heavy NFS clients over SMC 100 netcards. I wouldn't mind spend sometime to identify the problem, if someone could point me to the right direction. The last time I did any UNIX kernel work was back with UNIX sysIII.5. Any suggestion would be greatly appreicated. Best regards From owner-freebsd-stable Wed May 7 10:12:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02345 for stable-outgoing; Wed, 7 May 1997 10:12:16 -0700 (PDT) Received: from tarkin.smlab.com (tarkin.smlab.com [208.132.36.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02340 for ; Wed, 7 May 1997 10:12:14 -0700 (PDT) Received: from r2d2.smlab.com (mike@r2d2.smlab.com [192.168.2.7]) by tarkin.smlab.com (8.8.5/8.7.3) with SMTP id NAA27835; Wed, 7 May 1997 13:21:18 -0400 (EDT) Received: from localhost (mike@localhost) by r2d2.smlab.com (8.6.11/8.6.11) with SMTP id NAA05277; Wed, 7 May 1997 13:14:34 -0400 Date: Wed, 7 May 1997 13:14:34 -0400 (EDT) From: Mike Nowlin To: "Michael L. VanLoon -- HeadCandy.com" cc: freebsd-stable@FreeBSD.ORG Subject: Re: frozen virtual terminals on Dell system In-Reply-To: <199705071638.JAA05744@MindBender.serv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 7 May 1997, Michael L. VanLoon -- HeadCandy.com wrote: > I have seen exactly this same problem under NetBSD. I was going > through a switch-box, however, and just assumed the switch-box was to > blame. Now, I suspect that it's actually the Dell keyboard hardware. We have a single keyboard connected via switch box to a FreeBSD 2.1.7 machine, two Linux boxes, and a Win95 box... If you flip the switch too fast, the keyboard locks up. But if you "pause" between the switch positions (halfway between A and B), it works fine... Has something to do with the keyboard power being cut off and the sync pulses from the CPUs... --mike From owner-freebsd-stable Wed May 7 11:15:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA05973 for stable-outgoing; Wed, 7 May 1997 11:15:27 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA05957 for ; Wed, 7 May 1997 11:15:23 -0700 (PDT) Received: (qmail 19714 invoked by uid 1000); 7 May 1997 18:01:16 -0000 Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199705071638.JAA05744@MindBender.serv.net> Date: Wed, 07 May 1997 10:58:50 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: "Michael L. VanLoon -- HeadCandy.com" Subject: Re: frozen virtual terminals on Dell system Cc: freebsd-stable@FreeBSD.ORG, (Kevin Keyser) Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Michael L. VanLoon -- HeadCandy.com; On 07-May-97 you wrote: ... > Yes, the machines all run Windows NT and 95 fine. ... and that is all that counts. Right? :-) A new, M$-only keyboard? Simon From owner-freebsd-stable Wed May 7 13:58:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA17109 for stable-outgoing; Wed, 7 May 1997 13:58:51 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA17104 for ; Wed, 7 May 1997 13:58:49 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id NAA24742; Wed, 7 May 1997 13:59:08 -0700 (PDT) Message-Id: <199705072059.NAA24742@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Kachun Lee cc: freebsd-stable@FreeBSD.ORG Subject: Re: kern malloc leak in 2.2X ? In-reply-to: Your message of "Wed, 07 May 1997 10:10:01 -0000." <1.5.4.32.19970507101001.006db218@dopey.pathlink.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 07 May 1997 13:59:08 -0700 Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >After upgrading to 2.2 (2.2beta thru 2.2-releng-970422), some of our systems >would panic with 'kmem_map too small' every ~30 hours - clockwork. Per >suggestion of Mr. Greenman, I increased VM_KMEM_SIZE from 32M to 48M. The >systems still panic, but now about every 2.5days. That leads me to believe >there may be a memory leak in 2.2X. Those systems are all heavy NFS clients >over SMC 100 netcards. > >I wouldn't mind spend sometime to identify the problem, if someone could >point me to the right direction. The last time I did any UNIX kernel work >was back with UNIX sysIII.5. Any suggestion would be greatly appreicated. After two days, do a "vmstat -m"; this gives a break-down of memory allocations in the kernel and should provide a clue to the problem. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-stable Wed May 7 14:27:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA18831 for stable-outgoing; Wed, 7 May 1997 14:27:35 -0700 (PDT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA18825 for ; Wed, 7 May 1997 14:27:33 -0700 (PDT) Received: (from krentel@localhost) by cs.rice.edu (8.8.5/8.7.1) id QAA04248 for freebsd-stable@freebsd.org; Wed, 7 May 1997 16:27:29 -0500 (CDT) Date: Wed, 7 May 1997 16:27:29 -0500 (CDT) From: "Mark W. Krentel" Message-Id: <199705072127.QAA04248@cs.rice.edu> To: freebsd-stable@freebsd.org Subject: Re: frozen virtual terminals on Dell system Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > FreeBSD 2.1.X has an annoying habit of occasionally loosing keyboard > interrupts. In addition, the conflicting access to the keyboard > controller by the console driver and the PS/2 mouse driver is not > handled well. All this leads to keyboard lock up or frozen mouse > movement. That's interesting. I once had a keyboard lock up after disconnecting it for 1 day to use on another machine. Machine is a PPro 200 on Intel Venus VS440FX board (apparently with Intel's own BIOS) running 2.1.7. We borrowed the keyboard for > 24 hours, and on reconnecting, all keystrokes were ignored. We ended up rebooting, which worked and also kicked off the screen saver. There was nothing in the logs to indicate trouble, but just before it rebooted, I saw a SIGPIPE messge on the console (couldn't see it before because of screen saver). At the time, I dismissed it as something quirky in the Intel Venus board. As a test, I tried disconnecting the keyboard on another machine (regular Pentium on ASUS/Award board running 2.2.1-release). No problems. These Intel boards are stable and reliable, but give you almost nothing you can configure. No options for ignoring errors from keyboards, video cards, etc, nothing for setting memory timings. Intel knows what's best for you. I have no complaints, it's an excellent, reliable board, but if you want to tinker with the memory timings, try ASUS. So, was I right to blame the board, or was it freebsd 2.1.7? More importantly, what should I try short of rebooting? --Mark Krentel From owner-freebsd-stable Wed May 7 16:10:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA23872 for stable-outgoing; Wed, 7 May 1997 16:10:10 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA23809; Wed, 7 May 1997 16:09:58 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id TAA12926; Wed, 7 May 1997 19:08:48 -0400 (EDT) Date: Wed, 7 May 1997 19:08:48 -0400 (EDT) From: Brian Tao To: FREEBSD-STABLE , FREEBSD-HACKERS Subject: NFS service mysteriously stopping on 2.2-RELENG? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The 2.2-970420-RELENG NFS server I put together for a client is humming along quite nicely, now that I've done fiddling with it. However, there is an intermittent problem with the three BSD/OS clients attached to it. One two occasions in the past week, all three clients will "lose" the NFS server. One client is running BSD/OS 2.1 with NFSv2 UDP mounts, and the other two are BSD/OS 3.0 with NFSv3 TCP mounts. In addition to the "nfs server not responding" syslog messages, the TCP clients occasionally log this: May 7 04:14:26 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.4 May 7 05:38:45 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.2 May 7 05:38:45 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.3 May 7 05:38:45 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.1 May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.1 May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.2 May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.3 May 7 17:48:24 shell1 kernel: short receive (0/4) from nfs server nfs:/user/.4 I haven't seen this reported on the BSD/OS 2.1 UDP client yet. Sending a SIGKILL to the nfsd's on the FreeBSD server and restarting them with "nfsd -t -u 8" clears things right up. Unfortunately, I don't have any more information than this at the time, but there is a monitor script taking regular snapshots of the process table, nfsstat and netstat now. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-stable Wed May 7 16:11:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA23947 for stable-outgoing; Wed, 7 May 1997 16:11:05 -0700 (PDT) Received: from dopey.pathlink.com (dopey.pathlink.com [204.30.237.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA23940 for ; Wed, 7 May 1997 16:11:02 -0700 (PDT) Received: from dvl-1.pathlink.com (dvl-1.pathlink.com [204.30.237.241]) by dopey.pathlink.com (8.8.5/8.8.5) with SMTP id QAA23162 for ; Wed, 7 May 1997 16:21:33 -0700 (PDT) Message-Id: <1.5.4.32.19970507161052.007086a4@dopey.pathlink.com> X-Sender: kachun@dopey.pathlink.com X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Wed, 07 May 1997 16:10:52 +0000 To: freebsd-stable@freebsd.org From: Kachun Lee Subject: Re: kern malloc leak in 2.2X ? Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 01:59 PM 5/7/97 -0700, you wrote: >>After upgrading to 2.2 (2.2beta thru 2.2-releng-970422), some of our systems >>would panic with 'kmem_map too small' every ~30 hours - clockwork. Per >>suggestion of Mr. Greenman, I increased VM_KMEM_SIZE from 32M to 48M. The >>systems still panic, but now about every 2.5days. That leads me to believe >>there may be a memory leak in 2.2X. Those systems are all heavy NFS clients >>over SMC 100 netcards. >> >>I wouldn't mind spend sometime to identify the problem, if someone could >>point me to the right direction. The last time I did any UNIX kernel work >>was back with UNIX sysIII.5. Any suggestion would be greatly appreicated. > > After two days, do a "vmstat -m"; this gives a break-down of memory >allocations in the kernel and should provide a clue to the problem. I did that. Look like it all tied in Couldfree. Thanks for the help again. ------------------------------------ Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 44 724 124563 1280 0 32 1956 732 370957 640 1 64 37040 144 32219429 320 0 128 47344 752 23616751 160 1042 256 31520 352 2695471 80 49 512 54370 6 134739 40 0 1K 103 333 51488921 20 39837787 2K 15 15 5544 10 2668 4K 6 3 827 5 0 8K 1 0 1 5 0 16K 4 0 4 5 0 32K 3 0 3 5 0 64K 1 0 1 5 0 256K 1 0 1 5 0 Memory usage type by bucket size Size Type(s) 16 devbuf, pcb, routetbl, namei, vnodes, shm, proc, temp, sysctl 32 devbuf, pcb, routetbl, namei, pgrp, session, NFS req, subproc, MFS node, NFS daemon, ether_multi, temp 64 devbuf, routetbl, ifaddr, NFS req, namecache, shm, VM mapent, VM pgdata, file, lockf, in_multi 128 devbuf, pcb, routetbl, zombie, ifaddr, cred, vnodes, VM map, VM object, VM pgdata, file desc, ttys, isa_devlist 256 devbuf, socket, pcb, routetbl, NFS node, vnodes, VM map, VM pgdata, file desc, subproc, FFS node, MFS node, Export Host, NFS srvsock, NFS daemon, NFSV3 srvdesc, temp, select 512 devbuf, pcb, ioctlops, mount, NFS mount, UFS mount, VM pgdata, file desc, proc, NFS daemon, NFSV3 diroff, BIO buffer 1K devbuf, namei, UFS mount, VM pgdata, file desc, NQNFS Lease, BIO buffer 2K devbuf, UFS mount, VM pgdata, file desc, proc, ttys, BIO buffer 4K devbuf, VM pgdata, temp 8K mbuf 16K devbuf, MSDOSFS mount 32K NFS node, UFS quota, UFS mount 64K namecache 256K VM pgdata Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) mbuf 1 8K 8K 29492K 1 0 0 8K devbuf 31 79K 79K 29492K 56 0 0 16,32,64,128,256, 512,1K,2K,4K,16K socket 633 159K 182K 29492K 311179 0 0 256 pcb 664 123K 158K 29492K 334839 0 0 16,32,128,256,512 routetbl 795 111K 134K 29492K 32714 0 0 16,32,64,128,256 zombie 0 0K 1K 29492K 80152 0 0 128 ifaddr 13 2K 2K 29492K 13 0 0 64,128 namei 0 0K 33K 29492K 51171333 0 0 16,32,1K ioctlops 0 0K 1K 29492K 3 0 0 512 cred 300 38K 43K 29492K 86157 0 0 128 pgrp 305 10K 11K 29492K 75026 0 0 32 session 303 10K 11K 29492K 74884 0 0 32 mount 22 11K 11K 29492K 75 0 0 512 NFS req 9 1K 9K 29492K 26866954 0 0 32,64 NFS mount 18 9K 9K 29492K 71 0 0 512 NFS node 21474 5401K 5825K 29492K 1345761 0 0 256,32K vnodes 30037 3755K 3763K 29492K 32056 0 0 16,128,256 namecache 30001 1923K 1923K 29492K 30001 0 0 64,64K UFS quota 1 32K 32K 29492K 1 0 0 32K UFS mount 10 43K 43K 29492K 10 0 0 512,1K,2K,32K shm 283 18K 21K 29492K 71564 0 0 16,64 VM map 325 81K 92K 29492K 80477 0 0 128,256 VM mapent 5495 344K 344K 29492K 5495 0 0 64 VM object 15972 1997K 2070K 29492K 23100416 0 0 128 VM pgdata 537 253K 255K 29492K 1266 0 0 64,128,256,512,1K ,2K,4K,256K file 1009 64K 72K 29492K 4364888 0 0 64 file desc 323 48K 52K 29492K 80691 0 0 128,256,512,1K,2K lockf 1 1K 1K 29492K 890640 0 0 64 proc 327 165K 188K 29492K 80480 0 0 16,512,2K subproc 325 12K 14K 29492K 160629 0 0 32,256 FFS node 7925 1982K 3901K 29492K 329661 0 0 256 MFS node 1 1K 1K 29492K 17 0 0 32,256 NQNFS Lease 1 1K 1K 29492K 1 0 0 1K Export Host 11 3K 3K 29492K 11 0 0 256 NFS srvsock 2 1K 1K 29492K 2 0 0 256 NFS daemon 69 5K 5K 29492K 69 0 0 32,256,512 in_multi 4 1K 1K 29492K 4 0 0 64 ether_multi 3 1K 1K 29492K 3 0 0 32 NFSV3 srvdesc 0 0K 1K 29492K 352586 0 0 256 NFSV3 diroff 53978 26989K 26989K 29492K 53978 0 0 512 MSDOSFS mount 1 16K 16K 29492K 1 0 0 16K temp 590 22K 46K 29492K 217877 0 0 16,32,256,4K ttys 247 35K 45K 29492K 1222 0 0 128,2K isa_devlist 1 1K 1K 29492K 1 0 0 128 sysctl 0 0K 1K 29492K 1 0 0 16 BIO buffer 64 66K 419K 29492K 350782 0 0 512,1K,2K select 296 74K 85K 29492K 73168 0 0 256 Memory Totals: In Use Free Requests 43876K 604K 110657216 From owner-freebsd-stable Wed May 7 17:23:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27579 for stable-outgoing; Wed, 7 May 1997 17:23:12 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA27574 for ; Wed, 7 May 1997 17:23:08 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id JAA26316; Thu, 8 May 1997 09:52:58 +0930 (CST) From: Michael Smith Message-Id: <199705080022.JAA26316@genesis.atrad.adelaide.edu.au> Subject: Re: kern malloc leak in 2.2X ? In-Reply-To: <1.5.4.32.19970507161052.007086a4@dopey.pathlink.com> from Kachun Lee at "May 7, 97 04:10:52 pm" To: kachun@zippo.com (Kachun Lee) Date: Thu, 8 May 1997 09:52:57 +0930 (CST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kachun Lee stands accused of saying: > NFSV3 diroff 53978 26989K 26989K 29492K 53978 0 0 512 Here's your culprit. A short-term workaround might be to use NFSv2 mounts until this one can be caught. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-stable Wed May 7 17:30:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27956 for stable-outgoing; Wed, 7 May 1997 17:30:36 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA27951 for ; Wed, 7 May 1997 17:30:33 -0700 (PDT) Received: (qmail 23258 invoked by uid 1000); 8 May 1997 00:06:39 -0000 Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199705072127.QAA04248@cs.rice.edu> Date: Wed, 07 May 1997 17:01:10 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: "Mark W. Krentel" Subject: Re: frozen virtual terminals on Dell system Cc: freebsd-stable@FreeBSD.ORG Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi Mark W. Krentel; On 07-May-97 you wrote: ... > That's interesting. I once had a keyboard lock up after disconnecting > it for 1 day to use on another machine. Machine is a PPro 200 on > Intel Venus VS440FX board (apparently with Intel's own BIOS) running > 2.1.7. We borrowed the keyboard for > 24 hours, and on reconnecting, > all keystrokes were ignored. > > We ended up rebooting, which worked and also kicked off the screen > saver. There was nothing in the logs to indicate trouble, but just > before it rebooted, I saw a SIGPIPE messge on the console (couldn't > see it before because of screen saver). ... This is a feature, I think. The keyboard is not supposed to unplub and re-plug while the system is powderd up. Most do, but not necessarily. If something wants to download or configure in the keyboard at power up, it will not have it. some keyboard/motherboard combinations want to. Simon From owner-freebsd-stable Wed May 7 17:41:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA28503 for stable-outgoing; Wed, 7 May 1997 17:41:19 -0700 (PDT) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [207.95.42.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28498 for ; Wed, 7 May 1997 17:41:15 -0700 (PDT) Received: from dingo.its.enc.edu (dingo.its.enc.edu [207.95.222.250]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id UAA24574; Wed, 7 May 1997 20:37:09 -0400 (EDT) Date: Wed, 7 May 1997 20:42:15 -0400 (EDT) From: Charles Owens X-Sender: owensc@dingo.its.enc.edu To: Mike Nowlin cc: "Michael L. VanLoon -- HeadCandy.com" , freebsd-stable@FreeBSD.ORG Subject: Re: frozen virtual terminals on Dell system In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 7 May 1997, Mike Nowlin wrote: > > > On Wed, 7 May 1997, Michael L. VanLoon -- HeadCandy.com wrote: > > > I have seen exactly this same problem under NetBSD. I was going > > through a switch-box, however, and just assumed the switch-box was to > > blame. Now, I suspect that it's actually the Dell keyboard hardware. > > We have a single keyboard connected via switch box to a FreeBSD 2.1.7 > machine, two Linux boxes, and a Win95 box... If you flip the switch too > fast, the keyboard locks up. But if you "pause" between the switch > positions (halfway between A and B), it works fine... Has something to do > with the keyboard power being cut off and the sync pulses from the CPUs... > > --mike Some switch boxes have diodes on the keyboard power lines that are supposed to maintain constant power to the keyboard while switching. My friend found that this was actually causing some kind of spike that was blowing the keyboard power fuse on the motherboard. He blew two of these fuses and then decided to remove the diodes and wire the power lines the same as all other lines. Now when the switch is flipped power the keyboard gets power cycled. He's not had any more trouble. To be safe, when I bought my switchbox (from JDR) I rewired it in the same manner and have had no problems in over a year and a half of frequent switching. (I don't have a Dell, BTW...) --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- From owner-freebsd-stable Wed May 7 22:42:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA10242 for stable-outgoing; Wed, 7 May 1997 22:42:49 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA10237 for ; Wed, 7 May 1997 22:42:46 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id WAA04499; Wed, 7 May 1997 22:42:54 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id WAA07910; Wed, 7 May 1997 22:41:15 -0700 (PDT) Message-Id: <199705080541.WAA07910@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Charles Owens cc: Mike Nowlin , freebsd-stable@freebsd.org Subject: Re: frozen virtual terminals on Dell system In-reply-to: Your message of Wed, 07 May 97 20:42:15 -0400. Date: Wed, 07 May 1997 22:40:59 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Wed, 7 May 1997, Mike Nowlin wrote: >> On Wed, 7 May 1997, Michael L. VanLoon -- HeadCandy.com wrote: >> > I have seen exactly this same problem under NetBSD. I was going >> > through a switch-box, however, and just assumed the switch-box was to >> > blame. Now, I suspect that it's actually the Dell keyboard hardware. >> We have a single keyboard connected via switch box to a FreeBSD 2.1.7 >> machine, two Linux boxes, and a Win95 box... If you flip the switch too >> fast, the keyboard locks up. But if you "pause" between the switch >> positions (halfway between A and B), it works fine... Has something to do >> with the keyboard power being cut off and the sync pulses from the CPUs... >Some switch boxes have diodes on the keyboard power lines that are >supposed to maintain constant power to the keyboard while switching. My >friend found that this was actually causing some kind of spike that was >blowing the keyboard power fuse on the motherboard. He blew two of these [...] >To be safe, when I bought my switchbox (from JDR) I rewired it in the same >manner and have had no problems in over a year and a half of frequent >switching. Let me assure you that isn't the problem in my case. These are very expensive high-end fully digital switch-boxes (they even super-impose the name of the machine you're switched to in the corner of your display). We have literally hundreds of machines (many Dells) hooked up to these running NT. The two running NetBSD are the two that I'm having problems with. >(I don't have a Dell, BTW...) Well then, that's likely not going to help my case much, then. :-) It seems that this is a Dell-specific "feature". They like to do some things their own way, and I wouldn't be surprised a bit if they made some funky half-compatible keyboard mod. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-stable Thu May 8 05:44:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA24610 for stable-outgoing; Thu, 8 May 1997 05:44:11 -0700 (PDT) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA24604 for ; Thu, 8 May 1997 05:44:03 -0700 (PDT) Received: from gmarco (ts1port8d.masternet.it [194.184.65.239]) by www.giovannelli.it (8.8.5/8.7.3) with SMTP id OAA10448 for ; Thu, 8 May 1997 14:40:33 GMT Message-Id: <3.0.1.32.19970508143812.006b57e0@giovannelli.it> X-Sender: gmarco@giovannelli.it X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 08 May 1997 14:38:12 +0200 To: freebsd-stable@freebsd.org From: Gianmarco Giovannelli Subject: Strange error compiling kernel... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk During make depend I have on one box this error .... lex -t /usr/src/sys/dev/aic7xxx/scan.l > scan.c cc -O -I. -c scan.c cc -O -I. -c /usr/src/sys/dev/aic7xxx/aic7xxx_asm.c cc -O -I. -c /usr/src/sys/dev/aic7xxx/symbol.c cc -O -I. -o aic7xxx_asm gram.o scan.o aic7xxx_asm.o symbol.o -ll install -c -s -o root -g -m 555 aic7xxx_asm /sys/compile/SCOTTY install: unknown group -m *** Error code 67 Stop. *** Error code 1 Stop. I am running 2.2.1 -STABLE (ctm #269) Boh ? Any ideas ? Thanks again for information.... Regards... Gianmarco "Unix expert since yesterday" Home page: http://www2.masternet.it/~gmarco Server page: http://www2.masternet.it/ From owner-freebsd-stable Thu May 8 06:02:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA25435 for stable-outgoing; Thu, 8 May 1997 06:02:27 -0700 (PDT) Received: from tarkin.smlab.com (tarkin.smlab.com [208.132.36.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA25430 for ; Thu, 8 May 1997 06:02:24 -0700 (PDT) Received: from r2d2.smlab.com (mike@r2d2.smlab.com [192.168.2.7]) by tarkin.smlab.com (8.8.5/8.7.3) with SMTP id JAA28787 for ; Thu, 8 May 1997 09:11:33 -0400 (EDT) Received: from localhost (mike@localhost) by r2d2.smlab.com (8.6.11/8.6.11) with SMTP id JAA08059 for ; Thu, 8 May 1997 09:05:08 -0400 Date: Thu, 8 May 1997 09:05:08 -0400 (EDT) From: Mike Nowlin To: freebsd-stable@FreeBSD.ORG Subject: Re: frozen virtual terminals on Dell system In-Reply-To: <199705080541.WAA07910@MindBender.serv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well then, that's likely not going to help my case much, then. :-) It > seems that this is a Dell-specific "feature". They like to do some > things their own way, and I wouldn't be surprised a bit if they made > some funky half-compatible keyboard mod. You may have said this in the beginning of this discussion, but what Dell model(s) are you dealing with? I have a Dell Optiplex 433s/L that's just sitting here and hasn't been turned on in months. Maybe I'll throw FreeBSD on it and see what happens. I had it running FreeBSD 2.1.0 quite a while ago, and don't remember any problems (except it was sllloooowwww. -- 4MB wasn't quite enough!), but I'm willing to see if I can re-create the problem... --Mike From owner-freebsd-stable Thu May 8 06:37:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA26855 for stable-outgoing; Thu, 8 May 1997 06:37:11 -0700 (PDT) Received: from clio.rice.edu (clio.rice.edu [128.42.105.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA26847 for ; Thu, 8 May 1997 06:37:09 -0700 (PDT) Received: by clio.rice.edu (AIX 3.2/UCB 5.64/4.03) id AA13719; Thu, 8 May 1997 08:23:40 -0500 Date: Thu, 8 May 1997 08:23:40 -0500 From: keyser@clio.rice.edu (Kevin Keyser) Message-Id: <9705081323.AA13719@clio.rice.edu> To: mike@r2d2.smlab.com Subject: Re: frozen virtual terminals on Dell system Cc: freebsd-stable@FreeBSD.ORG Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > You may have said this in the beginning of this discussion, but what Dell > model(s) are you dealing with? I have a Dell Optiplex 433s/L that's just > sitting here and hasn't been turned on in months. Maybe I'll throw > FreeBSD on it and see what happens. I had it running FreeBSD 2.1.0 quite > a while ago, and don't remember any problems (except it was sllloooowwww. > -- 4MB wasn't quite enough!), but I'm willing to see if I can re-create > the problem... > > --Mike My note, which started this discussion, dealt with a Dell Optiplex GXL 5166 running FreeBSD 2.1.5. No switch box in my case, just the keyboard that came with the machine plugged in directly. Kevin Keyser keyser@clio.rice.edu From owner-freebsd-stable Thu May 8 17:05:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA28007 for stable-outgoing; Thu, 8 May 1997 17:05:06 -0700 (PDT) Received: from mailhost.anasazi.com (mailhost.anasazi.com [138.113.128.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA27998 for ; Thu, 8 May 1997 17:05:01 -0700 (PDT) Received: from chad.anasazi.com by mailhost.anasazi.com (5.65/3.7) id AA04324; Thu, 8 May 97 17:04:27 -0700 Received: by chad.anasazi.com (5.65/3.7) id AA23420; Thu, 8 May 97 17:04:23 -0700 From: chad@anasazi.com (Chad R. Larson) Message-Id: <9705090004.AA23420@chad.anasazi.com> Subject: Standard Template Library To: freebsd-stable@freebsd.org Date: Thu, 8 May 1997 17:04:22 -0700 (MST) Reply-To: chad@anasazi.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm looking for help on something that's probably obvious... Some of our developers are working on a set of C++ class libraries. They were interested in how portable the work they were doing was turning out. I gave them a login on one of our FreeBSD 2.1.7 boxes so they could try to build and test using g++. I got back a quick note saying that we were missing the "Standard Template Library". I admit to knowing almost nothing about c++, but I puttered around on the Free Software Foundation's server and found a FAQ that implied this beastie should be in the "libstdc++" library, which (they claim) is distributed as part of gcc as of version 2.6. My gcc says it is a 2.6.3, but that library, it's sources and .h files aren't to be found. So, what is this thing? Should I find it on my machine? If not, where does it (and its associated header files) live? -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 From owner-freebsd-stable Thu May 8 22:58:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12937 for stable-outgoing; Thu, 8 May 1997 22:58:49 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12932 for ; Thu, 8 May 1997 22:58:47 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id WAA25313; Thu, 8 May 1997 22:58:37 -0700 (PDT) Message-Id: <199705090558.WAA25313@austin.polstra.com> To: chad@anasazi.com Subject: Re: Standard Template Library Newsgroups: polstra.freebsd.stable In-Reply-To: <9705090004.AA23420@chad.anasazi.com> References: <9705090004.AA23420@chad.anasazi.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Date: Thu, 08 May 1997 22:58:36 -0700 From: John Polstra Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <9705090004.AA23420@chad.anasazi.com>, Chad R. Larson wrote: > I gave them a login on one of our FreeBSD 2.1.7 boxes so they could try > to build and test using g++. I got back a quick note saying that we > were missing the "Standard Template Library". I admit to knowing almost > nothing about c++, but I puttered around on the Free Software > Foundation's server and found a FAQ that implied this beastie should be > in the "libstdc++" library, which (they claim) is distributed as part of > gcc as of version 2.6. My gcc says it is a 2.6.3, but that library, > it's sources and .h files aren't to be found. It is present in gcc-2.7.2.1, which is the compiler shipped with FreeBSD-2.2 systems. For 2.1.x, you're out of luck. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-stable Thu May 8 23:26:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14405 for stable-outgoing; Thu, 8 May 1997 23:26:28 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA14400 for ; Thu, 8 May 1997 23:26:25 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id XAA27393; Thu, 8 May 1997 23:26:28 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id XAA11705; Thu, 8 May 1997 23:24:52 -0700 (PDT) Message-Id: <199705090624.XAA11705@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Mike Nowlin cc: freebsd-stable@freebsd.org Subject: Re: frozen virtual terminals on Dell system In-reply-to: Your message of Thu, 08 May 97 09:05:08 -0400. Date: Thu, 08 May 1997 23:24:41 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> Well then, that's likely not going to help my case much, then. :-) It >> seems that this is a Dell-specific "feature". They like to do some >> things their own way, and I wouldn't be surprised a bit if they made >> some funky half-compatible keyboard mod. >You may have said this in the beginning of this discussion, but what Dell >model(s) are you dealing with? I have a Dell Optiplex 433s/L that's just >sitting here and hasn't been turned on in months. Maybe I'll throw >FreeBSD on it and see what happens. I had it running FreeBSD 2.1.0 quite >a while ago, and don't remember any problems (except it was sllloooowwww. >-- 4MB wasn't quite enough!), but I'm willing to see if I can re-create >the problem... One of them is a Dell OptiPlex 133MHz Pentium (don't remember the exact numbers and letters). The other is either an OptiPlex or OmniPlex. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-stable Thu May 8 23:34:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA14831 for stable-outgoing; Thu, 8 May 1997 23:34:22 -0700 (PDT) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA14824 for ; Thu, 8 May 1997 23:34:18 -0700 (PDT) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id XAA27591; Thu, 8 May 1997 23:34:27 -0700 (PDT) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id XAA11779; Thu, 8 May 1997 23:32:52 -0700 (PDT) Message-Id: <199705090632.XAA11779@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: chad@anasazi.com cc: freebsd-stable@freebsd.org Subject: Re: Standard Template Library In-reply-to: Your message of Thu, 08 May 97 17:04:22 -0700. <9705090004.AA23420@chad.anasazi.com> Date: Thu, 08 May 1997 23:32:42 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I'm looking for help on something that's probably obvious... >Some of our developers are working on a set of C++ class libraries. >I gave them a login on one of our FreeBSD 2.1.7 boxes so they could try >to build and test using g++. I got back a quick note saying that we >were missing the "Standard Template Library". I admit to knowing almost >nothing about c++, but I puttered around on the Free Software [...] I don't know about GCC's implementation, but just in general, STL is one of the hottest things in the C++ world right now. It's a whole bunch of complex container classes created as templates, so you can automagically contain just about anything. Even includes some really sophisticated btree-ish stuff (based on a red/black tree). I would suspect you'd probably need the very latest GCC to get competant support for STL. You may need to fetch and build it yourself. (Once again speaking as someone who hasn't investigated how much of it comes with FreeBSD or NetBSD, but suspecting that if they had it at all, it would be an older version.) ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-stable Fri May 9 01:16:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20138 for stable-outgoing; Fri, 9 May 1997 01:16:03 -0700 (PDT) Received: from isy.liu.se (root@isy.liu.se [130.236.20.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA20114 for ; Fri, 9 May 1997 01:16:00 -0700 (PDT) Received: from kili.isy.liu.se (kili.isy.liu.se [130.236.27.25]) by isy.liu.se (8.8.5/8.8.5) with SMTP id KAA14106 for ; Fri, 9 May 1997 10:15:57 +0200 (MET DST) Received: from baloo.isy.liu.se (ppp0.isy.liu.se) by kili.isy.liu.se (5.x/SMI-SVR4) id AA22028; Fri, 9 May 1997 10:14:51 +0200 Message-Id: <1.5.4.32.19970509081713.00668494@kili.isy.liu.se> X-Sender: kentp@kili.isy.liu.se (Unverified) X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Fri, 09 May 1997 10:17:13 +0200 To: freebsd-stable@FreeBSD.ORG From: Kent Palmkvist Subject: Re: frozen virtual terminals (not just Dell systems) Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id BAA20132 Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 22:40 1997-05-07 -0700, you wrote: > > >Well then, that's likely not going to help my case much, then. :-) It >seems that this is a Dell-specific "feature". They like to do some >things their own way, and I wouldn't be surprised a bit if they made >some funky half-compatible keyboard mod. > >----------------------------------------------------------------------------- > Michael L. VanLoon michaelv@MindBender.serv.net I don't agree that this is a Dell-specific "feature". I have also had problems with a locking keyboard. The machine is a Kopak (Sager, Prostar etc) 486DX100 laptop. I had problems with locking keyboard if I pressed the extra FN key (used to alter brightness, contrast, volume etc) while running 2.0.x. It got fixed sometime during 2.1.x branch I think. Now with the new 2.2.1 it sometimes locks during installation (have run it multiple times). This happened last time when switching virtual consoles. Another sure keyboard lock is to start XFree. /Kent Kent Palmkvist email: kentp@isy.liu.se Dept.of Electrical Engineering http://www.tde.isy.liu.se/~kentp Linköping University 581 83 LINKÖPING phone: +46 13 281347 Sweden fax: +46 13 139282 From owner-freebsd-stable Fri May 9 21:12:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA15769 for stable-outgoing; Fri, 9 May 1997 21:12:18 -0700 (PDT) Received: from mailhost.anasazi.com (mailhost.anasazi.com [138.113.128.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA15762 for ; Fri, 9 May 1997 21:12:13 -0700 (PDT) Received: from chad.anasazi.com by mailhost.anasazi.com (5.65/3.7) id AA12847; Fri, 9 May 97 21:11:40 -0700 Received: by chad.anasazi.com (5.65/3.7) id AA25674; Fri, 9 May 97 21:11:38 -0700 From: chad@anasazi.com (Chad R. Larson) Message-Id: <9705100411.AA25674@chad.anasazi.com> Subject: IP aliasing hacks To: freebsd-stable@freebsd.org Date: Fri, 9 May 1997 21:11:37 -0700 (MST) Reply-To: chad@anasazi.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoting: > # From: @(#)netstart 5.9 (Berkeley) 3/30/91 > > # Note that almost all the user-configurable behavior is no longer in > # this file, but rather in /etc/sysconfig. Please check this file > # first before contemplating any changes here. If you do need to change > # this file for some reason, we would like to know about it. Ok, you asked for it... *** sysconfig.old Fri May 9 21:02:27 1997 --- sysconfig.new Fri May 9 21:02:12 1997 *************** *** 95,100 **** --- 95,108 ---- network_interfaces="lo0 ep0" ifconfig_lo0="inet localhost" + + # + # Set a list of network interface aliases. Used (for example) to + # support virtual hosted web servers. You need one entry for each + # interface that has aliases. The interface names are as configured + # above. For example: + # aliases_ed0="10.0.0.10 10.0.0.11" + # # # Set to the list of route add lines for this host. You must have a *** netstart.old Fri May 9 21:06:33 1997 --- netstart.new Fri May 9 21:06:46 1997 *************** *** 46,51 **** --- 46,56 ---- eval ifconfig_args=\$ifconfig_${ifn} ifconfig ${ifn} ${ifconfig_args} ifconfig ${ifn} + eval alias_list=\$aliases_${ifn} + for alias in $alias_list ; do + ifconfig ${ifn} ${alias} alias + echo "aliased $alias" + done done if [ -n "$defaultrouter" -a "x$defaultrouter" != "xNO" ] ; then -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 From owner-freebsd-stable Fri May 9 22:37:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA20030 for stable-outgoing; Fri, 9 May 1997 22:37:48 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA20024 for ; Fri, 9 May 1997 22:37:46 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA18494; Fri, 9 May 1997 22:37:50 -0700 (PDT) To: chad@anasazi.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: IP aliasing hacks In-reply-to: Your message of "Fri, 09 May 1997 21:11:37 PDT." <9705100411.AA25674@chad.anasazi.com> Date: Fri, 09 May 1997 22:37:50 -0700 Message-ID: <18491.863242670@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ok, you asked for it... Heh. This is already implemented. :-) >From the 2.2's /etc/rc.network (was earlier /etc/netstart): # Set up all the network interfaces, calling startup scripts if needed for ifn in ${network_interfaces}; do if [ -e /etc/start_if.${ifn} ]; then . /etc/start_if.${ifn} ${ifn} fi # Do the primary ifconfig if specified eval ifconfig_args=\$ifconfig_${ifn} if [ -n "${ifconfig_args}" ] ; then ifconfig ${ifn} ${ifconfig_args} fi # Check to see if aliases need to be added alias=0 while : do eval ifconfig_args=\$ifconfig_${ifn}_alias${alias} if [ -n "${ifconfig_args}" ]; then ifconfig ${ifn} ${ifconfig_args} alias alias=`expr ${alias} + 1` else break; fi done ... From owner-freebsd-stable Sat May 10 10:34:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA13065 for stable-outgoing; Sat, 10 May 1997 10:34:55 -0700 (PDT) Received: from devsys.jaguNET.com (devsys.jaguNET.com [206.156.208.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA13060 for ; Sat, 10 May 1997 10:34:53 -0700 (PDT) Received: (from jim@localhost) by devsys.jaguNET.com (8.8.5/jag-2.4) id NAA05508 for freebsd-stable@FreeBSD.ORG; Sat, 10 May 1997 13:34:50 -0400 (EDT) From: Jim Jagielski Message-Id: <199705101734.NAA05508@devsys.jaguNET.com> Subject: supfile to go from 2.2.1-REL to 2.2-STABLE To: freebsd-stable@FreeBSD.ORG Date: Sat, 10 May 1997 13:34:50 -0400 (EDT) Reply-To: jim@jaguNET.com X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Could someone point out the location for a supfile to go from 2.2.1-REL to 2.2-STABLE... Certainly a tag of tag=RELENG_2_1_0 can't be right... -- ==================================================================== Jim Jagielski | jaguNET Access Services jim@jaguNET.com | http://www.jaguNET.com/ "Not the Craw... the CRAW!" From owner-freebsd-stable Sat May 10 15:04:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA25905 for stable-outgoing; Sat, 10 May 1997 15:04:11 -0700 (PDT) Received: from mailhost.anasazi.com (mailhost.anasazi.com [138.113.128.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA25900 for ; Sat, 10 May 1997 15:04:08 -0700 (PDT) Received: from chad.anasazi.com by mailhost.anasazi.com (5.65/3.7) id AA17526; Sat, 10 May 97 15:03:34 -0700 Received: by chad.anasazi.com (5.65/3.7) id AA26848; Sat, 10 May 97 15:03:32 -0700 From: chad@anasazi.com (Chad R. Larson) Message-Id: <9705102203.AA26848@chad.anasazi.com> Subject: sendmail debugging To: freebsd-stable@freebsd.org Date: Sat, 10 May 1997 15:03:31 -0700 (MST) Reply-To: chad@anasazi.com X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is it just me? I can't get the -d0 switch to do anything useful. That is: /usr/sbin/sendmail -q30m -bd -d0.1 will emit some information about compiled options and system identity, but then sendmail still detaches from the terminal. It happens with both versions 8.8.3 and 8.8.5 on a FreeBSD 2.1 platform. -crl -- Chad R. Larson (CRL22) Brother, can you paradigm? 602-870-3330 chad@anasazi.com chad@anasaz.UUCP chad@dcfinc.com Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020 From owner-freebsd-stable Sat May 10 16:36:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA00312 for stable-outgoing; Sat, 10 May 1997 16:36:09 -0700 (PDT) Received: from actcom.co.il (root@actcom.co.il [192.114.47.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA00303 for ; Sat, 10 May 1997 16:36:02 -0700 (PDT) Received: from localhost by actcom.co.il with SMTP (8.8.4/actcom-0.1) id BAA03156; Sun, 11 May 1997 01:43:29 +0300 (EET DST) (rfc931-sender: baum@localhost) Date: Sun, 11 May 1997 01:43:28 +0300 (EET DST) From: Alexander Indenbaum To: Jim Jagielski cc: freebsd-stable@FreeBSD.ORG Subject: Re: supfile to go from 2.2.1-REL to 2.2-STABLE In-Reply-To: <199705101734.NAA05508@devsys.jaguNET.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 10 May 1997, Jim Jagielski wrote: > Could someone point out the location for a supfile to go from > 2.2.1-REL to 2.2-STABLE... Certainly a tag of tag=RELENG_2_1_0 > can't be right... > -- RELENG_2_2 is more reasonable tag :{) > ==================================================================== > Jim Jagielski | jaguNET Access Services > jim@jaguNET.com | http://www.jaguNET.com/ > "Not the Craw... the CRAW!" > Alexander Indenbaum baum@actcom.co.il From owner-freebsd-stable Sat May 10 20:54:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA09390 for stable-outgoing; Sat, 10 May 1997 20:54:24 -0700 (PDT) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA09385 for ; Sat, 10 May 1997 20:54:22 -0700 (PDT) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970116) with ESMTP id XAA23218; Sat, 10 May 1997 23:53:07 -0400 (EDT) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id XAA04035; Sat, 10 May 1997 23:53:06 -0400 (EDT) To: chad@anasazi.com cc: freebsd-stable@FreeBSD.ORG From: "Gary Palmer" Subject: Re: INN and mmap() In-reply-to: Your message of "Mon, 05 May 1997 18:07:51 PDT." <9705060107.AA18210@chad.anasazi.com> Date: Sat, 10 May 1997 23:53:05 -0400 Message-ID: <4032.863322785@orion.webspan.net> Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chad R. Larson wrote in message ID <9705060107.AA18210@chad.anasazi.com>: > 2) Is the 2.1 mmap() broken, or is there just a misunderstanding > between the implementation and INN's expectations? Yes to both. > 3) Has mmap() been changed in 2.2 or 3.0? If so, are the changes > slated to be rolled into the RELENG_2_1_0 tree? RELENG_2_1_0 is a dead tree for stuff like this (and I believe the changes were too extensive too). Believe me, from experience, RELENG_2_2 works *MUCH* better for heavily hit servers like news servers. news.webspan.net has been running from the RELENG_2_2 branch for well over 8 months without any kernel problems, and with working mmap() makes things a bit better (some other local tweaks help too :) ) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-stable Sat May 10 21:13:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10007 for stable-outgoing; Sat, 10 May 1997 21:13:46 -0700 (PDT) Received: from ns2.harborcom.net (root@ns2.harborcom.net [206.158.4.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA10000; Sat, 10 May 1997 21:13:43 -0700 (PDT) Received: from localhost (bradley@localhost) by ns2.harborcom.net (8.8.5/8.8.5) with SMTP id AAA06592; Sun, 11 May 1997 00:13:42 -0400 (EDT) Date: Sun, 11 May 1997 00:13:42 -0400 (EDT) From: Bradley Dunn X-Sender: bradley@ns2.harborcom.net To: freebsd-stable@freebsd.org, davidn@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, Revision 1.25.2.8 of src/libexec/ftpd/ftpd.c had the following code added: + if (buf == MAP_FAILED) { MAP_FAILED is not defined in the RELENG_2_2 . Revision 1.15 of src/sys/sys/mman.h needs to be merged into RELENG_2_2. pbd -- Why can't you be a non-conformist like everyone else? From owner-freebsd-stable Sat May 10 21:34:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10861 for stable-outgoing; Sat, 10 May 1997 21:34:39 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10812; Sat, 10 May 1997 21:34:27 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199705110434.VAA10812@hub.freebsd.org> Subject: Re: sendmail debugging To: chad@anasazi.com Date: Sat, 10 May 1997 21:34:27 -0700 (PDT) Cc: freebsd-stable@freebsd.org In-Reply-To: <9705102203.AA26848@chad.anasazi.com> from "Chad R. Larson" at May 10, 97 03:03:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chad R. Larson wrote: > > Is it just me? I can't get the -d0 switch to do anything useful. > > That is: > > /usr/sbin/sendmail -q30m -bd -d0.1 > > will emit some information about compiled options and system identity, > but then sendmail still detaches from the terminal. It happens with > both versions 8.8.3 and 8.8.5 on a FreeBSD 2.1 platform. there are a host of options for the -d switch. to prevent sendmail from disconnecting from the controlling tty use "-d52.5" (from teh bat book p668) jmb From owner-freebsd-stable Sat May 10 21:54:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA11646 for stable-outgoing; Sat, 10 May 1997 21:54:34 -0700 (PDT) Received: from devsys.jaguNET.com (devsys.jaguNET.com [206.156.208.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11641 for ; Sat, 10 May 1997 21:54:31 -0700 (PDT) Received: (from jim@localhost) by devsys.jaguNET.com (8.8.5/jag-2.4) id AAA07535 for freebsd-stable@freebsd.org; Sun, 11 May 1997 00:54:27 -0400 (EDT) From: Jim Jagielski Message-Id: <199705110454.AAA07535@devsys.jaguNET.com> Subject: MAP_FAILED To: freebsd-stable@freebsd.org Date: Sun, 11 May 1997 00:54:27 -0400 (EDT) Reply-To: jim@jaguNET.com X-Mailer: ELM [version 2.4 PL25] Content-Type: text Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk MAP_FAILED needs to be defined somewhere at present... For example, libexec/ftpd/ftpd.c uses it now and since it's not defined any place, *boom*. -- ==================================================================== Jim Jagielski | jaguNET Access Services jim@jaguNET.com | http://www.jaguNET.com/ "Not the Craw... the CRAW!" From owner-freebsd-stable Sat May 10 22:39:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA13363 for stable-outgoing; Sat, 10 May 1997 22:39:45 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA13357; Sat, 10 May 1997 22:39:41 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id XAA20138; Sat, 10 May 1997 23:39:34 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id XAA04640; Sat, 10 May 1997 23:36:49 -0600 (MDT) Date: Sat, 10 May 1997 23:36:48 -0600 (MDT) From: Marc Slemko To: Gary Palmer cc: freebsd-stable@FreeBSD.ORG Subject: Re: INN and mmap() In-Reply-To: <4032.863322785@orion.webspan.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 10 May 1997, Gary Palmer wrote: > Chad R. Larson wrote in message ID > <9705060107.AA18210@chad.anasazi.com>: > > 2) Is the 2.1 mmap() broken, or is there just a misunderstanding > > between the implementation and INN's expectations? > > Yes to both. > > > 3) Has mmap() been changed in 2.2 or 3.0? If so, are the changes > > slated to be rolled into the RELENG_2_1_0 tree? > > RELENG_2_1_0 is a dead tree for stuff like this (and I believe the > changes were too extensive too). Believe me, from experience, > RELENG_2_2 works *MUCH* better for heavily hit servers like news > servers. news.webspan.net has been running from the RELENG_2_2 branch > for well over 8 months without any kernel problems, and with working > mmap() makes things a bit better (some other local tweaks help too :) ) We upgraded a news server from INN 1.4unoff4 + patches running on RELENG_2_1_0 to 1.5.1 running on RELENG_2_2 and I was amazed by how much less memory the new server took. innd took a third of the memory that it did before. Not sure how much of that is due to 1.5.1 vs. 1.4unoff4, but a lot is due to the much better malloc() in 2.2. Only problem we have with that server is that once in a while the profiling clock (aka. "alternate system clock" by systat -v) dies and needs a poke to restart. Isn't a huge deal since I just restart it from the initialization code of a lkm, but it cna be annoying.