From owner-freebsd-stable Sun Aug 1 14:47: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 685C014C9E for ; Sun, 1 Aug 1999 14:46:56 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-207.dialup.rdu.ipass.net [209.170.132.207]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id RAA17017 for ; Sun, 1 Aug 1999 17:46:44 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id RAA11500 for stable@freebsd.org; Sun, 1 Aug 1999 17:49:17 -0400 (EDT) (envelope-from rhh) Date: Sun, 1 Aug 1999 17:49:16 -0400 From: Randall Hopper To: stable@freebsd.org Subject: Code Forge -- FreeBSD beta not available Message-ID: <19990801174916.A11322@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hadn't seen anything on the mailing lists about this yet, and I just noticed... http://www.codeforge.com/ 22 July 1999: C-Forge version 1.3-2 released: "FreeBSD beta now available!" I haven't used this IDE. But I've read some positive reviews. Not too sure how you go about getting this FreeBSD beta though. Their download page still looks Linux-centric (distrib, kernel vers, etc.). Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Aug 1 15:19:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 66D3714BEC for ; Sun, 1 Aug 1999 15:19:33 -0700 (PDT) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-207.dialup.rdu.ipass.net [209.170.132.207]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id SAA20777 for ; Sun, 1 Aug 1999 18:18:09 -0400 (EDT) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id SAA12345 for stable@freebsd.org; Sun, 1 Aug 1999 18:20:42 -0400 (EDT) (envelope-from rhh) Date: Sun, 1 Aug 1999 18:20:42 -0400 From: Randall Hopper To: stable@freebsd.org Subject: Code Forge -- FreeBSD beta now available Message-ID: <19990801182042.A12268@ipass.net> References: <19990801174916.A11322@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990801174916.A11322@ipass.net>; from Randall Hopper on Sun, Aug 01, 1999 at 05:49:16PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Subject: Code Forge -- FreeBSD beta now available s/not/now/ in the Subject line. I've made spelling errors in e-mail, but not one that changes everything. Sorry about that. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 2 14: 8:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from logatome.micronet.fr (logatome-2.francenet.fr [193.149.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 269621505F; Mon, 2 Aug 1999 14:08:08 -0700 (PDT) (envelope-from Sebastien.Gioria@FranceNet.fr) Received: from gioria.dialup.FranceNet.fr (eku28.dialup.francenet.fr [193.149.106.173] (may be forged)) by logatome.micronet.fr (8.8.8/8.8.8) with ESMTP id XAA09202; Mon, 2 Aug 1999 23:05:50 +0200 (CEST) Received: by gioria.dialup.FranceNet.fr (Postfix, from userid 42) id 2CC241FF8A; Mon, 2 Aug 1999 23:07:26 +0200 (CEST) Message-ID: <19990802230726.G23044@FranceNet.fr> Date: Mon, 2 Aug 1999 23:07:26 +0200 From: Sebastien GIORIA To: hackers@FreeBSD.org, stable@FreeBSD.org Subject: Jail syscalls Reply-To: Sebastien GIORIA Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Operating-System: Definitely FreeBSD Function: Security Administrator X-Work-Organization: FranceNet X-Work-Postal-Address: 28 Rue Desaix , 75015 Paris, France, Terre X-Home-Organization: French FreeBSD Documentation Project X-Home-Postal-Address: 32 Rue Baron Le Roy, 75012 Paris, France, Terre X-Operating-System: FreeBSD-STABLE + PAO enabled X-URL-Home: http://www.FreeBSD-fr.org X-URL-Work: http://www.FranceNet.fr Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I'm in the process of evaluating (next month) some box who made the same that jail syscall but this is linux boxes :-( or Solaris boxes. So, If I can make a FreeBSD-STABLE (3.X box) working with jail in the competition, I've got a good point for my boss. We are currently working with some FreeBSD boxes as mail, dns, radius servers and if we can made webserver, this will be a great work for us because we love it. So my question is; Are they some guys who have patchs for a -STABLE box ? This is not a problem if this is not actually supported because the linux boxes are only ALPHA boxes. My process decision is in the next 6 months, so if some guys from core (particuliary PHK; if I remenber this is the responsible of the jail subsystem). Thank for your responses S. -- FranceNet Security Administrator Sebastien.Gioria@FranceNet.fr French FreeBSD Documentation Project gioria@FreeBSD.org Tout FreeBSD en Francais http://www.FreeBSD-fr.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 2 15:25: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.one.net (mail.one.net [206.112.192.107]) by hub.freebsd.org (Postfix) with ESMTP id A220D14F23 for ; Mon, 2 Aug 1999 15:24:54 -0700 (PDT) (envelope-from gmanaugh@one.net) Received: from port-1-42.adsl.one.net ([216.23.20.42] HELO superguy ident: IDENT-NOT-QUERIED [port 24068]) by mail.one.net with SMTP id <41270-5328>; Mon, 2 Aug 1999 18:24:39 -0400 From: "Guy Manaugh" To: Subject: subscribe Date: Mon, 2 Aug 1999 18:24:34 -0400 Message-ID: <000001bedd35$ccb98cb0$7a168d0a@manaugh.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 2 15:53:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 8DFB714FE0; Mon, 2 Aug 1999 15:52:59 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA25513; Mon, 2 Aug 1999 18:54:53 -0400 From: Bill Paul Message-Id: <199908022254.SAA25513@skynet.ctr.columbia.edu> Subject: FYI for those with 3Com 3c905C cards To: current@freebsd.org, stable@freebsd.org Date: Mon, 2 Aug 1999 18:54:52 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3767 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've gotten a couple of reports from people claiming to have trouble with the 3c905C, usually along the lines of "the autonegotiation works and I can bring the card up, but I can't receive or send any packets." (For those who don't know, the 3c905C differes from the 3c905B in that it has a new 3Com XL ASIC revision called the "Tornado," plus has management features including wake on LAN and SMBUS interfaces, and it has a built-in boot ROM with support for BOOTP, DHCP, PXE, and a bunch of other acronyms.) First off, this is not entirely correctly: in the few cases where I've been able to squeeze information out of people, I've found that running tcpdump on the interface shows that the 3c905C does at least receive some traffic, so "can't send or receive any packets" is not entirely correctly. I haven't gotten anyone to do proper transmitter testing. Diagnosing this has been hard, largely due to the fact that I haven't been able to duplicate the problem with my hardware: I've tried a Dell PowerEdge 2300/400 dual PII 400 SMP box, a P200 GW2K box, a 486/66 and my alphastation 200, and in each case I was able to send and receive traffic without any apparent problems. The only peculiarity I encountered was with the PowerEdge system. The two cards I have were sent to me by 3Com; when the first one arrived, I plugged it into one of the primary PCI slots in the Dell (one of the same slots I'd used before with several other cards) and the machine refused to power on. Initially, I thought the card was hosed, and 3Com sent me a second one, which exhibited the same behavior. Finally I discovered that if I put the card in one of the secondary PCI slots (which turns out to be PCI bus 2, connected to PCI bus 0 via a DEC PCI-PCI bridge), the machine would power on fine and the card would work correctly in FreeBSD. (For all you armchair technicians out there, no, it's not a problem with the card drawing too much power or a shorted trace on the card. I don't know what it is, though I suspect some PCI BIOS weirdness.) Today I was experimenting with another machine, a Dell PowerEdge 4300/500 dual PIII 500Mhz system, and I did finally encounter a problem: for some reason, the 3c905C refused to receive certain NFS packets (in particular NFS create requests). I don't know why this happened exactly, however I fixed the problem by modifying the xl driver code to issue individual "reset TX block" and "reset RX block" command after issuing the global reset command in xl_reset(). Now that the transmitter and receiver are reset as part of the card initialization, everything seems to work correctly. I committed this changed to the xl driver in both the current and stable branches today, plus I updated the code at http://www.freebsd.org/~wpaul/3Com. If you have a 3c905C card and have been having trouble getting it to work with FreeBSD, I would appreciate it if you could cvsup to the latest -stable or -current or download the driver from the web server and give it a try. I'm not positive that this will fix all the problems people have been seeing, but I'm very curious to see what effect it has. If you notice any improvements (or not), please let me know at wpaul@skynet.ctr.columbia.edu. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 2 16:56:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id E335514CCA for ; Mon, 2 Aug 1999 16:56:03 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id QAA54406; Mon, 2 Aug 1999 16:50:54 -0700 (PDT) (envelope-from obrien) Message-ID: <19990802165054.A54365@nuxi.com> Date: Mon, 2 Aug 1999 16:50:54 -0700 From: "David O'Brien" To: Oscar Bonilla Cc: "stable@FreeBSD.ORG" Subject: Re: Bison update request Reply-To: obrien@FreeBSD.ORG References: <19990728121656.C420@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kris Kennaway on Thu, Jul 29, 1999 at 09:39:23AM +0930 X-Operating-System: FreeBSD 3.2-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > For what I've read in -current it seems bison is on its way out. > > better use yacc. > > This was stated the other day by David O'Brien as his intention, so it may > not be wise to depend on bison being in current forever. Very correct. I am working hard to figure out why Byacc can't be used to create cc1plus's parser. In fact simply upgrading /usr/src/contrib/bison (which is version 1.25) to version 1.26a causes me the same problem as Byacc. There is a single line I can comment out of vers 1.26a, 1.27, and 1.28 that will allow me to use the newer Bison's to compile -CURRENT's cc1plus. I will either upgrade /usr/src/contrib/bison to 1.28 or remove it completely. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Aug 2 16:57: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 239D314A2D for ; Mon, 2 Aug 1999 16:57:00 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id QAA54434; Mon, 2 Aug 1999 16:53:59 -0700 (PDT) (envelope-from obrien) Message-ID: <19990802165359.B54365@nuxi.com> Date: Mon, 2 Aug 1999 16:53:59 -0700 From: "David O'Brien" To: Dispatcher , Vadim Chekan Cc: stable@FreeBSD.ORG Subject: Re: Bison update request Reply-To: obrien@FreeBSD.ORG References: <379FFFCF.992175D0@gc.lviv.ua> <199907291137.HAA24115@blackhelicopters.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199907291137.HAA24115@blackhelicopters.org>; from Dispatcher on Thu, Jul 29, 1999 at 07:37:27AM -0400 X-Operating-System: FreeBSD 3.2-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bison was used to support gcc, which is the compiler used in 3.x. The > version of gcc 3.2 uses is also old, so we need a matching bison. Close, but not quite. Bison was brought in because gcc-2.7.x (or maybe it was 2.6.x) would not compile with Byacc. Nobody really wanted to maintain Bison in the base tree, thus it hasn't gotten any attention. Bison 1.25 works for ``make world'' and that is suffient for FreeBSD's base needs. It has nothing to do with gcc-2.7.2 (and old version) also requireing an old version of Bison (over just requiring Bison). > -current uses egcs. We can easily use yacc with it, with only a few > changes. If anyone knows the changes, please let me know! :-) > The motivation is: > Yacc has a BSD license, while Bison has a GNU license. Correct. We aim to depend on as few GPL licensed tools for building the system as possible. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 2:13:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from iota.cubes.de (iota.cubes.de [193.30.133.102]) by hub.freebsd.org (Postfix) with ESMTP id 24F6815289 for ; Tue, 3 Aug 1999 02:13:21 -0700 (PDT) (envelope-from Andreas.Stumpf@cubes.de) Received: from cubes.de (gamma.cubes.de [193.30.133.104]) by iota.cubes.de (8.9.3/8.9.3) with ESMTP id LAA12052 for ; Tue, 3 Aug 1999 11:10:04 +0200 Message-ID: <37A6B2C7.D8B818E2@cubes.de> Date: Tue, 03 Aug 1999 11:13:44 +0200 From: Andreas Stumpf Organization: cubes GmbH X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en,de MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: PCMCIA: "Device not configured" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Everybody, I just installed FreeBSD 3.1 on my notebook. My problem is, that the system doesn't access the PCMCIA-Ports. The controller is recognized but any access to the ports is denied with the message "/dev/card0: Device not configured" I've tried a lot to make it work, but you all can guess while reading this posting: without success: - I searched in handbook and FAQ at freebsd.org for any hints - I tried kernels with "device card" configured - I tried kernels without "device card" configured and loading the kernel-module pcic.ko - I compared major number of /dev/card[01]-entry against majors.i386 - I asked an experienced friend (Hi Christoph) Now I don't have any more ideas and have to hope, that anybody else has a solution. This mail is accompanied by the output of dmesg, some useful diagnostic commands and parts of the dmesg-Output from a running Linux on this notebook. ============================================================================== dmesg-Output: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #13: Fri Jul 30 16:24:47 CEST 1999 root@omega.cubes.de:/usr/src/sys/compile/OMEGA Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (120.27-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x1bf real memory = 41943040 (40960K bytes) avail memory = 37941248 (37052K bytes) Preloaded elf kernel "kernel" at 0xf02e0000. DEVFS: ready for devices Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 vga0: rev 0x00 on pci0.17.0 chip1: rev 0xa3 on pci0.18.0 pcic0: rev 0xfe int a irq 255 on pci0.23.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x300 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1031MB (2112768 sectors), 2096 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, iordis acd0: drive speed 689KB/sec, 128KB cache acd0: supported read types: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked ppc0 at 0x278 irq 7 on isa ppc0: SMC FDC37C665GT chipset (EPP/PS2/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Initializing PC-card drivers: ed Intel Pentium detected, installing workaround for F00F bug DEVFS: ready to run IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry IP Filter: initialized. Default = pass all, Logging = enabled changing root device to wd0s1a ============================================================================== Output from some commands: $ ls -l /dev/ca* crw-r--r-- 1 root wheel 50, 0 Jul 30 08:16 /dev/card0 crw-r--r-- 1 root wheel 50, 1 Jul 30 08:16 /dev/card1 ============================================================================== $ pccardc pccardmem pccardc: /dev/card0: Device not configured ============================================================================== $ kldstat Id Refs Address Size Name 1 5 0xf0100000 1de608 kernel 2 1 0xf07d7000 3000 pcic.ko 3 2 0xf07ec000 a000 ibcs2.ko 4 1 0xf07f9000 3000 ibcs2_coff.ko 5 1 0xf07fe000 d000 linux.ko ============================================================================== included in /sys/i386/conf/OMEGA: # PCCARD (PCMCIA) support controller card0 device pcic0 at card? device pcic1 at card? ============================================================================== dmesg from Linux on the same PC: Linux version 2.2.5 (root@omega) (gcc version 2.7.2.3) #3 Sun May 30 12:33:51 MEST 1999 Detected 120275255 Hz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 48.03 BogoMIPS Memory: 38828k/40960k available (1048k kernel code, 408k reserved, 636k data, 40k init) VFS: Diskquotas version dquot_6.4.0 initialized CPU: Intel Pentium 75 - 200 stepping 06 Checking 386/387 coupling... OK, FPU using exception 16 error reporting. Checking 'hlt' instruction... OK. Intel Pentium with F0 0F bug - workaround enabled. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.10 entry at 0xe1f3e PCI: Using configuration type 1 PCI: Probing PCI hardware Linux NET4.0 for Linux 2.2 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0 for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP Initializing RT netlink socket Starting kswapd v 1.5 Detected PS/2 Mouse Port. pty: 256 Unix98 ptys configured Real Time Clock Driver v1.09 RAM disk driver initialized: 16 RAM disks of 20480K size PCI_IDE: unknown IDE controller on PCI bus 00 device 91, VID=1060, DID=0101 PCI_IDE: not 100% native mode: will probe irqs later hda: TOSHIBA MK2101MAN, ATA DISK drive hdc: TOSHIBA CD-ROM XM-1302B, ATAPI CDROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: TOSHIBA MK2101MAN, 2067MB w/128kB Cache, CHS=525/128/63 hdc: ATAPI 4X CD-ROM drive, 128kB Cache Uniform CDROM driver Revision: 2.54 Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 Partition check: hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 > VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 40k freed Adding Swap: 80604k swap-space (priority -1) Serial driver version 4.27 with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Linux PCMCIA Card Services 3.0.9 kernel build: 2.2.5 unknown options: [pci] [cardbus] Intel PCIC probe: Cirrus PD6729 PCI-to-PCMCIA at bus 0 slot 23, port 0x3000, 2 sockets host opts [0]: [ring] [1/5/0] [1/20/0] host opts [1]: [ring] [1/5/0] [1/20/0] ISA irqs (default) = 3,4,5,7,9,10,11,12 polling interval = 1000 ms cs: IO port probe 0x1000-0x17ff: excluding 0x10b8-0x10bf 0x1170-0x1177 0x11f0-0x11f7 0x1220-0x1227 0x1278-0x127f 0x12f8-0x12ff 0x1340-0x1347 0x1370-0x1377 0x1388-0x138f 0x13f0-0x13ff 0x14b8-0x14bf 0x1570-0x1577 0x15f0-0x15f7 0x1678-0x167f 0x16f8-0x16ff 0x1770-0x1777 0x17f0-0x17ff cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x227 0x278-0x27f 0x340-0x347 0x388-0x38f 0x3b0-0x3df 0x408-0x40f 0x480-0x48f 0x4b8-0x4bf 0x4d0-0x4d7 cs: IO port probe 0x0a00-0x0aff: excluding 0xa78-0xa7f 0xaf8-0xaff cs: memory probe 0x0d0000-0x0dffff: clean. eth0: NE2000 Compatible: port 0x300, irq 3, hw_addr 00:00:E8:25:6B:0C lp: driver loaded but no devices found ============================================================================== Thanks in advance for any helping comment! Andreas Stumpf -- ============================================================================== Andreas Stumpf, Ditzingen, Germany Email: Andreas.Stumpf@cubes.de ============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 7:53:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id C856214C29 for ; Tue, 3 Aug 1999 07:51:55 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id IAA13840; Tue, 3 Aug 1999 08:50:09 -0600 (CST) (envelope-from obonilla) Date: Tue, 3 Aug 1999 08:50:03 -0600 From: Oscar Bonilla To: Andreas Stumpf Cc: freebsd-stable@FreeBSD.ORG Subject: Re: PCMCIA: "Device not configured" Message-ID: <19990803085003.A13798@fisicc-ufm.edu> References: <37A6B2C7.D8B818E2@cubes.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <37A6B2C7.D8B818E2@cubes.de>; from Andreas Stumpf on Tue, Aug 03, 1999 at 11:13:44AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 03, 1999 at 11:13:44AM +0200, Andreas Stumpf wrote: > Hi Everybody, > > I just installed FreeBSD 3.1 on my notebook. My problem is, that > the system doesn't access the PCMCIA-Ports. The controller is recognized > but any access to the ports is denied with the message > "/dev/card0: Device not configured" I've tried a lot to make it work, > but you all can guess while reading this posting: without success: > - I searched in handbook and FAQ at freebsd.org for any hints > - I tried kernels with "device card" configured > - I tried kernels without "device card" configured and loading the > kernel-module pcic.ko > - I compared major number of /dev/card[01]-entry against majors.i386 > - I asked an experienced friend (Hi Christoph) > Now I don't have any more ideas and have to hope, that anybody else > has a solution. > Install PAO (http://www.jp.freebsd.org/PAO/) Regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 8:53:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from easeway.com (ns1.easeway.com [209.69.39.1]) by hub.freebsd.org (Postfix) with ESMTP id 0016714E4E for ; Tue, 3 Aug 1999 08:53:14 -0700 (PDT) (envelope-from mwlucas@easeway.com) Received: (from mwlucas@localhost) by easeway.com (8.8.8/8.8.5) id LAA13889 for freebsd-stable@freebsd.org; Tue, 3 Aug 1999 11:23:12 -0400 (EDT) Message-Id: <199908031523.LAA13889@easeway.com> Subject: upgrade to 3.2-stable, ppp stops? To: freebsd-stable@freebsd.org Date: Tue, 3 Aug 1999 11:23:12 -0400 (EDT) From: mwlucas@exceptionet.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, My office proxy server was, until Sunday, a 2.2.8-stable box running ppp for our ISDN net connection. I upgraded to source via cvsup and make aout-to-elf, ran mergemaster. Everything went fine. Userland ppp no longer works, however. My ISDN terminal unit still has the same configuration. I used the same ppp.conf that I had under 2.2.8. When I had problems, I rebuilt ppp.conf from scratch, per the handbook and man page. The terminal unit has a light for the serial line connection, and a light for the outgoing dial attempt. The serial light comes on, but the line activity light remains off. Has anything in ppp changed between 2.2.8 and 3-stable? Any suggestions on where to look? Thanks, ==ml -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 9:40:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 25E9114FFD for ; Tue, 3 Aug 1999 09:40:48 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id RAA42803; Tue, 3 Aug 1999 17:40:41 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id RAA09516; Tue, 3 Aug 1999 17:41:51 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199908031641.RAA09516@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: mwlucas@exceptionet.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: upgrade to 3.2-stable, ppp stops? In-reply-to: Your message of "Tue, 03 Aug 1999 11:23:12 EDT." <199908031523.LAA13889@easeway.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Aug 1999 17:41:51 +0100 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hello, > > My office proxy server was, until Sunday, a 2.2.8-stable box running ppp > for our ISDN net connection. > > I upgraded to source via cvsup and make aout-to-elf, ran mergemaster. > Everything went fine. > > Userland ppp no longer works, however. > > My ISDN terminal unit still has the same configuration. I used the same > ppp.conf that I had under 2.2.8. When I had problems, I rebuilt ppp.conf > from scratch, per the handbook and man page. > > The terminal unit has a light for the serial line connection, and a light > for the outgoing dial attempt. The serial light comes on, but the line > activity light remains off. > > Has anything in ppp changed between 2.2.8 and 3-stable? Any suggestions > on where to look? Lots. How about saying what your log & config files look like. There's info about this sort of thing at http://www.FreeBSD.org/FAQ/userppp.html > Thanks, > ==ml > -- > Michael Lucas | > Exceptionet, Inc. | www.exceptionet.com > "Exceptional Networking" | -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 10:27: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from easeway.com (ns1.easeway.com [209.69.39.1]) by hub.freebsd.org (Postfix) with ESMTP id E575E152E1 for ; Tue, 3 Aug 1999 10:27:00 -0700 (PDT) (envelope-from mwlucas@easeway.com) Received: (from mwlucas@localhost) by easeway.com (8.8.8/8.8.5) id NAA14141; Tue, 3 Aug 1999 13:13:04 -0400 (EDT) Message-Id: <199908031713.NAA14141@easeway.com> Subject: Re: upgrade to 3.2-stable, ppp stops? In-Reply-To: <199908031641.RAA09516@keep.lan.Awfulhak.org> from Brian Somers at "Aug 3, 99 05:41:51 pm" To: brian@FreeBSD.org.uk (Brian Somers) Date: Tue, 3 Aug 1999 13:13:04 -0400 (EDT) Cc: mwlucas@exceptionet.com, freebsd-stable@FreeBSD.ORG From: mwlucas@exceptionet.com X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it turned out to be a loose cable, simply coincident with the make aout-to-elf build. Yet again, a simple posting to -stable was all that was required for me to find and fix the error. Unless, of course, you want me to send-pr that the 2.2-stable to 3.2- stable upgrade loosened my cables. ;) Thanks anyway, ==ml > Lots. How about saying what your log & config files look like. > There's info about this sort of thing at > > http://www.FreeBSD.org/FAQ/userppp.html > > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > > -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 11:10:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 611ED152D2; Tue, 3 Aug 1999 11:10:41 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA84037; Tue, 3 Aug 1999 19:04:20 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id QAA47237; Tue, 3 Aug 1999 16:42:07 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Tue, 3 Aug 1999 16:42:07 +0100 From: Nik Clayton To: Poul-Henning Kamp Cc: stable@freebsd.org, current@freebsd.org Subject: Re: Sitting inside, looking out... Message-ID: <19990803164207.A46171@kilt.nothing-going-on.org> References: <14964.933450146.1@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <14964.933450146.1@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Jul 31, 1999 at 09:42:26PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for completeness; On Sat, Jul 31, 1999 at 09:42:26PM +0200, Poul-Henning Kamp wrote: > 2. Who are the committers anyway ? > ---------------------------------- > > All the noise about Matt Dillons commit bit have generated a lot > of questions about who gets to be committers, so here is a little > insight into the process of appointing a committer: > > Generally we in core operate with three kinds of committers: > > Ports committers > These are people who maintain one or more ports. > > If Asami-san wants to glue a bit on somebody, we will > generally let him. > > Limited scope committers > These are people who maintain some specific bit of the tree, > typically a subsystem they are (co-)authors of. A good example > is the HARP ATM stack, which Mike Spengler is taking care of > (and many thanks for that Mike!) > > Since these people are taken on board with a explicitly > stated limited scope, we are more relaxed about them than > we are about the last category. People have been known > to successfully sneak out from this category and into: > > Committers at large > These are the people who persist in sending well documented > PRs containing correct patches. The only way we have > devised so far for ridding ourselves of this kind of > annoying behaviour is to say "Here! you're a committer, > now close your own PRs!" :-) Doc committers Contributors to the Documentation Project. Generally stick within doc/ and www/, but have been known to wander in to the src/ hierarchy when manual pages need fixing up. There are generally two ways to become a doc committer. The first is the same as "Committers at large". Send enough good quality doc/ PRs and I'll get bored of committing them soon enough. The second is if you are maintaining a particular language translation of the FreeBSD docs (FAQ, Handbook, man pages, and so on). At least, that's my take on it. > NOTE: If somebody can find a sponsor for it, I would really > like to offer an "official FreeBSD Committer sweat-shirt" > to each and every single committer. Luxury cars, free > vacations and suitcases filled with cash would also do. What an excellent idea. How about the FreeBSD Project coming up with the artwork, and then 'licensing' it to each user group? The user groups handle the printing and distribution of the shirts as necessary (with appropriate local modifications as necessary) and probably charge $LOCAL_CURRENCY 1.00 or 2.00 more than the cost of the shirts, which gets punted back to the Project. I know I'd pay. Hmm. "I submitted a PR to FreeBSD, and all I got was this lousy t-shirt." > PS: See you all at the FreeBSD-con in October! http://www.freebsdcon.org/ Absolutely. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 11:17:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 64BC415327 for ; Tue, 3 Aug 1999 11:17:22 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 56123 invoked from network); 3 Aug 1999 18:17:05 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 3 Aug 1999 18:17:05 -0000 Date: Tue, 3 Aug 1999 13:17:05 -0500 (CDT) From: David Scheidt To: Nik Clayton Cc: Poul-Henning Kamp , stable@freebsd.org, current@freebsd.org Subject: Re: Sitting inside, looking out... In-Reply-To: <19990803164207.A46171@kilt.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [moved to -chat] On Tue, 3 Aug 1999, Nik Clayton wrote: > > Hmm. "I submitted a PR to FreeBSD, and all I got was this lousy t-shirt." Wouldn't we rather have "I fixed a PR in FreeBSD..."? David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 11:23:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 37D9B152E0; Tue, 3 Aug 1999 11:23:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA30737; Tue, 3 Aug 1999 20:22:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nik Clayton Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... In-reply-to: Your message of "Tue, 03 Aug 1999 16:42:07 BST." <19990803164207.A46171@kilt.nothing-going-on.org> Date: Tue, 03 Aug 1999 20:22:55 +0200 Message-ID: <30735.933704575@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990803164207.A46171@kilt.nothing-going-on.org>, Nik Clayton writes: >Just for completeness; Yeah, sorry for leaving you gang out , but I didn't want to make it too long, the important thing was to get the three main kinds down, doc committers are pretty much the same story as the other two "limited scope" types. >At least, that's my take on it. > >> NOTE: If somebody can find a sponsor for it, I would really >> like to offer an "official FreeBSD Committer sweat-shirt" >> to each and every single committer. Luxury cars, free >> vacations and suitcases filled with cash would also do. > >How about the FreeBSD Project coming up with the >artwork, and then 'licensing' it to each user group? For it to have significance for the committers, it should be done in such a manner that only the committers get their hands on them. >Hmm. "I submitted a PR to FreeBSD, and all I got was this lousy t-shirt." Now, there's an idea :-) -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 11:29:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from postman.bahianet.com.br (postman.bahianet.com.br [200.223.88.38]) by hub.freebsd.org (Postfix) with ESMTP id 2863B1530E; Tue, 3 Aug 1999 11:29:13 -0700 (PDT) (envelope-from jcarlos@bahianet.com.br) Received: from nop (nop.bahianet.com.br [200.223.88.126]) by postman.bahianet.com.br (8.9.3/8.9.3) with SMTP id PAA17887; Tue, 3 Aug 1999 15:27:58 -0300 (EST) Message-ID: <001101beddde$6448bf80$0400a8c0@bahianet.com.br> From: "Joao Carlos" To: , Subject: IPX/SPX Date: Tue, 3 Aug 1999 15:31:24 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there currently any way to FreeBSD work in an IPX network?? projects about that?? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 11:39:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 926521510E; Tue, 3 Aug 1999 11:39:29 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id NAA81987; Tue, 3 Aug 1999 13:38:18 -0500 (CDT) (envelope-from dan) Date: Tue, 3 Aug 1999 13:38:17 -0500 From: Dan Nelson To: Joao Carlos Cc: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: IPX/SPX Message-ID: <19990803133817.A81939@dan.emsphone.com> References: <001101beddde$6448bf80$0400a8c0@bahianet.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <001101beddde$6448bf80$0400a8c0@bahianet.com.br>; from "Joao Carlos" on Tue Aug 3 15:31:24 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Aug 03), Joao Carlos said: > Is there currently any way to FreeBSD work in an IPX network?? > projects about that?? If you mean a Netware network, there is a loadable module that lets a FreeBSD client access a Netware server using IPX. http://www.butya.kz/~bp/ -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 13:19:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mark.kingsu.ab.ca (mark.kingsu.ab.ca [199.185.113.37]) by hub.freebsd.org (Postfix) with ESMTP id 1DD8414D4E for ; Tue, 3 Aug 1999 13:19:10 -0700 (PDT) (envelope-from bwood@KingsU.ab.ca) Received: from KingsU.ab.ca (kingsnet.kingsu.ab.ca [199.185.113.33]) by mark.kingsu.ab.ca (8.9.3/8.9.2) with ESMTP id OAA90786 for ; Tue, 3 Aug 1999 14:18:45 -0600 (MDT) (envelope-from bwood@KingsU.ab.ca) Message-Id: <199908032018.OAA90786@mark.kingsu.ab.ca> Received: from KINGSNET/SpoolDir by KingsU.ab.ca (Mercury 1.44); 3 Aug 99 14:18:52 -0700 Received: from SpoolDir by KINGSNET (Mercury 1.44); 3 Aug 99 14:18:30 -0700 From: "Broderick Wood" Organization: The King's University College To: freebsd-stable@FreeBSD.ORG Date: Tue, 3 Aug 1999 14:18:23 -0600 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Startup Script X-mailer: Pegasus Mail for Win32 (v3.10) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A while back someone had posted a nifty little script to keep a Daemon running (ie. check if running and restart if not)... Anybody happen to keep a copy? I forgot to ... --------------------------- -BMW- Don't just stand there! Pray something! (bwood@kingsu.ab.ca) Broderick Wood, Director of Information Technology Services The King's University College 9125 - 50 Street Edmonton, Alberta T6B 2H3 (780) 465-8315 (780) 465-3534 (FAX) ><> <>< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 14: 5:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id 7D50B150AD for ; Tue, 3 Aug 1999 14:05:18 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn1031.bossig.com [208.26.241.31]) by revolution.3-cities.com (8.9.3/8.9.3) with ESMTP id OAA24482; Tue, 3 Aug 1999 14:05:04 -0700 (PDT) Message-ID: <37A75AAF.E7E4D29B@3-cities.com> Date: Tue, 03 Aug 1999 14:10:07 -0700 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Broderick Wood Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Startup Script References: <199908032018.OAA90786@mark.kingsu.ab.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Search for it in the archives. It has to be there :-). Kent Broderick Wood wrote: > > A while back someone had posted a nifty little script to keep a > Daemon running (ie. check if running and restart if not)... > > Anybody happen to keep a copy? I forgot to ... > > > > --------------------------- > > -BMW- > > Don't just stand there! Pray something! > > (bwood@kingsu.ab.ca) > Broderick Wood, > Director of Information Technology Services > The King's University College > 9125 - 50 Street > Edmonton, Alberta > T6B 2H3 > (780) 465-8315 > (780) 465-3534 (FAX) > > ><> <>< > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 15:38:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fe040.worldonline.dk (fe040.worldonline.dk [212.54.64.205]) by hub.freebsd.org (Postfix) with SMTP id B728414CE3 for ; Tue, 3 Aug 1999 15:38:55 -0700 (PDT) (envelope-from isl40424@image.dk) Received: (qmail 4724 invoked by uid 0); 3 Aug 1999 22:38:55 -0000 Received: from 38.ppp1-18.image.dk (HELO image.dk) (212.54.74.102) by mail020.worldonline.dk with SMTP; 3 Aug 1999 22:38:55 -0000 Message-ID: <37A76FB6.5514FC3F@image.dk> Date: Wed, 04 Aug 1999 00:39:51 +0200 From: Kim Kruse X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 16: 3:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A74B514F38; Tue, 3 Aug 1999 16:03:27 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA24144; Tue, 3 Aug 1999 16:02:32 -0700 (PDT) (envelope-from dillon) Date: Tue, 3 Aug 1999 16:02:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199908032302.QAA24144@apollo.backplane.com> To: Poul-Henning Kamp Cc: Nik Clayton , stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... References: <30735.933704575@critter.freebsd.dk> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would recommend simply having a 'FreeBSD' T-Shirt. None of this 'committers' or 'core' stuff. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 18: 9:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 79B6815114; Tue, 3 Aug 1999 18:09:44 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA17458; Tue, 3 Aug 1999 18:08:22 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199908040108.SAA17458@freeway.dcfinc.com> Subject: Re: Sitting inside, looking out... In-Reply-To: <199908032302.QAA24144@apollo.backplane.com> from Matthew Dillon at "Aug 3, 99 04:02:32 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 3 Aug 1999 18:08:22 -0700 (MST) Cc: phk@critter.freebsd.dk, nik@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Matthew Dillon wrote: > I would recommend simply having a 'FreeBSD' T-Shirt. None of this > 'committers' or 'core' stuff. > > -Matt > Matthew Dillon > No, I think you missed the point. The T-shirt (or sweatshirt, or baseball cap or whatever) should be special, easily identified as special and available only to the group you're trying to incent/reward. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 18:23: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 943B715159; Tue, 3 Aug 1999 18:23:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA25112; Tue, 3 Aug 1999 18:21:03 -0700 (PDT) (envelope-from dillon) Date: Tue, 3 Aug 1999 18:21:03 -0700 (PDT) From: Matthew Dillon Message-Id: <199908040121.SAA25112@apollo.backplane.com> To: "Chad R. Larson" Cc: phk@critter.freebsd.dk, nik@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... References: <199908040108.SAA17458@freeway.dcfinc.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :As I recall, Matthew Dillon wrote: :> I would recommend simply having a 'FreeBSD' T-Shirt. None of this :> 'committers' or 'core' stuff. :> :> -Matt :> Matthew Dillon :> : :No, I think you missed the point. The T-shirt (or sweatshirt, or :baseball cap or whatever) should be special, easily identified as :special and available only to the group you're trying to :incent/reward. : : -crl :-- :Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? I understand the point. It's a bad idea. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 19:15: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 45FCA151EE; Tue, 3 Aug 1999 19:15:04 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA17617; Tue, 3 Aug 1999 19:14:22 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199908040214.TAA17617@freeway.dcfinc.com> Subject: Re: Sitting inside, looking out... In-Reply-To: <199908040121.SAA25112@apollo.backplane.com> from Matthew Dillon at "Aug 3, 99 06:21:03 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 3 Aug 1999 19:14:22 -0700 (MST) Cc: phk@critter.freebsd.dk, nik@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Matthew Dillon wrote: > :No, I think you missed the point. The T-shirt (or sweatshirt, or > :baseball cap or whatever) should be special, easily identified as > :special and available only to the group you're trying to > :incent/reward. > : > : -crl > :-- > :Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > > I understand the point. It's a bad idea. I disagree. I've used exactly that kind of incentive for my guys a number of times. The most coveted apparel around REZsolutions for a while was the undyed denem shirt with our logo and the phrase "REZsolutions Life Support Team" embroidered above the pocket, that we gave the SysAdm staff after a particularly long, hard implementation. Other departments would say, "Keen, how can I get one of those?" and the answer was, "You can't." The guys are proud to wear them. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Aug 3 19:31:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (adsl-63-193-112-19.dsl.snfc21.pacbell.net [63.193.112.19]) by hub.freebsd.org (Postfix) with ESMTP id 53E8414E2A; Tue, 3 Aug 1999 19:31:44 -0700 (PDT) (envelope-from mike@snafu.adept.org) Received: from localhost (mike@localhost) by snafu.adept.org (8.9.3/8.9.3) with ESMTP id TAA13573; Tue, 3 Aug 1999 19:30:37 -0700 (PDT) Date: Tue, 3 Aug 1999 19:30:37 -0700 (PDT) From: Mike Hoskins To: Matthew Dillon Cc: "Chad R. Larson" , phk@critter.freebsd.dk, nik@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... In-Reply-To: <199908040121.SAA25112@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 3 Aug 1999, Matthew Dillon wrote: > :No, I think you missed the point. The T-shirt (or sweatshirt, or > :baseball cap or whatever) should be special, easily identified as > :special and available only to the group you're trying to > :incent/reward. > I understand the point. It's a bad idea. I understand both points... First, I think everyone seriously involved with development effort(s) deserves a big 'Thank you' and a pat on the back for putting up with a lot of the BS that goes on and spending sleepless nights tackling problems the rest of us can barely imagine solutions to... In this regard, something that makes these individuals 'special' is good... because they are special. Second, by making select individuals 'special' in an attempt to provide incentive, you may do just the opposite... You may alienate individuals by making them feel like they're not a member of the 'chosen few'. I can see both sides of this argument... Which is why I think the best action would be to simply make FreeBSD shirts as available as possible, rather than risking the alienation specialized products could lead to. I wouldn't feel alienated... I'd very gladly pitch in money for shirts, hats, jkh-signature-edition love ewes *wink*, etc... but some people may... *shrug* Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 3:39:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailx.dacom.co.kr (mailx.dacom.co.kr [203.252.3.22]) by hub.freebsd.org (Postfix) with ESMTP id A536F14FF1 for ; Wed, 4 Aug 1999 03:39:27 -0700 (PDT) (envelope-from leesw@prolangs.co.kr) Received: from prolangs.co.kr ([210.124.83.146]) by mailx.dacom.co.kr (8.9.1a/8.9.1) with ESMTP id TAA17357 for ; Wed, 4 Aug 1999 19:34:21 +0900 (KST) Message-ID: <37A895EC.661412BE@prolangs.co.kr> Date: Thu, 05 Aug 1999 04:35:08 +0900 From: Charlie Root Reply-To: leesw@prolangs.co.kr Organization: prolangs X-Mailer: Mozilla 4.61 [ko] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: ko MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 3:41: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailx.dacom.co.kr (mailx.dacom.co.kr [203.252.3.22]) by hub.freebsd.org (Postfix) with ESMTP id D256C14FF1 for ; Wed, 4 Aug 1999 03:40:58 -0700 (PDT) (envelope-from leesw@prolangs.co.kr) Received: from prolangs.co.kr ([210.124.83.146]) by mailx.dacom.co.kr (8.9.1a/8.9.1) with ESMTP id TAA18085 for ; Wed, 4 Aug 1999 19:34:53 +0900 (KST) Message-ID: <37A8960D.B857882D@prolangs.co.kr> Date: Thu, 05 Aug 1999 04:35:41 +0900 From: Charlie Root Reply-To: leesw@prolangs.co.kr Organization: prolangs X-Mailer: Mozilla 4.61 [ko] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: ko MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: ( ) Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 11:14:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id D7D291519E for ; Wed, 4 Aug 1999 11:14:13 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id OAA08842; Wed, 4 Aug 1999 14:25:18 -0400 (EDT) Date: Wed, 4 Aug 1999 14:25:18 -0400 From: Dan Moschuk To: Randall Hopper Cc: stable@FreeBSD.ORG Subject: Re: Code Forge -- FreeBSD beta not available Message-ID: <19990804142518.D8260@trinsec.com> References: <19990801174916.A11322@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990801174916.A11322@ipass.net>; from Randall Hopper on Sun, Aug 01, 1999 at 05:49:16PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | Hadn't seen anything on the mailing lists about this yet, and I just | noticed... | | http://www.codeforge.com/ | | 22 July 1999: | C-Forge version 1.3-2 released: | | "FreeBSD beta now available!" | | I haven't used this IDE. But I've read some positive reviews. | | Not too sure how you go about getting this FreeBSD beta though. Their | download page still looks Linux-centric (distrib, kernel vers, etc.). I had to send them an email to get access to a special download page where the FreeBSD beta was available (although, the Linux version runs fine under linux emulation). It's a neat little IDE, although not neat enough to sway me from vim. Cheers, Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 12: 0: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 3CE6C15405; Wed, 4 Aug 1999 11:59:46 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA66852; Wed, 4 Aug 1999 19:50:28 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id QAA15669; Wed, 4 Aug 1999 16:39:23 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Wed, 4 Aug 1999 16:39:23 +0100 From: Nik Clayton To: Poul-Henning Kamp Cc: Nik Clayton , stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... Message-ID: <19990804163923.A13708@kilt.nothing-going-on.org> Reply-To: chat@freebsd.org References: <19990803164207.A46171@kilt.nothing-going-on.org> <30735.933704575@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <30735.933704575@critter.freebsd.dk>; from Poul-Henning Kamp on Tue, Aug 03, 1999 at 08:22:55PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Reply-to set to -chat] On Tue, Aug 03, 1999 at 08:22:55PM +0200, Poul-Henning Kamp wrote: > In message <19990803164207.A46171@kilt.nothing-going-on.org>, Nik Clayton writes: > >Just for completeness; > > Yeah, sorry for leaving you gang out , but I didn't want to make > it too long, the important thing was to get the three main kinds > down, doc committers are pretty much the same story as the other > two "limited scope" types. Oh, absolutely. But you have to understand that the -doc committers are a rough crowd, and if I don't speak up for them every so they often they start saying rude things about my parentage. What's worse is the translation teams -- they say rude things about my parentage and I can't even understand what they're saying. . . [ Hmm, there's a thought -- could someone who speaks Japanese, Spanish, or one of the other languages we've got translated please check out the different translations of the FAQ, and make sure it doesn't just consist of "Nik's mother wears army boots" repeated again and again. Thanks ] > >At least, that's my take on it. > > > >> NOTE: If somebody can find a sponsor for it, I would really > >> like to offer an "official FreeBSD Committer sweat-shirt" > >> to each and every single committer. Luxury cars, free > >> vacations and suitcases filled with cash would also do. > > > >How about the FreeBSD Project coming up with the > >artwork, and then 'licensing' it to each user group? > > For it to have significance for the committers, it should be done in > such a manner that only the committers get their hands on them. As Matt points out, this has room to backfire. You can see the commit log now; Modified files: CVSROOT avail Log: John Smith is no longer a committer. He's promised to burn his t-shirt in private, and never mention this again. Given that (by and large) the committers are just a subset of a much larger developer base, and that we have developers who, for their own reasons, have declined to become committers, something that's limited to committers is probably not so great. But for patches that closed PRs, absolutely. We could maybe have a generic design that's registered as a copyright (or a trademark, or whatever) with the project, and the project can license this design out to user groups, or individuals, as necessary, and for a small fee. So, if the UK user group wanted to put out 'official UK FreeBSD user group' t-shirts then they can do so, for (say $20 licensing for the design, and $1 per t-shirt). And to pick another example at random, Matt could have a "FreeBSD VM God" t-shirt (and richly deserved it is too). But why stop at t-shirts? FreeBSD boxer shorts? Bra and panties? Anoraks? OK, maybe not the last one. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 13:57:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from asteroid.svib.ru (asteroid.svib.ru [195.151.166.145]) by hub.freebsd.org (Postfix) with ESMTP id C12BD1502F for ; Wed, 4 Aug 1999 13:57:37 -0700 (PDT) (envelope-from tarkhil@asteroid.svib.ru) Received: from shuttle.svib.ru (shuttle.svib.ru [195.151.166.144]) by asteroid.svib.ru (8.9.3/8.9.3) with ESMTP id AAA17475; Thu, 5 Aug 1999 00:55:26 +0400 (MSD) (envelope-from tarkhil@asteroid.svib.ru) Received: (from tarkhil@localhost) by shuttle.svib.ru (8.9.3/8.8.8) id AAA27324; Thu, 5 Aug 1999 00:57:06 +0400 (MSD) (envelope-from tarkhil) From: Alex Povolotsky MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14248.43294.239370.488465@shuttle.svib.ru> Date: Thu, 5 Aug 1999 00:57:02 +0400 (MSD) To: mwlucas@exceptionet.com Cc: stable@FreeBSD.ORG Subject: Net_SSLeay.pm-1.03 In-Reply-To: <199907072009.QAA02936@easeway.com> References: <199907072009.QAA02936@easeway.com> X-Mailer: VM 6.71 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Reply-To: tarkhil@asteroid.svib.ru X-URL: http://freebsd.svib.ru Comments: Hyperbole mail buttons accepted, v04.17. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "mwlucas" == mwlucas writes: mwlucas> Hello, I'm trying to compile Net_SSLeay.pm-1.03 on a mwlucas> 3.2-stable system. After mucking with the various include mwlucas> files, I can get it to this point, where it chokes & dies: mwlucas> prompt#make cc -c -I/usr/local/include/ -DVERSION=\"1.03\" mwlucas> -DXS_VERSION=\"1.03\" -DPIC -fpic mwlucas> warning: this is the location of the previous definition *** mwlucas> Error code 1 mwlucas> Stop. prompt# mwlucas> Any advice? Any success since then? --- Alexander B. Povolotsky [ICQ 18277558] [2:5020/145] [http://freebsd.svib.ru] [tarkhil@asteroid.svib.ru] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 14:25:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail-atm.maine.rr.com (maine.rr.com [204.210.64.1]) by hub.freebsd.org (Postfix) with ESMTP id 8546A1513E for ; Wed, 4 Aug 1999 14:25:32 -0700 (PDT) (envelope-from brunner@maine.rr.com) Received: from computername (dt0b4n1b.maine.rr.com [24.95.12.27]) by mail-atm.maine.rr.com (8.8.7/8.8.8) with SMTP id RAA21009 for ; Wed, 4 Aug 1999 17:24:33 -0400 (EDT) Message-Id: <3.0.6.32.19990804171524.0178fc30@maine.rr.com> X-Sender: brunner@maine.rr.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 04 Aug 1999 17:15:24 -0400 To: stable@FreeBSD.ORG From: Eric Brunner Subject: Problem rebuilding bootstrap libraries (crtbegin.c) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I've 2.2.8 installed on my new vaio laptop, and decided to upgrade to 3.2. The build failed when an unknown pseudo op ".section" is encountered during the rebuild of the bootstrap libraries. The file in question is src/lib/csu/i386 elf/crtbegin.c (sorry, no dash key) The error message is: section attributes are not supported for this target Assembler messages: 68: Error: Unknown pseudo op: '.section' (two keyboard errors in this report, the dash in pseudo op, and the backtick is replaced by an apostrophe). Thanks in advance, Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 16:55:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smyk.apk.net (smyk.apk.net [207.54.158.17]) by hub.freebsd.org (Postfix) with ESMTP id 7008314F73 for ; Wed, 4 Aug 1999 16:55:24 -0700 (PDT) (envelope-from ipswitch@apk.net) Received: from CARBON (stuart.apk.net [207.54.148.235]) by smyk.apk.net (8.9.3/8.9.3/apk.990708) with SMTP id TAA12370 for ; Wed, 4 Aug 1999 19:50:22 -0400 (EDT) From: ipswitch@apk.net (Stuart Krivis) To: stable@FreeBSD.ORG Subject: Re: Sitting inside, looking out... Date: Wed, 04 Aug 1999 23:46:55 GMT Organization: Yoyodyne Propulsion Systems, Inc. Reply-To: ipswitch@apk.net Message-ID: <37aacfcb.6166937@mail.apk.net> References: <19990803164207.A46171@kilt.nothing-going-on.org> <30735.933704575@critter.freebsd.dk> <19990804163923.A13708@kilt.nothing-going-on.org> In-Reply-To: <19990804163923.A13708@kilt.nothing-going-on.org> X-Mailer: Forte Agent 1.5/32.452 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 4 Aug 1999 16:39:23 +0100, Nik Clayton wrote: >But why stop at t-shirts? FreeBSD boxer shorts? Bra and panties? = Anoraks? > >OK, maybe not the last one. Anoraks are just the thing to wear when you go penguin hunting. Yeah, I know, wrong end of the world... if they can make a penguin lovable, then I can stretch the truth a bit too. :-)=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 19: 3:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b169.neo.rr.com [24.93.181.169]) by hub.freebsd.org (Postfix) with ESMTP id A8F16153AA for ; Wed, 4 Aug 1999 19:03:01 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id WAA01247; Wed, 4 Aug 1999 22:02:39 -0400 Date: Wed, 4 Aug 1999 22:02:34 -0400 (EDT) From: Mike Nowlin To: Stuart Krivis Cc: stable@FreeBSD.ORG Subject: Re: Sitting inside, looking out... In-Reply-To: <37aacfcb.6166937@mail.apk.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Anoraks are just the thing to wear when you go penguin hunting. > Or when you go out breaking windows.... Oops -- they're already broken... :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Aug 4 20:33:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mx7.sac.fedex.com (mx7.sac.fedex.com [199.81.194.38]) by hub.freebsd.org (Postfix) with ESMTP id F367914ED1 for ; Wed, 4 Aug 1999 20:32:59 -0700 (PDT) (envelope-from gcr@sa.fedex.com) Received: from mx4.sac.fedex.com (sendmail@mx4.sac.fedex.com [199.82.159.68]) by mx7.sac.fedex.com (8.9.3/8.9.3) with ESMTP id WAA67938 for ; Wed, 4 Aug 1999 22:32:45 -0500 (CDT) (envelope-from gcr@sa.fedex.com) Received: from zippy.sac.fedex.com (gcr@zippy.sac.fedex.com [199.81.28.74]) by mx4.sac.fedex.com (8.9.1/8.9.1) with ESMTP id WAA14366 for ; Wed, 4 Aug 1999 22:32:44 -0500 (CDT) Received: from localhost (gcr@localhost) by zippy.sac.fedex.com (8.9.1/8.9.1) with ESMTP id WAA01381 for ; Wed, 4 Aug 1999 22:32:35 -0500 (CDT) Date: Wed, 4 Aug 1999 22:32:33 -0500 (CDT) From: Greg Rivers To: freebsd-stable@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable subscribe cvs-all To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 1:28: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.energo.ru (ns.energo.ru [195.208.111.1]) by hub.freebsd.org (Postfix) with ESMTP id E39A715253 for ; Thu, 5 Aug 1999 01:28:00 -0700 (PDT) (envelope-from vitaly@energo.ru) Received: from energo.ru ([194.85.102.104]) by mail.energo.ru (8.8.7/8.8.5) with ESMTP id MAA08016 for ; Thu, 5 Aug 1999 12:27:07 +0400 (MSD) Message-ID: <37A94AF7.974B2499@energo.ru> Date: Thu, 05 Aug 1999 12:27:35 +0400 From: "Vitaly A. Kuzmin" Organization: JSC "Lenenergo" X-Mailer: Mozilla 4.61 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: (no subject) Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 4:15:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hackerz.org (hackerz.org [209.31.146.67]) by hub.freebsd.org (Postfix) with ESMTP id 6F50C154C8 for ; Thu, 5 Aug 1999 04:15:16 -0700 (PDT) (envelope-from randy@hackerz.org) Received: from localhost (randy@localhost) by hackerz.org (5.56/) with ESMTP id HAA28538 for ; Thu, 5 Aug 1999 07:41:04 -0400 (EDT) Date: Thu, 5 Aug 1999 07:41:04 -0400 (EDT) From: Charles Quarri To: freebsd-stable@FreeBSD.ORG Subject: /usr/src/contrib/isc-dhcp Broken Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I tried rebuilding last night, and it appears that isc-dhcp is broken, here is the error I got: cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/dhclient/../../contrib/isc-dhcp/common/tables.c cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/dhclient/../../contrib/isc-dhcp/common/tree.c cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sbin/dhclient/../../contrib/isc-dhcp/common/upf.c cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includes -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/usr/include -static -o dhclient clparse.o dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o hash.o icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o socket.o tables.o tree.o upf.o packet.o: In function `assemble_hw_header': packet.o(.text+0x8c): undefined reference to `assemble_ethernet_header' packet.o: In function `decode_hw_header': packet.o(.text+0x1c4): undefined reference to `decode_ethernet_header' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 It probably just an oversight on someones part, but I thought I should let someone know. C. Quarri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 5: 4:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 4416F14CDE for ; Thu, 5 Aug 1999 05:04:47 -0700 (PDT) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id IAA13743; Thu, 5 Aug 1999 08:04:15 -0400 (EDT) Message-Id: <4.1.19990805081442.04d4e5d0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 05 Aug 1999 08:16:29 -0400 To: Charles Quarri From: Mike Tancsa Subject: Re: /usr/src/contrib/isc-dhcp Broken Cc: stable@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:41 AM 8/5/99 , Charles Quarri wrote: >I tried rebuilding last night, and it appears that isc-dhcp is broken, >here is the error I got: > >inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o socket.o >tables.o tree.o upf.o >packet.o: In function `assemble_hw_header': >packet.o(.text+0x8c): undefined reference to `assemble_ethernet_header' >packet.o: In function `decode_hw_header': >packet.o(.text+0x1c4): undefined reference to `decode_ethernet_header' >*** Error code 1 > Yup, Same thing here as well for the past 12hrs or so. I took out the entry in /usr/src/sbin/Makefile so that I could build everything else. I am not that interested in the dhcp client anyways :-) ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 5:31:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from iota.cubes.de (iota.cubes.de [193.30.133.102]) by hub.freebsd.org (Postfix) with ESMTP id 6AE8A151DA for ; Thu, 5 Aug 1999 05:31:03 -0700 (PDT) (envelope-from Andreas.Stumpf@cubes.de) Received: from cubes.de (gamma.cubes.de [193.30.133.104]) by iota.cubes.de (8.9.3/8.9.3) with ESMTP id OAA08247; Thu, 5 Aug 1999 14:27:17 +0200 Message-ID: <37A98401.23FFE5E3@cubes.de> Date: Thu, 05 Aug 1999 14:30:57 +0200 From: Andreas Stumpf Organization: cubes GmbH X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en,de MIME-Version: 1.0 To: Oscar Bonilla Cc: freebsd-stable@FreeBSD.ORG Subject: Re: PCMCIA: "Device not configured" References: <37A6B2C7.D8B818E2@cubes.de> <19990803085003.A13798@fisicc-ufm.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everybody, my problem is solved now, thanks to all who helped. The failure to recognise my PCIC-controller had two reasons: - the IO-address was non-standard at 0x3000 (in words: threethousand) and not configurable in BIOS - with FreeBSD 3.1 I could not configure the driver to use this address I upgraded to FreeBSD 3.2, installed PAO, configured the right address and now it works! First I tried to install the PAO-Version for 3.1 but I can't recommend this to anybody. The original PAO-kernel showed the device pcic0 in the PCI-section of the visual-configuration, so the IO-address couldn't be changed. Worse of all it left a patched source-tree where the kernel- compilation failed with compiler-errors in pccard/pcic.c Regards Andreas Oscar Bonilla wrote: > Install PAO (http://www.jp.freebsd.org/PAO/) -- ============================================================================== Andreas Stumpf, Ditzingen, Germany Email: Andreas.Stumpf@cubes.de ============================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 6:27: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.greatbasin.net (mail.greatbasin.net [207.228.35.39]) by hub.freebsd.org (Postfix) with ESMTP id 3771F154A9 for ; Thu, 5 Aug 1999 06:26:58 -0700 (PDT) (envelope-from dan@jgl.reno.nv.us) Received: from pandora.home (rno-max2-44.gbis.net [207.228.60.172]) by mail.greatbasin.net (8.9.3/8.9.3) with ESMTP id GAA12456; Thu, 5 Aug 1999 06:26:36 -0700 (PDT) Received: from danco (danco.home [10.0.0.2]) by pandora.home (8.9.3/8.9.2) with SMTP id GAA04838; Thu, 5 Aug 1999 06:26:34 -0700 (PDT) (envelope-from dan@jgl.reno.nv.us) Message-ID: <000901bedf46$24058980$0200000a@home> From: "Dan O'Connor" To: "Charles Quarri" , References: Subject: Re: /usr/src/contrib/isc-dhcp Broken Date: Thu, 5 Aug 1999 06:26:33 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last night I installed FBSD 3.2 on our server at work (it was a Win95 machine serving 8 people), updated sources via cvsup, and ran a make world. I got the exact same error message. This was the first time in 9 months of tinkering with FreeBSD that I've had a make world fail, so, needless to say, I was a little freaked. But it's nice to know it's not just me. Hopefully, the source for this will get fixed quickly... --Dan ** The thing I like most about Windows 98 is... ** You can download FreeBSD with it! ----- Original Message ----- From: Charles Quarri To: Sent: Thursday, August 05, 1999 4:41 AM Subject: /usr/src/contrib/isc-dhcp Broken > I tried rebuilding last night, and it appears that isc-dhcp is broken, > here is the error I got: > > cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includ es -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/ usr/include -c /usr/src/sbin/dhclient/../../contrib/isc-dhcp/common/tables.c > cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includ es -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/ usr/include -c /usr/src/sbin/dhclient/../../contrib/isc-dhcp/common/tree.c > cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includ es -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/ usr/include -c /usr/src/sbin/dhclient/../../contrib/isc-dhcp/common/upf.c > cc -nostdinc -O -pipe -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp/includ es -I/usr/src/sbin/dhclient/../../contrib/isc-dhcp -I/usr/obj/usr/src/tmp/ usr/include -static -o dhclient clparse.o dhclient.o alloc.o bpf.o conflex.o convert.o dispatch.o errwarn.o hash.o icmp.o inet.o inet_addr.o memory.o nit.o options.o packet.o parse.o print.o raw.o socket.o tables.o tree.o upf.o > packet.o: In function `assemble_hw_header': > packet.o(.text+0x8c): undefined reference to `assemble_ethernet_header' > packet.o: In function `decode_hw_header': > packet.o(.text+0x1c4): undefined reference to `decode_ethernet_header' > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > It probably just an oversight on someones part, but I thought I > should let someone know. > > C. Quarri > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 8:41:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8B8A014D28 for ; Thu, 5 Aug 1999 08:41:43 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id IAA03114; Thu, 5 Aug 1999 08:41:02 -0700 (PDT) (envelope-from obrien) Message-ID: <19990805084102.A3098@nuxi.com> Date: Thu, 5 Aug 1999 08:41:02 -0700 From: "David O'Brien" To: Mike Tancsa , Charles Quarri Cc: stable@FreeBSD.ORG Subject: Re: /usr/src/contrib/isc-dhcp Broken Reply-To: obrien@FreeBSD.ORG References: <4.1.19990805081442.04d4e5d0@granite.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4.1.19990805081442.04d4e5d0@granite.sentex.ca>; from Mike Tancsa on Thu, Aug 05, 1999 at 08:16:29AM -0400 X-Operating-System: FreeBSD 3.2-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yup, Same thing here as well for the past 12hrs or so. I got pulled away. So all the commits to upgrade `dhclient' spanned more time that I would have liked. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 12:35:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id CC09D1553F for ; Thu, 5 Aug 1999 12:34:58 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 1382 invoked by uid 100); 5 Aug 1999 19:34:57 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Aug 1999 19:34:57 -0000 Date: Thu, 5 Aug 1999 12:34:57 -0700 (PDT) From: Mike Meyer To: stable@freebsd.org Subject: PIIX4? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I came back after a power outage to find my system still down. Checking the hardware docs, I find that a jumper must be set to enable PIIX4, which means the system will power back on. The question is, is PIIX4 something magic that FreeBSD needs to support, and does it? Or does it mean the system just reboot from scratch after an AC failure? Thanx, ; Thu, 5 Aug 1999 12:39:33 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 1414 invoked by uid 100); 5 Aug 1999 19:37:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Aug 1999 19:37:43 -0000 Date: Thu, 5 Aug 1999 12:37:43 -0700 (PDT) From: Mike Meyer To: stable@freebsd.org Subject: Changing from Dangerously Dedicated? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that I have - inadvertantly - changed my main disk from "Dangerously Dedicated" to the DOS-compatable mode. Since this happened after an AC failure at an inopportune moment, I'm not sure whether the problems reported by FSCK are due to that or not. Someone want to know what might - or might not - have been broken by this? Thanx, ; Thu, 5 Aug 1999 12:40:39 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA13484; Thu, 5 Aug 1999 12:34:45 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908051934.MAA13484@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Meyer Cc: stable@freebsd.org Subject: Re: PIIX4? In-reply-to: Your message of "Thu, 05 Aug 1999 12:34:57 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Aug 1999 12:34:45 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I came back after a power outage to find my system still > down. Checking the hardware docs, I find that a jumper must be set to > enable PIIX4, which means the system will power back on. > > The question is, is PIIX4 something magic that FreeBSD needs to > support, and does it? Or does it mean the system just reboot from > scratch after an AC failure? Er, no. "PIIX4" is the Intel name for the PCI/ISA bridge chip, which also contains a pile of other stuff. Your documentation is defective (and FreeBSD already supports the stuff contained in the PIIX4). -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 12:42: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 2395F1551A for ; Thu, 5 Aug 1999 12:42:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA13508; Thu, 5 Aug 1999 12:36:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908051936.MAA13508@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Meyer Cc: stable@freebsd.org Subject: Re: Changing from Dangerously Dedicated? In-reply-to: Your message of "Thu, 05 Aug 1999 12:37:43 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Aug 1999 12:36:42 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems that I have - inadvertantly - changed my main disk from > "Dangerously Dedicated" to the DOS-compatable mode. > > Since this happened after an AC failure at an inopportune moment, I'm > not sure whether the problems reported by FSCK are due to that or not. > Someone want to know what might - or might not - have been broken by > this? If you are at the point where fsck is running, you have not done what you think you have. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 12:53:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from c004.sfo.cp.net (c004-h005.c004.sfo.cp.net [209.228.14.76]) by hub.freebsd.org (Postfix) with SMTP id 315DA14D7C for ; Thu, 5 Aug 1999 12:53:48 -0700 (PDT) (envelope-from jason@intercom.com) Received: (cpmta 1212 invoked from network); 5 Aug 1999 11:34:38 -0700 Received: from shagalicious.com (HELO intercom.com) (206.98.165.250) by smtp.intercom.com with SMTP; 5 Aug 1999 11:34:38 -0700 X-Sent: 5 Aug 1999 18:34:38 GMT Message-ID: <37A9D940.AFF2450B@intercom.com> Date: Thu, 05 Aug 1999 14:34:40 -0400 From: "Jason J. Horton" Organization: Intercom Online Inc. X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.2-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: VINUM Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is vinum stable and useable on 3.x-STABLE branch? -- -Jason J. Horton Moving Target Intercom Online Inc. 212.378.2202 | http://www.intercom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 13:15:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.symmetron.com (mail.symmetron.com [206.239.186.66]) by hub.freebsd.org (Postfix) with ESMTP id BB40015534 for ; Thu, 5 Aug 1999 13:15:18 -0700 (PDT) (envelope-from FreeBSD.lists@symmetron.com) Received: from mail (mail.symmetron.com [127.0.0.1]) by mail.symmetron.com (Netscape Mail Server v2.02) with SMTP id AAA182; Thu, 5 Aug 1999 16:14:53 -0400 Reply-To: From: FreeBSD.lists@symmetron.com (Symmetron's FreeBSD Mailing Lists) To: "Mike Meyer" , Subject: RE: PIIX4? Date: Thu, 5 Aug 1999 16:14:53 -0400 Keywords: FreeBSD-Stable Message-ID: <001a01bedf7f$2d8368e0$42baefce@mail.symmetron.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Importance: Normal In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG check your BIOS configuration... Mine (ASUS motherboard) has an item called "AC Power Loss Restart", it's default is to leave the system off after the power is reapplied. I always change this so that my servers come back on after a power loss. -john --------------- John A. Shue 4000 Legato Road, Suite 600 Fairfax, VA 22033 (703) 591-5559 (703) 591-6337 FAX -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Mike Meyer Sent: Thursday, August 05, 1999 3:35 PM To: stable@freebsd.org Subject: PIIX4? Well, I came back after a power outage to find my system still down. Checking the hardware docs, I find that a jumper must be set to enable PIIX4, which means the system will power back on. The question is, is PIIX4 something magic that FreeBSD needs to support, and does it? Or does it mean the system just reboot from scratch after an AC failure? Thanx, ; Thu, 5 Aug 1999 14:43:20 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 2578 invoked by uid 100); 5 Aug 1999 21:42:16 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Aug 1999 21:42:16 -0000 Date: Thu, 5 Aug 1999 14:42:16 -0700 (PDT) From: Mike Meyer To: stable@freebsd.org Subject: RE: PIIX4? In-Reply-To: <001a01bedf7f$2d8368e0$42baefce@mail.symmetron.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 5 Aug 1999, Symmetron's FreeBSD Mailing Lists wrote: :->check your BIOS configuration... Mine (ASUS motherboard) has an item called "AC Power :->Loss Restart", it's default is to leave the system off after the power is reapplied. I :->always change this so that my servers come back on after a power loss. That was the first thing I did. Couldn't find any such thing. This is a Supermicro S2DGR (or maybe S2DGU) using a 2mb AMI flash BIOS. Thanx, ; Thu, 5 Aug 1999 14:46:57 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Thu, 5 Aug 1999 17:42:36 -0400 Message-ID: From: tcobb@staff.circle.net To: mwm@phone.net Cc: stable@freebsd.org Subject: RE: PIIX4? Date: Thu, 5 Aug 1999 17:42:35 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Supermicro usually has a jumper for PIIX versus BIOS Power save state. Set it to the NON-default setting. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Mike Meyer [mailto:mwm@phone.net] > Sent: Thursday, August 05, 1999 5:42 PM > To: stable@freebsd.org > Subject: RE: PIIX4? > > > On Thu, 5 Aug 1999, Symmetron's FreeBSD Mailing Lists wrote: > :->check your BIOS configuration... Mine (ASUS > motherboard) has an item called "AC Power > :->Loss Restart", it's default is to leave the system off > after the power is reapplied. I > :->always change this so that my servers come back on after > a power loss. > > That was the first thing I did. Couldn't find any such > thing. This is > a Supermicro S2DGR (or maybe S2DGU) using a 2mb AMI flash BIOS. > > Thanx, > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 14:49:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.inficad.com (mail.inficad.com [207.19.74.5]) by hub.freebsd.org (Postfix) with ESMTP id 207231557B for ; Thu, 5 Aug 1999 14:49:27 -0700 (PDT) (envelope-from joeym@inficad.com) Received: from exchsrvr.inficad.com (exchsrvr.inficad.com [208.204.81.4]) by mail.inficad.com (8.9.3/8.9.0) with ESMTP id OAA10087; Thu, 5 Aug 1999 14:48:18 -0700 (MST) Received: by exchsrvr.inficad.com with Internet Mail Service (5.5.1960.3) id ; Thu, 5 Aug 1999 14:48:18 -0700 Message-ID: <813A3F0E2D02D211884900A0C966731EA7B1E9@exchsrvr.inficad.com> From: joeym@inficad.com To: jason@intercom.com, freebsd-stable@FreeBSD.ORG Subject: RE: VINUM Date: Thu, 5 Aug 1999 14:48:16 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd say use vinum in 3.2, but not 3.1.. I had some problems with it in 3.1 Anyway, my backup server is a 90GB vinum stripe. Box uptime is around 70-75 days now, with over 6 terabytes of read/write activity on the 90GB vinum volume. I love vinum. -- Joey Miller UNIX System Administrator Inficad Communications 602.265.4423 / 888.265.4423 -----Original Message----- From: Jason J. Horton [mailto:jason@intercom.com] Sent: Thursday, August 05, 1999 11:35 AM To: freebsd-stable@FreeBSD.ORG Subject: VINUM Is vinum stable and useable on 3.x-STABLE branch? -- -Jason J. Horton Moving Target Intercom Online Inc. 212.378.2202 | http://www.intercom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 15:30:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guru.phone.net (guru.phone.net [209.157.82.120]) by hub.freebsd.org (Postfix) with SMTP id 3E46214D9B for ; Thu, 5 Aug 1999 15:30:21 -0700 (PDT) (envelope-from mwm@phone.net) Received: (qmail 360 invoked by uid 100); 5 Aug 1999 22:29:01 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Aug 1999 22:29:01 -0000 Date: Thu, 5 Aug 1999 15:29:01 -0700 (PDT) From: Mike Meyer To: stable@freebsd.org Subject: RE: PIIX4? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 5 Aug 1999 tcobb@staff.circle.net wrote: :->Supermicro usually has a jumper for PIIX versus BIOS Power save state. :->Set it to the NON-default setting. Well, they only had one such jumper - labeled PIIX4 vs. save PD state. Changing it seemed made the system power back up after I removed power while it was up (no, FreeBSD was *not* running at that time!). Thanx, ; Thu, 5 Aug 1999 15:36:58 -0700 (PDT) (envelope-from kwc@world.std.com) Received: from world.std.com by europe.std.com (STD1.2/BZS-8-1.0) id SAA04728; Thu, 5 Aug 1999 18:36:53 -0400 (EDT) Received: by world.std.com (TheWorld/Spike-2.0) id AA20023; Thu, 5 Aug 1999 18:35:28 -0400 Date: Thu, 5 Aug 1999 18:35:28 -0400 From: kwc@world.std.com (Kenneth W Cochran) Message-Id: <199908052235.AA20023@world.std.com> To: freebsd-stable@freebsd.org Subject: make world/buildworld failures sig11 AMI mainboard Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello... I continue to get failures and/or coredumps while attempting "make world" or "make buildworld" on a system installed from the 3.2 CDs & cvsup'ed to RELENG_3. These occur at seemingly random times/places in the process. I've tried it about 2 dozen times now, & with no success. CVSUP'ing went fine. (I kept the log.) I believe I could almost quote the gcc-sig11 faq chapter & verse... :/ Kernel building seems to work ok, but sometimes it, too, bombs out. I've had this problem with Linux, too, but not lately. (Slackware 4.0 with kernel 2.2.10 & previous...) I think I may have eliminated RAM as the problem, as I've tried varying configurations & amounts & continue to have the problem. (Interesting to see how it works on a RAM-constrained system...) System hardware is as follows: American Megatrends (AMI) Atlas PCI-II mainboard (Series 727) (uses SiS 55xx-series chipset, I think... 5511?) Pentium 133 (P54C) 32mb ram (with parity) Number 9 Motion 771 2mb PCI video (S3-968) DPT PCI SCSI HBA (I forget the model #) with 4mb ecc cache. Seagate ST34573LW in SE mode Seagate ST32550W Plextor PX-32CS SCSI CD-ROM with 1.02 firmware There appears to be nothing in the BIOS setup relating to memory waitstates, etc.; I've tried changing the memory "speed" with no change in results... FBSD has rebooted my system a couple of times, too, & I can't so far trace it... I don't recall Linux ever having done that. I've run Linux for a few years now & various other *ix before that. I've also run BSDI & more recently getting more "serious" with FBSD. System board manufacturer is no help. Have I any options besides replacing this mainboard? -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 15:49: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 91A14155B9 for ; Thu, 5 Aug 1999 15:49:06 -0700 (PDT) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id AAA05651 for ; Fri, 6 Aug 1999 00:17:25 +0200 (CEST) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id AAA22966 for ; Fri, 6 Aug 1999 00:17:24 +0200 Date: Fri, 6 Aug 1999 00:17:23 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: stable@FreeBSD.ORG Subject: Re: PIIX4? In-Reply-To: <001a01bedf7f$2d8368e0$42baefce@mail.symmetron.com> Message-ID: <9908060015040.22964-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > check your BIOS configuration... Mine (ASUS motherboard) has an item called "AC Power > Loss Restart", it's default is to leave the system off after the power is reapplied. I > always change this so that my servers come back on after a power loss. I actually keep it on off. After a power failure I don't also want several circuit breakers to go off due to an enormous power surge. Most ATX-based motherboards are real bad in this respect, sucking kilowatts of power when they get plugged in, and no way to disable this (no real on/off switch). [Would you mind trimming your quotes a little bit the next time?] -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 17:58: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id E22B414BD4 for ; Thu, 5 Aug 1999 17:57:55 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA21903; Fri, 6 Aug 1999 10:26:00 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990806102559:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <199908051934.MAA13484@dingo.cdrom.com> Date: Fri, 06 Aug 1999 10:25:59 +0930 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: PIIX4? Cc: stable@freebsd.org, Mike Meyer Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990806102559:611=_ Content-Type: text/plain; charset=us-ascii On 05-Aug-99 Mike Smith wrote: > > The question is, is PIIX4 something magic that FreeBSD needs to > > support, and does it? Or does it mean the system just reboot from > > scratch after an AC failure? > Er, no. "PIIX4" is the Intel name for the PCI/ISA bridge chip, which > also contains a pile of other stuff. Your documentation is defective > (and FreeBSD already supports the stuff contained in the PIIX4). I think its really telling him that he should change the jumper for power supply to 'PIIX4 Control' instead of 'BIOS Control'.. ie the upshot being turn power on when AC comes on or wait for the power button :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990806102559:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN6oyn1bYW/HEoF9pAQFcUgP9EgxCnjJ4OKIbSJK67eMoAugtVhV/E2RB 0KJAx6w4JGTuEoM26rWblnvm7qC/q69Mprj+0jhy0fJMdJvjfsjVrXtC6TLPBn1h cL3DjBvh77CvccOnCCTn31IoiKn9QtQiLVEm42TrxTNjp/xWhhLwMWfqm0Xa6hRM u+i884g+fqY= =niac -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990806102559:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 18:57:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailgw00.execpc.com (mailgw00.execpc.com [169.207.1.78]) by hub.freebsd.org (Postfix) with ESMTP id A570B14E2B for ; Thu, 5 Aug 1999 18:57:36 -0700 (PDT) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (lakertya-1-105.mdm.mkt.execpc.com [169.207.118.105]) by mailgw00.execpc.com (8.9.1) id UAA06427; Thu, 5 Aug 1999 20:55:58 -0500 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id CC777271; Thu, 5 Aug 1999 20:55:56 -0500 (CDT) To: N Cc: stable@FreeBSD.ORG Subject: Re: PIIX4? In-reply-to: Your message of "Fri, 06 Aug 1999 00:17:23 +0200." <9908060015040.22964-100000@liquid.tpb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Aug 1999 20:55:56 -0500 From: Jon Hamilton Message-Id: <19990806015556.CC777271@woodstock.monkey.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <9908060015040.22964-100000@liquid.tpb.net>, N wrote: } > check your BIOS configuration... Mine (ASUS motherboard) has an item calle } d "AC Power } > Loss Restart", it's default is to leave the system off after the power is r } eapplied. I } > always change this so that my servers come back on after a power loss. } } I actually keep it on off. After a power failure I don't also want } several circuit breakers to go off due to an enormous power surge. I've heard people worry out loud about that at times, but I've never had it happen, and don't know anyone who has had it happen. Besides, your computer draws so little power even at startup that it's really optimizing the wrong thing. OTOH, I do lend some credence to the argument that having the computer remain off when power is reapplied may save you some problems e.g. in a storm, where the power may flash off and back on quickly several times in a short period. In that scenario, you are almost certainly better off just letting the machine sit there powered down. } Most ATX-based motherboards are real bad in this respect, sucking } kilowatts of power when they get plugged in, and no way to disable this } (no real on/off switch). Kilowatts? Hardly. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 19:13:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id C021514E58 for ; Thu, 5 Aug 1999 19:12:47 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA01903; Fri, 6 Aug 1999 11:38:34 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="_=XFMail.1.3.p0.FreeBSD:990806113834:611=_"; micalg=pgp-md5; protocol="application/pgp-signature" In-Reply-To: <19990806015556.CC777271@woodstock.monkey.net> Date: Fri, 06 Aug 1999 11:38:34 +0930 (CST) From: "Daniel O'Connor" To: Jon Hamilton Subject: Re: PIIX4? Cc: stable@FreeBSD.ORG, N Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:990806113834:611=_ Content-Type: text/plain; charset=us-ascii On 06-Aug-99 Jon Hamilton wrote: > that having the computer remain off when power is reapplied may save > you some problems e.g. in a storm, where the power may flash off and > back on quickly several times in a short period. In that scenario, you > are almost certainly better off just letting the machine sit there powered > down. Or get a UPS.. > } Most ATX-based motherboards are real bad in this respect, sucking > } kilowatts of power when they get plugged in, and no way to disable this > } (no real on/off switch). > Kilowatts? Hardly. I don't think they'd even have a high startup current either.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum --_=XFMail.1.3.p0.FreeBSD:990806113834:611=_ Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: 2.6.3ia iQCVAwUBN6pDolbYW/HEoF9pAQEsbAP6AwACs73excvYImMQ+qEqHE9MGSLE8fOY wze23j4Cemj+LPPQVIw+PDjRTx5QzTlcHpNJDQX3+NYBsL9nxlA8RaAa8dsr9WvZ iLHGIhA+0DNcQ5BN5DOweG4zfbEDWA4mku+MlZMF8Y4GlXdTbgdnoDTXLB2VpVyN qOBfw8gtYro= =5Xt2 -----END PGP MESSAGE----- --_=XFMail.1.3.p0.FreeBSD:990806113834:611=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 23:24:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dingo.cdrom.com (castles549.castles.com [208.214.165.113]) by hub.freebsd.org (Postfix) with ESMTP id 7F335150B6 for ; Thu, 5 Aug 1999 23:24:22 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA00400; Thu, 5 Aug 1999 23:19:13 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908060619.XAA00400@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jon Hamilton Cc: N , stable@FreeBSD.ORG Subject: Re: PIIX4? In-reply-to: Your message of "Thu, 05 Aug 1999 20:55:56 CDT." <19990806015556.CC777271@woodstock.monkey.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Aug 1999 23:19:13 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've heard people worry out loud about that at times, but I've never > had it happen, and don't know anyone who has had it happen. Besides, > your computer draws so little power even at startup that it's really > optimizing the wrong thing. OTOH, I do lend some credence to the argument > that having the computer remain off when power is reapplied may save > you some problems e.g. in a storm, where the power may flash off and > back on quickly several times in a short period. In that scenario, you > are almost certainly better off just letting the machine sit there powered > down. If you care about this at all, buy a UPS. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Aug 5 23:39:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 7809B14D20 for ; Thu, 5 Aug 1999 23:39:44 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA84784; Fri, 6 Aug 1999 08:38:04 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199908060638.IAA84784@gratis.grondar.za> To: kwc@world.std.com (Kenneth W Cochran) Cc: freebsd-stable@FreeBSD.ORG Subject: Re: make world/buildworld failures sig11 AMI mainboard Date: Fri, 06 Aug 1999 08:38:04 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > These occur at seemingly random times/places in the process. You have corrupt memory. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 0:53:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from caerbanog.nimlabs.org (caerbanog.nimlabs.org [207.44.173.41]) by hub.freebsd.org (Postfix) with ESMTP id 4BBEA150CE for ; Fri, 6 Aug 1999 00:53:21 -0700 (PDT) (envelope-from nim@caerbanog.nimlabs.org) Received: (from nim@localhost) by caerbanog.nimlabs.org (8.9.3/8.9.3) id FAA73081 for freebsd-stable@freebsd.org; Thu, 5 Aug 1999 05:29:52 -0700 (PDT) (envelope-from nim) Date: Thu, 5 Aug 1999 05:29:51 -0700 From: Nick Martin To: freebsd-stable@freebsd.org Subject: Several Bugs (or maybe Features) Message-ID: <19990805052951.A72463@caerbanog.nimlabs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running FreeBSD 3.2-STABLE (last rebuilt on 990605-ish) and I have a number of problems: a) Time is slow. In 90 seconds of real time, the clock advances about 1 second. This causes a number of problems with scripts, cron, etc, and is very annoying. b) I cannot reboot. When I halt or reboot, does the usual halted by nim, syslog exited on signal 15, then hangs (although, I have only tested it for 3 min, so it may be related to problem a). It does not get to the point of unmounting drives, as next time I start up, it fscks. This is very bad, as I will be away and installed FreeBSD over Linux as I hoped it would be more "fire-and-forget"-able. Not being able to remotly reboot is very very annoying (of course, with luck, I won't need to, but still...) And now, all the relevent info. Running on an AMD K5-75, SCSI card (using the isp driver, and working great), 10/100 ether with the Tulip (de) driver, 32 MB RAM, etc. One point is that I installed and compiled it on a diff computer (Cyrix P200 (150 MHz)), but I recompiled the kernel (not the world) on the AMD. A dmesg that seems to relate to (a): Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 74704326 Hz CPU AMD K5 model 0 (74.70-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x500 Stepping=0 Features=0x3bf Is there some way to adjust the Timecounter? How do I find out what it should be (I do have the motherboard manual around, somewhere, but I'd prefer not to have to look for it) An unrelated question: I am pretty short on space on /usr, and I still have all the aout compatibity stuff there (I upgraded from 3.1-Release). Do I need it? Should I keep it? How do I get rid of it (cleanly) if no to the previous 2? Thanks in advance for your help. -- Nick Martin, nim@nimlabs.org, http://www.nimlabs.org The only thing that should be seperated by color is laundry -Alexis Walters To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 1:16:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D697414F99 for ; Fri, 6 Aug 1999 01:16:24 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id KAA83052; Fri, 6 Aug 1999 10:16:17 +0200 (CEST) (envelope-from des) To: Mike Meyer Cc: stable@FreeBSD.ORG Subject: Re: Changing from Dangerously Dedicated? References: From: Dag-Erling Smorgrav Date: 06 Aug 1999 10:16:16 +0200 In-Reply-To: Mike Meyer's message of "Thu, 5 Aug 1999 12:37:43 -0700 (PDT)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Meyer writes: > Someone want to know what might - or might not - have been broken by > this? A description of your actual problem might come in handy. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 6:20:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 9F0AF14CEF for ; Fri, 6 Aug 1999 06:20:45 -0700 (PDT) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id PAA20861 for ; Fri, 6 Aug 1999 15:20:34 +0200 (CEST) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA24304 for ; Fri, 6 Aug 1999 15:20:33 +0200 Date: Fri, 6 Aug 1999 15:20:33 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: stable@FreeBSD.ORG Subject: Re: PIIX4? In-Reply-To: <19990806015556.CC777271@woodstock.monkey.net> Message-ID: <9908061518170.24294-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jon Hamilton wrote: > } > check your BIOS configuration... Mine (ASUS motherboard) has an item calle > } d "AC Power > } > Loss Restart", it's default is to leave the system off after the power is r > } eapplied. I > } > always change this so that my servers come back on after a power loss. > } I actually keep it on off. After a power failure I don't also want > } several circuit breakers to go off due to an enormous power surge. > I've heard people worry out loud about that at times, but I've never > had it happen, and don't know anyone who has had it happen. Besides, Happened to me. Scheduled power outage in our office building on a Saturday. We powered off all PC's and pulled out all the plugs. In the end, the block with my workstation (a Sun) kept breaking because three Sun 21" monitors did the same soft poweroff trick. > } Most ATX-based motherboards are real bad in this respect, sucking > } kilowatts of power when they get plugged in, and no way to disable this > } (no real on/off switch). > Kilowatts? Hardly. Think a room filled with Gateway PC's :-) -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 6:24:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 4CC6415532 for ; Fri, 6 Aug 1999 06:24:10 -0700 (PDT) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id PAA10135 for ; Fri, 6 Aug 1999 15:23:36 +0200 (CEST) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA24309 for ; Fri, 6 Aug 1999 15:23:35 +0200 Date: Fri, 6 Aug 1999 15:23:35 +0200 (CEST) From: N X-Sender: niels@liquid.tpb.net To: stable@FreeBSD.ORG Subject: Re: PIIX4? In-Reply-To: Message-ID: <9908061520500.24294-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: <9908061520502.24294@liquid.tpb.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel O'Connor wrote: > Or get a UPS.. Please don't believe a UPS doesn't have its own failure modes. In civilised parts of the world one can argue that having one *increases* downtime - if only for the time it takes to re-route power over it at installation time, and no power grid losses after that that would've brought down power in your premises. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 10: 8:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from madcap.apk.net (madcap.apk.net [207.54.158.16]) by hub.freebsd.org (Postfix) with ESMTP id A99F715611 for ; Fri, 6 Aug 1999 10:08:11 -0700 (PDT) (envelope-from awyeah@apk.net) Received: from locutus (awyeah.apk.net [207.54.148.182]) by madcap.apk.net (8.9.3/8.9.3/apk.981124) with SMTP id NAA08489; Fri, 6 Aug 1999 13:03:48 -0400 (EDT) From: "Dave Andrzejewski" To: "N" , Subject: RE: PIIX4? Date: Fri, 6 Aug 1999 13:02:49 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 In-Reply-To: <9908061520500.24294-100000@liquid.tpb.net> Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Actually, it's quite interesting because at my school, we had a couple servers running in the tech office because there was no space left in the server room. The admin's computer was on a UPS, and the 2 servers were on surge suppressors. There was a power-related problem, and it kept "flickering" - turning off and back on rapidly. Well, the 2 servers stayed up just fine, and the admin's workstation kept turning off. It was, of course, a faulty UPS, but still, it kind of makes you think. :-) (Eventually, the power went out long enough for the servers to go down, but, the servers being netware and all, they had no problem.) Dave <===================================================================> Dave Andrzejewski http://awyeah.yourworks.com E-Mail: awyeah@apk.net http://www.yourworks.com AOL/Instant Messager: Seckzy Boi ICQ: 556410 Whois: DA6239 awyeah@IRC - IRC Operator on DALnet - /server sodre.dal.net 7000 ------------------------------------------------------------------- Get paid to surf the web! http://www.alladvantage.com/go.asp?refid=DKF648 <===================================================================> > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of N > Sent: Friday, August 06, 1999 9:24 AM > To: stable@FreeBSD.ORG > Subject: Re: PIIX4? > > > Daniel O'Connor wrote: > > > Or get a UPS.. > > Please don't believe a UPS doesn't have its own failure modes. In > civilised parts of the world one can argue that having one *increases* > downtime - if only for the time it takes to re-route power over it at > installation time, and no power grid losses after that that would've > brought down power in your premises. > > > -- Niels. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.0.2i iQA/AwUBN6sVOMHnYhUtgdpwEQKTMwCgseC6lAyT+Cn3ud0Xja1B053+3DsAnj7O jEqAZG8UO9vqfM9k3zvu+mcW =F+tO -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 10:34:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by hub.freebsd.org (Postfix) with ESMTP id 43CB515620 for ; Fri, 6 Aug 1999 10:34:37 -0700 (PDT) (envelope-from george@dblab.ece.ntua.gr) Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA96997; Fri, 6 Aug 1999 20:34:29 +0300 (EEST) Received: from hawk.dbnet.ece.ntua.gr (hawk.dbnet.ece.ntua.gr [147.102.12.8]) by dblab.ece.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA09427; Fri, 6 Aug 1999 20:34:29 +0300 (EEST) Received: (from george@localhost) by hawk.dbnet.ece.ntua.gr (8.9.3/8.9.2) id UAA02805; Fri, 6 Aug 1999 20:34:29 +0300 (EEST) Date: Fri, 6 Aug 1999 20:34:29 +0300 From: Yiorgos Adamopoulos To: Nick Martin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Several Bugs (or maybe Features) Message-ID: <19990806203429.A2789@dblab.ece.ntua.gr> Reply-To: adamo@dblab.ece.ntua.gr References: <19990805052951.A72463@caerbanog.nimlabs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990805052951.A72463@caerbanog.nimlabs.org>; from Nick Martin on Thu, Aug 05, 1999 at 05:29:51AM -0700 X-Organization: Knowledge and Data Base Systems Laboratory, National Technical University of Athens, GREECE X-URL: http://home.eu.org/~adamo X-Alt-Email: adamo@ieee.org X-Work-Phone: +30-1-772-1-436 X-Work-FAX: +30-1-772-1-442 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 05, 1999 at 05:29:51AM -0700, Nick Martin wrote: > a) Time is slow. In 90 seconds of real time, the clock advances about 1 > b) I cannot reboot. When I halt or reboot, does the usual halted by nim, I think these two indicate problems with your hardware. Otherwise, at least a) should be noted by most of us. I am certain that b) has to do with your hardware, it was happening to me on box with Solaris 2.5.1 and with FreeBSD. -- ieee.org!adamo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 11:44:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.clientlogic.com (ns.clientlogic.com [207.51.66.75]) by hub.freebsd.org (Postfix) with ESMTP id 9FD4A14DAF for ; Fri, 6 Aug 1999 11:44:56 -0700 (PDT) (envelope-from ChrisMic@clientlogic.com) Received: by site0s1 with Internet Mail Service (5.5.2448.0) id ; Fri, 6 Aug 1999 14:44:07 -0400 Message-ID: <6C37EE640B78D2118D2F00A0C90FCB4401105B50@site2s1> From: Christopher Michaels To: jason@intercom.com, freebsd-stable@FreeBSD.ORG Subject: RE: VINUM Date: Fri, 6 Aug 1999 14:46:31 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have nowhere near that much volume on my vinum volume, but i've had absolutely no problems. It even recovered from a power outage w/o any problems at all. -Chris > -----Original Message----- > From: joeym@inficad.com [SMTP:joeym@inficad.com] > Sent: Thursday, August 05, 1999 5:48 PM > To: jason@intercom.com; freebsd-stable@FreeBSD.ORG > Subject: RE: VINUM > > I'd say use vinum in 3.2, but not 3.1.. I had some problems with it in > 3.1 > > Anyway, my backup server is a 90GB vinum stripe. Box uptime is around > 70-75 days now, with over 6 terabytes of read/write activity on the 90GB > vinum volume. I love vinum. > > -- > Joey Miller > UNIX System Administrator > Inficad Communications > 602.265.4423 / 888.265.4423 > > > -----Original Message----- > From: Jason J. Horton [mailto:jason@intercom.com] > Sent: Thursday, August 05, 1999 11:35 AM > To: freebsd-stable@FreeBSD.ORG > Subject: VINUM > > > Is vinum stable and useable on 3.x-STABLE branch? > > -- > -Jason J. Horton > Moving Target > Intercom Online Inc. > 212.378.2202 | http://www.intercom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 12: 6:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.visti.net (P1M2.prime.net.ua [195.64.229.34]) by hub.freebsd.org (Postfix) with ESMTP id BB3E814C7F for ; Fri, 6 Aug 1999 12:06:33 -0700 (PDT) (envelope-from andyo@prime.net.ua) Received: from prime.net.ua (www.4av.free.net [127.0.0.1] (may be forged)) by andyo.prime.net (8.9.3/8.9.3) with ESMTP id WAA00357; Fri, 6 Aug 1999 22:04:32 +0300 (EET DST) Message-ID: <37AB31B6.872AFD8B@prime.net.ua> Date: Fri, 06 Aug 1999 22:04:23 +0300 From: =?koi8-r?Q?=E1=CE=C4=D2=C5=CA=20=F7=2E=20=EF=CC=C5=CA=CE=C9=CB?= (Andy V. Oleynik) Reply-To: andyo@prime.net.ua Organization: =?koi8-r?Q?=ED=2D=E9=CE=C6=CF?= X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) X-Accept-Language: ru, uk, en MIME-Version: 1.0 To: Nick Martin Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Several Bugs (or maybe Features) (looks like known bug , see PR) References: <19990805052951.A72463@caerbanog.nimlabs.org> <19990806203429.A2789@dblab.ece.ntua.gr> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could U pleas send ur dmesg & MBD/CPU specifications? Yiorgos Adamopoulos wrote: > On Thu, Aug 05, 1999 at 05:29:51AM -0700, Nick Martin wrote: > > a) Time is slow. In 90 seconds of real time, the clock advances about 1 > > > b) I cannot reboot. When I halt or reboot, does the usual halted by nim, > > I think these two indicate problems with your hardware. Otherwise, at least a) > should be noted by most of us. > > I am certain that b) has to do with your hardware, it was happening to me on > box with Solaris 2.5.1 and with FreeBSD. > -- > ieee.org!adamo > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Andy V. Oleynik (When U aim for perfection, U discover it's a moving target ö80) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 20:33: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (law-f60.hotmail.com [209.185.131.123]) by hub.freebsd.org (Postfix) with SMTP id 684F914CE5 for ; Fri, 6 Aug 1999 20:32:54 -0700 (PDT) (envelope-from lightningweb@hotmail.com) Received: (qmail 17072 invoked by uid 0); 7 Aug 1999 03:32:41 -0000 Message-ID: <19990807033241.17071.qmail@hotmail.com> Received: from 24.4.2.215 by www.hotmail.com with HTTP; Fri, 06 Aug 1999 20:32:40 PDT X-Originating-IP: [24.4.2.215] From: "lweb Lightningweb" To: freebsd-stable@FreeBSD.ORG Cc: greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Subject: continued crashes with 3.1-Stable Date: Fri, 06 Aug 1999 20:32:40 PDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have not resolved our problem with frequent freezes with our web server. We had two responses to our first mail to this list, but neither one was the solution. The problem is that the server will stop responding to ANYTHING except pings. No telnet, no ssh, no web, no ftp, nothing. Open telnet sessions don't drop, there's just no response to keyboard activity. One suggestion was to fix the "pthreads library," whic we did. The other was: "You may have hardware problems." This server is going down more frequently. Three times so far today. There is no apparant pattern to the crashes. They seem to happen most often during an Mysql database query, but it's happened many times without any queries (a few times just by running "pine" with a large mailbox file). We cannot recreate the crash when we want, it just crashes at random times. We've tried hammering it with web, database queries, and benchamrking programs that slam the RAID array and memory and processors, but it chuggs right along. We have replaced drives in the RAID array, we are now replacing drive caddies. Next step I think will be the RAID controller. I have a strong gut feeling that it is software however. There's nothing to substantiate this, except that that more often than not, the crash happens during an MySQL query. Some (NOT ALL) of the suspect errors that we've recorded from the console during a crash are: (da0:dpt0:0:0:0): Invalidating pack biodone: buffer already done spec_getpages: I/O read failure: (error code=6) size: 32768, resid: 32768, a_count: 32768, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 8 Everyone please take a second look at this and help us brainstorm the problem? I am including a list of the hardware, the original message we sent to the list, and a recent dmesg: FreeBSD 3.1-STABLE #1 Dual-Proc PII 450 512MB RAM DPT PM334UW RAID controller - 16MB RAM - dual bus Ultra Wide - Six 9.1GB Quantum VikingII SCSI3 U2W drives - Three drives per bus, RAID5, one drive is hot-spare Intel EtherExpress Pro 10/100B Ethernet TOSHIBA CD-ROM XM-6201TA -------------- I've recently had the job of system administration dumped in my lap. I'm looking forward to getting on top of it, but I'm a little behind the 8-ball right now. If my subject matter varies too far from the allowed context of this list, please don't flame me too badly. Background: We are running a dual PII 450 system with a 45 gig raid array, controlled by a DPT PM334. The O/S: FreeBSD 3.1-STABLE #1 For several months this has been rock solid. However, in the past three weeks, we've had a number of crashes, most of which seem to be related to mysql queries. The system would be totally unresponsive to ssh/telnet and web, but would still return pings. The server is colocated at our ISP, so it's been tricky to track down the exact 'on screen' console errors. Today, shortly after we upgraded our mysql version, I did see the error. (da0:dpt0:0:0:0): Invalidating Pack (da0:dpt0:0:0:0): Invalidating Pack devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)! biodone: buffer already done (da0:dpt0:0:0:0): Read (10). CDB: 28 0 3 87 33 1f 0 0 80 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:20,0 (da0:dpt0:0:0:0): Invalid command operation code devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)! biodone: buffer already done Followed by a complete system freeze, including the console. Some hunting and searching has led us to believe that we are encountering a driver failure and that we should bring the OS back to -stable. As I said, I haven't done this before, so I'm a little anxious. Before I take that step, I would be very greatful to hear some input from those who surely know more about this than I do. Is bringing the system back to -stable likely to correct our problem? Am I missing some indicator in the error above? Has someone else encountered similar trouble (and found a fix?) I'll be happy to take replies in private e-mail if this is off topic. Any help would be great. Thanks, Jeremy _______________________________________________________________ Get Free Email and Do More On The Web. Visit http://www.msn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 21:20:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id BAFCC14CB9 for ; Fri, 6 Aug 1999 21:20:30 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Sat, 7 Aug 1999 00:15:39 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> From: tcobb@staff.circle.net To: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG Cc: greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Subject: RE: continued crashes with 3.1-Stable Date: Sat, 7 Aug 1999 00:15:38 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the problem is the SMP. I've been having frequent freezes with SMP under heavy webserver load with 3.2-R, and 3.2-S. I'm unfortunately led to believe that FreeBSD SMP is just not ready for primetime. Too bad the $$ we blew on a dual PIII-550 box. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: lweb Lightningweb [mailto:lightningweb@hotmail.com] > Sent: Friday, August 06, 1999 11:33 PM > To: freebsd-stable@FreeBSD.ORG > Cc: greg@lightningweb.com; jeremy@lightningweb.com; > keith@lightningweb.com; criter@lightningweb.com > Subject: continued crashes with 3.1-Stable > > > We have not resolved our problem with frequent freezes with > our web server. > We had two responses to our first mail to this list, but > neither one was the > solution. The problem is that the server will stop > responding to ANYTHING > except pings. No telnet, no ssh, no web, no ftp, nothing. > Open telnet > sessions don't drop, there's just no response to keyboard activity. > > One suggestion was to fix the "pthreads library," whic we > did. The other > was: "You may have hardware problems." > > This server is going down more frequently. Three times so > far today. There > is no apparant pattern to the crashes. They seem to happen > most often > during an Mysql database query, but it's happened many > times without any > queries (a few times just by running "pine" with a large > mailbox file). > > We cannot recreate the crash when we want, it just crashes > at random times. > We've tried hammering it with web, database queries, and > benchamrking > programs that slam the RAID array and memory and > processors, but it chuggs > right along. > > We have replaced drives in the RAID array, we are now > replacing drive > caddies. Next step I think will be the RAID controller. I > have a strong > gut feeling that it is software however. There's nothing > to substantiate > this, except that that more often than not, the crash > happens during an > MySQL query. > > Some (NOT ALL) of the suspect errors that we've recorded > from the console > during a crash are: > > (da0:dpt0:0:0:0): Invalidating pack > biodone: buffer already done > spec_getpages: I/O read failure: (error code=6) > size: 32768, resid: 32768, a_count: 32768, valid: 0x0 > nread: 0, reqpage: 0, pindex: 0, pcount: 8 > > > Everyone please take a second look at this and help us > brainstorm the > problem? I am including a list of the hardware, the > original message we > sent to the list, and a recent dmesg: > > FreeBSD 3.1-STABLE #1 > Dual-Proc PII 450 > 512MB RAM > DPT PM334UW RAID controller > - 16MB RAM > - dual bus Ultra Wide > - Six 9.1GB Quantum VikingII SCSI3 U2W drives > - Three drives per bus, RAID5, one drive is hot-spare > Intel EtherExpress Pro 10/100B Ethernet > TOSHIBA CD-ROM XM-6201TA > > > -------------- > I've recently had the job of system administration dumped > in my lap. I'm > looking forward to getting on top of it, but I'm a little > behind the 8-ball > right now. If my subject matter varies too far from the > allowed context of > this list, please don't flame me too badly. > > Background: We are running a dual PII 450 system with a 45 > gig raid array, > controlled by a DPT PM334. > > The O/S: FreeBSD 3.1-STABLE #1 > > For several months this has been rock solid. However, in > the past three > weeks, we've had a number of crashes, most of which seem to > be related to > mysql queries. The system would be totally unresponsive to > ssh/telnet and > web, but would still return pings. > > The server is colocated at our ISP, so it's been tricky to > track down the > exact 'on screen' console errors. Today, shortly after we > upgraded our > mysql version, I did see the error. > > > (da0:dpt0:0:0:0): Invalidating Pack > (da0:dpt0:0:0:0): Invalidating Pack > devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)! > biodone: buffer already done > (da0:dpt0:0:0:0): Read (10). CDB: 28 0 3 87 33 1f 0 0 80 0 > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:20,0 > (da0:dpt0:0:0:0): Invalid command operation code > devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)! > biodone: buffer already done > > > Followed by a complete system freeze, including the console. > > Some hunting and searching has led us to believe that we > are encountering a > driver failure and that we should bring the OS back to -stable. > > As I said, I haven't done this before, so I'm a little > anxious. Before I > take that step, I would be very greatful to hear some input > from those who > surely know more about this than I do. > > Is bringing the system back to -stable likely to correct > our problem? Am I > missing some indicator in the error above? Has someone > else encountered > similar trouble (and found a fix?) > > I'll be happy to take replies in private e-mail if this is > off topic. > > Any help would be great. > > Thanks, > Jeremy > > > _______________________________________________________________ > Get Free Email and Do More On The Web. Visit http://www.msn.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 22: 0:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.atl.bellsouth.net (mail0.atl.bellsouth.net [205.152.0.27]) by hub.freebsd.org (Postfix) with ESMTP id B33C814CE5 for ; Fri, 6 Aug 1999 22:00:35 -0700 (PDT) (envelope-from wghicks@bellsouth.net) Received: from wghicks.bellsouth.net (host-209-214-65-122.atl.bellsouth.net [209.214.65.122]) by mail0.atl.bellsouth.net (3.3.0/8.9.3) with ESMTP id AAA24843; Sat, 7 Aug 1999 00:53:37 -0400 (EDT) Received: from wghicks.bellsouth.net (wghicks@localhost [127.0.0.1]) by wghicks.bellsouth.net (8.9.3/8.9.2) with ESMTP id AAA01918; Sat, 7 Aug 1999 00:57:48 -0400 (EDT) (envelope-from wghicks@wghicks.bellsouth.net) Message-Id: <199908070457.AAA01918@bellsouth.net> To: "lweb Lightningweb" Cc: freebsd-stable@freebsd.org, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com, wghicks@wghicks.bellsouth.net Subject: Re: continued crashes with 3.1-Stable In-reply-to: Your message of "Fri, 06 Aug 1999 20:32:40 PDT." <19990807033241.17071.qmail@hotmail.com> Date: Sat, 07 Aug 1999 00:57:48 -0400 From: W Gerald Hicks Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Uh... If you are running 3.1 then you aren't "tracking stable". :-) I'd certainly recommend that as a prudent course for production systems. Some would argue that freezing on a particular snapshot is the best strategy for maintaining stability for "production systems". I believe that a complete strategy includes monitoring the activity on the stable mailing lists *and* watching the updates to software installed from the ports systems. It's nice to have a few spare machines for building and testing prior to production deployment. Larger installations can benefit by having a local FreeBSD mirror (CVSup/WWW/FTP). Good Luck, Jerry Hicks wghicks@bellsouth.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Aug 6 22:33: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 3832D14D63 for ; Fri, 6 Aug 1999 22:33:05 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA02605; Fri, 6 Aug 1999 22:31:38 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: tcobb@staff.circle.net Cc: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Subject: Re: continued crashes with 3.1-Stable In-reply-to: Your message of "Sat, 07 Aug 1999 00:15:38 EDT." <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> Date: Fri, 06 Aug 1999 22:31:38 -0700 Message-ID: <2602.934003898@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think the problem is the SMP. I've been having frequent > freezes with SMP under heavy webserver load with 3.2-R, > and 3.2-S. I'm unfortunately led to believe that FreeBSD I wonder why this doesn't happen to Yahoo's SMP boxes then. They run -stable and would be screaming blue murder if their webservers were doing the same thing. So, for that matter, would Hotmail. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 0:41:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cr575310-a.shprd1.on.wave.home.com (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with SMTP id 6147114F32 for ; Sat, 7 Aug 1999 00:41:22 -0700 (PDT) (envelope-from dark@idiotswitch.org) Received: (qmail 75747 invoked from network); 7 Aug 1999 07:39:29 -0000 Received: from a11.idiotswitch.org (10.0.0.11) by a1.idiotswitch.org with SMTP; 7 Aug 1999 07:39:29 -0000 From: Rod Taylor To: jkh@zippy.cdrom.com, freebsd-stable@freebsd.org Subject: Re: continued crashes with 3.1-Stable Date: Sat, 7 Aug 1999 03:39:14 -0400 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain References: <2602.934003898@localhost> MIME-Version: 1.0 Message-Id: <99080703410000.01685@a11.idiotswitch.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 07 Aug 1999, Jordan K. Hubbard wrote: > > I think the problem is the SMP. I've been having frequent > > freezes with SMP under heavy webserver load with 3.2-R, > > and 3.2-S. I'm unfortunately led to believe that FreeBSD > > I wonder why this doesn't happen to Yahoo's SMP boxes then. > They run -stable and would be screaming blue murder if their > webservers were doing the same thing. So, for that matter, > would Hotmail. > Perhaps someone should try to find out what hardware on their systems works. Is it possible that FreeBSD supports one SMP mobo brand better than others? -- Documentation is the castor oil of programming. -- Rod Taylor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 1: 3:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from xl2.cscd.lviv.ua (xl2.cscd.lviv.ua [195.5.56.1]) by hub.freebsd.org (Postfix) with ESMTP id 8DC6914DC6 for ; Sat, 7 Aug 1999 01:03:32 -0700 (PDT) (envelope-from vadim@gc.lviv.ua) Received: from extra.gc.lviv.ua (extra.gc.lviv.ua [195.5.56.19]) by xl2.cscd.lviv.ua (8.9.1a/8.9.1) with ESMTP id LAA22195 for ; Sat, 7 Aug 1999 11:13:07 +0300 (EEST) Received: from gate.gc.lviv.ua (gate.gc.lviv.ua [192.168.168.18]) by extra.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id PAA23944 for ; Fri, 6 Aug 1999 15:45:11 +0300 (EEST) Received: from gc.lviv.ua (intra.lviv.gc.com.ua [192.168.1.93]) by gate.gc.lviv.ua (8.9.3/8.9.3) with ESMTP id PAA99080 for ; Fri, 6 Aug 1999 15:45:10 +0300 (EEST) Message-ID: <37AAD7A1.810A8BFE@gc.lviv.ua> Date: Fri, 06 Aug 1999 15:40:01 +0300 From: Vadim Chekan Organization: Galitsky Kontrakty X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: Several Bugs (or maybe Features) References: <19990805052951.A72463@caerbanog.nimlabs.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Martin wrote: > > I am running FreeBSD 3.2-STABLE (last rebuilt on 990605-ish) and I have > a number of problems: > > a) Time is slow. In 90 seconds of real time, the clock advances about 1 I got the same problem on my HP Vectra XU PPro200. ========================================================================= Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #0: Mon Apr 12 12:06:07 EEST 1999 vadim@gate.gc.lviv.ua:/usr/src/sys/compile/GATE.3 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 171775530 Hz CPU: Pentium Pro (171.78-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff real memory = 67108864 (65536K bytes) avail memory = 62128128 (60672K bytes) ========================================================================= but on the same mashine after reboot: ========================================================================= Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-STABLE #0: Mon Apr 12 12:06:07 EEST 1999 vadim@gate.gc.lviv.ua:/usr/src/sys/compile/GATE.3 Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199739577 Hz CPU: Pentium Pro (199.74-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff real memory = 67108864 (65536K bytes) avail memory = 62128128 (60672K bytes) ========================================================================= > > A dmesg that seems to relate to (a): > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 74704326 Hz > CPU AMD K5 model 0 (74.70-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x500 Stepping=0 > Features=0x3bf > Vadim Chekan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 5:32:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 694C014D0B; Sat, 7 Aug 1999 05:32:47 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Sat, 7 Aug 1999 08:28:11 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B3FB9@FREYA> From: tcobb@staff.circle.net To: jkh@zippy.cdrom.com, freebsd-smp@freebsd.org Cc: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG Subject: RE: continued crashes with 3.1-Stable Date: Sat, 7 Aug 1999 08:28:10 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wonder why this is the case, too. However, there have been a series of reports of crashes and freezes in the 3.2 and 4.0 series that have gone unresolved and, in fact, unresponded. I'd like to be able to use FreeBSD in an SMP environment, but it just isn't stable on the box we've built (Supermicro P6DBU, 1GB ECC RAM, dual PIII 550, DPT RAID). Unfortunately, our hosting customer who is running a high-end e-commerce site on this machine isn't excited about being a testbed, they want a solution that works and stays working. --- Our issue may be related to the large memory config, but I'm not getting panics, just freezes, so it is tough to tell. If anyone has any suggestions, I'd love to hear them was I have to get them a working solution in place before next week or I lose this business. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Jordan K. Hubbard [mailto:jkh@zippy.cdrom.com] > Sent: Saturday, August 07, 1999 1:32 AM > To: tcobb@staff.circle.net > Cc: lightningweb@hotmail.com; freebsd-stable@FreeBSD.ORG; > greg@lightningweb.com; jeremy@lightningweb.com; > keith@lightningweb.com; > criter@lightningweb.com > Subject: Re: continued crashes with 3.1-Stable > > > > I think the problem is the SMP. I've been having frequent > > freezes with SMP under heavy webserver load with 3.2-R, > > and 3.2-S. I'm unfortunately led to believe that FreeBSD > > I wonder why this doesn't happen to Yahoo's SMP boxes then. > They run -stable and would be screaming blue murder if their > webservers were doing the same thing. So, for that matter, > would Hotmail. > > - Jordan > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 5:53:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from corwin.nall.com (corwin.nall.com [216.30.44.163]) by hub.freebsd.org (Postfix) with ESMTP id 4724214DC1 for ; Sat, 7 Aug 1999 05:53:41 -0700 (PDT) (envelope-from joe@nall.com) Received: from nall.com (localhost [127.0.0.1]) by corwin.nall.com with ESMTP (8.7.1/8.7.1) id HAA08252; Sat, 7 Aug 1999 07:52:03 -0500 (CDT) Message-ID: <37AC2BF2.C4C60F1E@nall.com> Date: Sat, 07 Aug 1999 07:52:02 -0500 From: Joe Nall Organization: Nall Design Works X-Mailer: Mozilla 4.6 [en] (X11; I; HP-UX B.10.26 9000/770) X-Accept-Language: en MIME-Version: 1.0 To: lweb Lightningweb Cc: freebsd-stable@FreeBSD.ORG Subject: Re: continued crashes with 3.1-Stable References: <19990807033241.17071.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG lweb Lightningweb wrote: > > One suggestion was to fix the "pthreads library," whic we did. The other > was: "You may have hardware problems." > ... > We have replaced drives in the RAID array, we are now replacing drive > caddies. Next step I think will be the RAID controller. I have a strong > gut feeling that it is software however. There's nothing to substantiate > this, except that that more often than not, the crash happens during an > MySQL query. > ... > (da0:dpt0:0:0:0): Invalidating pack > biodone: buffer already done > spec_getpages: I/O read failure: (error code=6) > size: 32768, resid: 32768, a_count: 32768, valid: 0x0 > nread: 0, reqpage: 0, pindex: 0, pcount: 8 > > Everyone please take a second look at this and help us brainstorm the > problem? I am including a list of the hardware, the original message we > sent to the list, and a recent dmesg: > > FreeBSD 3.1-STABLE #1 > Dual-Proc PII 450 > 512MB RAM > DPT PM334UW RAID controller > - 16MB RAM > - dual bus Ultra Wide > - Six 9.1GB Quantum VikingII SCSI3 U2W drives > - Three drives per bus, RAID5, one drive is hot-spare > Intel EtherExpress Pro 10/100B Ethernet > TOSHIBA CD-ROM XM-6201TA Don't discount the hardware problem response. We use big (200GB+) Winchester Systems raid arrays on production HP-UX servers at work. These boxes have a custom, modified OS that we were blaming for random, very painful crashes with occasional data corruption on a JFS filesystem. On of the symptoms of these crashes were the lack of crash dumps. Two week ago we found out that the firmware installed in the dual redundant controllers (nothing but the best :) had known problems with similar symptoms to ours and we should upgrade. The lack of crash dump should have been a clue earlier that there were disk problems. The "Invalidating pack" error comes from the SCSI CAM driver in "src/sys/cam/scsi/scsi_da.c" and occurs when there has been a catastrophic error (quoting from the code). The error returned from the driver is ENXIO. It appears that your DPT is dropping a SCSI LUN off line. So far my FreeBSD servers have been exactly as reliable as my hardware. Good Luck, Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 11:36:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from p1fed3.frb.org (p1fed3.frb.org [151.198.183.196]) by hub.freebsd.org (Postfix) with ESMTP id 8E9CF14EA8 for ; Sat, 7 Aug 1999 11:36:11 -0700 (PDT) (envelope-from seth@freebie.dp.ny.frb.org) Received: by p1fed3.frb.org; id OAA01335; Sat, 7 Aug 1999 14:35:13 -0400 (EDT) Received: from p1pmdf.p1fw.frb.org(192.168.11.8) by p1fed3.frb.org via smap (3.2) id xma001326; Sat, 7 Aug 99 14:34:52 -0400 Date: Sat, 07 Aug 1999 14:34:49 -0400 (EDT) From: Seth Subject: RE: continued crashes with 3.1-Stable In-reply-to: <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> To: tcobb@staff.circle.net Cc: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Have to disagree. 3.1-R had some problems. 3.2-S works flawlessly, even under heavy load (big disk I/O and >24 system load averages). This is a dual Xeon 450, scsi disks off an adaptec 7890, 384 megs RAM. Some things you didn't mention -- what was the date of your last build, and why haven't you gone to 3.2-S yet? SB On Sat, 7 Aug 1999 tcobb@staff.circle.net wrote: > I think the problem is the SMP. I've been having frequent > freezes with SMP under heavy webserver load with 3.2-R, > and 3.2-S. I'm unfortunately led to believe that FreeBSD > SMP is just not ready for primetime. Too bad the $$ we blew > on a dual PIII-550 box. > > -Troy Cobb > Circle Net, Inc. > http://www.circle.net > > > -----Original Message----- > > From: lweb Lightningweb [mailto:lightningweb@hotmail.com] > > Sent: Friday, August 06, 1999 11:33 PM > > To: freebsd-stable@FreeBSD.ORG > > Cc: greg@lightningweb.com; jeremy@lightningweb.com; > > keith@lightningweb.com; criter@lightningweb.com > > Subject: continued crashes with 3.1-Stable > > > > > > We have not resolved our problem with frequent freezes with > > our web server. > > We had two responses to our first mail to this list, but > > neither one was the > > solution. The problem is that the server will stop > > responding to ANYTHING > > except pings. No telnet, no ssh, no web, no ftp, nothing. > > Open telnet > > sessions don't drop, there's just no response to keyboard activity. > > > > One suggestion was to fix the "pthreads library," whic we > > did. The other > > was: "You may have hardware problems." > > > > This server is going down more frequently. Three times so > > far today. There > > is no apparant pattern to the crashes. They seem to happen > > most often > > during an Mysql database query, but it's happened many > > times without any > > queries (a few times just by running "pine" with a large > > mailbox file). > > > > We cannot recreate the crash when we want, it just crashes > > at random times. > > We've tried hammering it with web, database queries, and > > benchamrking > > programs that slam the RAID array and memory and > > processors, but it chuggs > > right along. > > > > We have replaced drives in the RAID array, we are now > > replacing drive > > caddies. Next step I think will be the RAID controller. I > > have a strong > > gut feeling that it is software however. There's nothing > > to substantiate > > this, except that that more often than not, the crash > > happens during an > > MySQL query. > > > > Some (NOT ALL) of the suspect errors that we've recorded > > from the console > > during a crash are: > > > > (da0:dpt0:0:0:0): Invalidating pack > > biodone: buffer already done > > spec_getpages: I/O read failure: (error code=6) > > size: 32768, resid: 32768, a_count: 32768, valid: 0x0 > > nread: 0, reqpage: 0, pindex: 0, pcount: 8 > > > > > > Everyone please take a second look at this and help us > > brainstorm the > > problem? I am including a list of the hardware, the > > original message we > > sent to the list, and a recent dmesg: > > > > FreeBSD 3.1-STABLE #1 > > Dual-Proc PII 450 > > 512MB RAM > > DPT PM334UW RAID controller > > - 16MB RAM > > - dual bus Ultra Wide > > - Six 9.1GB Quantum VikingII SCSI3 U2W drives > > - Three drives per bus, RAID5, one drive is hot-spare > > Intel EtherExpress Pro 10/100B Ethernet > > TOSHIBA CD-ROM XM-6201TA > > > > > > -------------- > > I've recently had the job of system administration dumped > > in my lap. I'm > > looking forward to getting on top of it, but I'm a little > > behind the 8-ball > > right now. If my subject matter varies too far from the > > allowed context of > > this list, please don't flame me too badly. > > > > Background: We are running a dual PII 450 system with a 45 > > gig raid array, > > controlled by a DPT PM334. > > > > The O/S: FreeBSD 3.1-STABLE #1 > > > > For several months this has been rock solid. However, in > > the past three > > weeks, we've had a number of crashes, most of which seem to > > be related to > > mysql queries. The system would be totally unresponsive to > > ssh/telnet and > > web, but would still return pings. > > > > The server is colocated at our ISP, so it's been tricky to > > track down the > > exact 'on screen' console errors. Today, shortly after we > > upgraded our > > mysql version, I did see the error. > > > > > > (da0:dpt0:0:0:0): Invalidating Pack > > (da0:dpt0:0:0:0): Invalidating Pack > > devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)! > > biodone: buffer already done > > (da0:dpt0:0:0:0): Read (10). CDB: 28 0 3 87 33 1f 0 0 80 0 > > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:20,0 > > (da0:dpt0:0:0:0): Invalid command operation code > > devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)! > > biodone: buffer already done > > > > > > Followed by a complete system freeze, including the console. > > > > Some hunting and searching has led us to believe that we > > are encountering a > > driver failure and that we should bring the OS back to -stable. > > > > As I said, I haven't done this before, so I'm a little > > anxious. Before I > > take that step, I would be very greatful to hear some input > > from those who > > surely know more about this than I do. > > > > Is bringing the system back to -stable likely to correct > > our problem? Am I > > missing some indicator in the error above? Has someone > > else encountered > > similar trouble (and found a fix?) > > > > I'll be happy to take replies in private e-mail if this is > > off topic. > > > > Any help would be great. > > > > Thanks, > > Jeremy > > > > > > _______________________________________________________________ > > Get Free Email and Do More On The Web. Visit http://www.msn.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 12: 2:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id F392514F8F for ; Sat, 7 Aug 1999 12:02:41 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id VAA51775; Sat, 7 Aug 1999 21:00:32 +0200 (CEST) Message-Id: <199908071900.VAA51775@midten.fast.no> To: joe@nall.com Cc: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG Subject: Re: continued crashes with 3.1-Stable From: Tor.Egge@fast.no In-Reply-To: Your message of "Sat, 07 Aug 1999 07:52:02 -0500" References: <37AC2BF2.C4C60F1E@nall.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 07 Aug 1999 21:00:32 +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > (da0:dpt0:0:0:0): Invalidating pack [...] > > FreeBSD 3.1-STABLE #1 [....] > > - Six 9.1GB Quantum VikingII SCSI3 U2W drives [...] > Don't discount the hardware problem response. We use big (200GB+) [...] I had similar problems when using 3.1-STABLE and 18 GB Quantum Atlas III disks with old firmware (). A disk dropped the scsi bus, the following selection operation timed out, and the CAM layer immediately invalidated the disk pack. Afterwards, the buffer cache was filled with dirty buffers destined for the bad disk. When the number of free buffers dropped to 0, the machine got stuck in an infinite kernel loop at splbio() protection. See PR 11697 for more details. By having the patch in PR 11697 applied, I was able to avoid the hang, but a reboot was still needed to access the bad disk again. Support for selection retries were added to the CAM code 1999/05/09. This reduces the problem as long as the disks only take short lunch breaks. I've not experienced this problem with newer revisions of the Quantum Atlas III Disk firmware (XN495). Also note that 3.1-STABLE had some problems with low memory hangs which were fixed about 1999/03/18. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 13:10: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from caerbanog.nimlabs.org (caerbanog.nimlabs.org [207.44.173.41]) by hub.freebsd.org (Postfix) with ESMTP id B81F214C9B for ; Sat, 7 Aug 1999 13:09:59 -0700 (PDT) (envelope-from nim@caerbanog.nimlabs.org) Received: (from nim@localhost) by caerbanog.nimlabs.org (8.9.3/8.9.3) id KAA14062 for freebsd-stable@freebsd.org; Thu, 5 Aug 1999 10:44:48 -0700 (PDT) (envelope-from nim) Received: from gyu.nimlabs.org (IDENT:nim@ppp-asok08--187.sirius.net [205.134.245.187]) by caerbanog.nimlabs.org (8.9.3/8.9.3) with ESMTP id KAA14024 for ; Thu, 5 Aug 1999 10:44:02 -0700 (PDT) (envelope-from nim@neglekt.lick.pvt.k12.ca.us) Received: (from nim@localhost) by gyu.nimlabs.org (8.8.7/8.8.7) id NAA08644 for nim@nimlabs.org; Sat, 7 Aug 1999 13:02:42 -0700 Date: Sat, 7 Aug 1999 13:00:16 -0700 From: Nick Martin To: "Andrej V. Olejnik (Andy V. Oleynik)" Cc: freebsd-stable@freebsd.org Subject: Re: Several Bugs (or maybe Features) (looks like known bug , see PR) Message-ID: <19990807130016.H442@neglekt.lwhs.org> References: <19990805052951.A72463@caerbanog.nimlabs.org> <19990806203429.A2789@dblab.ece.ntua.gr> <37AB31B6.872AFD8B@prime.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <37AB31B6.872AFD8B@prime.net.ua>; from Andrej V. Olejnik@caerbanog (Andy V. Oleynik) on Fri, Aug 06, 1999 at 10:04:23PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 06, 1999 at 10:04:23PM +0300, Andrej V. Olejnik@caerbanog (Andy V. Oleynik) wrote: > Could U pleas send ur dmesg & MBD/CPU specifications? > Yiorgos Adamopoulos wrote: I think I found the answer to why the clock is slow in a PR, namely to turn off apm support. But that still doesnt tell me how to get the thing to reboot properly (which is also very important). OK, here is the full dmesg from that box: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-STABLE #3: Wed Aug 4 09:13:58 PDT 1999 nim@caerbanog.nimlabs.org:/usr/src/sys/compile/CAERBANOG Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 74704326 Hz CPU: AMD K5 model 0 (74.70-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x500 Stepping=0 Features=0x3bf real memory = 33554432 (32768K bytes) avail memory = 29786112 (29088K bytes) Preloaded elf kernel "kernel" at 0xc02ed000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 ide_pci0: rev 0x04 on pci0.1.0 de0: rev 0x22 int a irq 11 on pci0.9.0 de0: Asante 21140A [10-100Mb/s] pass 2.2 de0: address 00:00:94:a1:a6:d7 de0: enabling 10baseT port Qlogic ISP Driver, FreeBSD CAM Version 0.991, Core Version 1.8 isp0: rev 0x02 int a irq 10 on pci0.10.0 isp0: using Memory space register mapping isp0: set PCI line size to 16 isp0: set PCI latency to 64 isp0: Board Revision 1020A, loaded F/W Revision 7.63.0 isp0: not supporting QFRZ option for target 0 isp0: not supporting QFRZ option for target 1 isp0: not supporting QFRZ option for target 2 isp0: not supporting QFRZ option for target 3 isp0: not supporting QFRZ option for target 4 isp0: not supporting QFRZ option for target 5 isp0: not supporting QFRZ option for target 6 isp0: not supporting QFRZ option for target 7 isp0: not supporting QFRZ option for target 8 isp0: not supporting QFRZ option for target 9 isp0: not supporting QFRZ option for target 10 isp0: not supporting QFRZ option for target 11 isp0: not supporting QFRZ option for target 12 isp0: not supporting QFRZ option for target 13 isp0: not supporting QFRZ option for target 14 isp0: not supporting QFRZ option for target 15 isp0: skipping settings for target 8 bus 0 isp0: skipping settings for target 9 bus 0 isp0: skipping settings for target 10 bus 0 isp0: skipping settings for target 11 bus 0 isp0: skipping settings for target 12 bus 0 isp0: skipping settings for target 13 bus 0 isp0: skipping settings for target 14 bus 0 isp0: skipping settings for target 15 bus 0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2060MB (4219425 sectors), 4465 cyls, 15 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 ep0 not found at 0x300 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 5 seconds for SCSI devices to settle isp0: driver initiated bus reset of bus 0 isp0: target 0 lun 0 had an unexpected bus free isp0: Auto Request Sense failed for target 0 lun 0 chanda0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 516MB (1057616 512 byte sectors: 64H 32S/T 516C) ging root device to wd0s1a WARNING: / was not properly dismounted de0: abnormal interrupt: transmit underflow (raising TX threshold to 96|256) de0: abnormal interrupt: transmit underflow (raising TX threshold to 128|512) de0: abnormal interrupt: transmit underflow (raising TX threshold to 160|1024) de0: abnormal interrupt: transmit underflow (switching to store-and-forward mode) Hope that helps. -- Nick Martin, nim@nimlabs.org, http://www.nimlabs.org If God didn't mean for us to juggle, tennis balls wouldn't come three to a can. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 13:23:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 697AC14CEE for ; Sat, 7 Aug 1999 13:23:16 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Sat, 7 Aug 1999 16:18:09 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B3FC4@FREYA> From: tcobb@staff.circle.net To: seth@freebie.dp.ny.frb.org Cc: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Subject: RE: continued crashes with 3.1-Stable Date: Sat, 7 Aug 1999 16:18:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The machine I'm having trouble with is a dual-PIII 500 running FreeBSD 3.2-19990730-STABLE. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Seth [mailto:seth@freebie.dp.ny.frb.org] > Sent: Saturday, August 07, 1999 2:35 PM > To: tcobb@staff.circle.net > Cc: lightningweb@hotmail.com; freebsd-stable@FreeBSD.ORG; > greg@lightningweb.com; jeremy@lightningweb.com; > keith@lightningweb.com; > criter@lightningweb.com > Subject: RE: continued crashes with 3.1-Stable > > > Have to disagree. 3.1-R had some problems. 3.2-S works > flawlessly, even > under heavy load (big disk I/O and >24 system load > averages). This is a > dual Xeon 450, scsi disks off an adaptec 7890, 384 megs RAM. > > Some things you didn't mention -- what was the date of your > last build, > and why haven't you gone to 3.2-S yet? > > SB > > On Sat, 7 Aug 1999 tcobb@staff.circle.net wrote: > > > I think the problem is the SMP. I've been having frequent > > freezes with SMP under heavy webserver load with 3.2-R, > > and 3.2-S. I'm unfortunately led to believe that FreeBSD > > SMP is just not ready for primetime. Too bad the $$ we blew > > on a dual PIII-550 box. > > > > -Troy Cobb > > Circle Net, Inc. > > http://www.circle.net > > > > > -----Original Message----- > > > From: lweb Lightningweb [mailto:lightningweb@hotmail.com] > > > Sent: Friday, August 06, 1999 11:33 PM > > > To: freebsd-stable@FreeBSD.ORG > > > Cc: greg@lightningweb.com; jeremy@lightningweb.com; > > > keith@lightningweb.com; criter@lightningweb.com > > > Subject: continued crashes with 3.1-Stable > > > > > > > > > We have not resolved our problem with frequent freezes with > > > our web server. > > > We had two responses to our first mail to this list, but > > > neither one was the > > > solution. The problem is that the server will stop > > > responding to ANYTHING > > > except pings. No telnet, no ssh, no web, no ftp, nothing. > > > Open telnet > > > sessions don't drop, there's just no response to > keyboard activity. > > > > > > One suggestion was to fix the "pthreads library," whic we > > > did. The other > > > was: "You may have hardware problems." > > > > > > This server is going down more frequently. Three times so > > > far today. There > > > is no apparant pattern to the crashes. They seem to happen > > > most often > > > during an Mysql database query, but it's happened many > > > times without any > > > queries (a few times just by running "pine" with a large > > > mailbox file). > > > > > > We cannot recreate the crash when we want, it just crashes > > > at random times. > > > We've tried hammering it with web, database queries, and > > > benchamrking > > > programs that slam the RAID array and memory and > > > processors, but it chuggs > > > right along. > > > > > > We have replaced drives in the RAID array, we are now > > > replacing drive > > > caddies. Next step I think will be the RAID controller. I > > > have a strong > > > gut feeling that it is software however. There's nothing > > > to substantiate > > > this, except that that more often than not, the crash > > > happens during an > > > MySQL query. > > > > > > Some (NOT ALL) of the suspect errors that we've recorded > > > from the console > > > during a crash are: > > > > > > (da0:dpt0:0:0:0): Invalidating pack > > > biodone: buffer already done > > > spec_getpages: I/O read failure: (error code=6) > > > size: 32768, resid: 32768, a_count: > 32768, valid: 0x0 > > > nread: 0, reqpage: 0, pindex: 0, pcount: 8 > > > > > > > > > Everyone please take a second look at this and help us > > > brainstorm the > > > problem? I am including a list of the hardware, the > > > original message we > > > sent to the list, and a recent dmesg: > > > > > > FreeBSD 3.1-STABLE #1 > > > Dual-Proc PII 450 > > > 512MB RAM > > > DPT PM334UW RAID controller > > > - 16MB RAM > > > - dual bus Ultra Wide > > > - Six 9.1GB Quantum VikingII SCSI3 U2W drives > > > - Three drives per bus, RAID5, one drive is hot-spare > > > Intel EtherExpress Pro 10/100B Ethernet > > > TOSHIBA CD-ROM XM-6201TA > > > > > > > > > -------------- > > > I've recently had the job of system administration dumped > > > in my lap. I'm > > > looking forward to getting on top of it, but I'm a little > > > behind the 8-ball > > > right now. If my subject matter varies too far from the > > > allowed context of > > > this list, please don't flame me too badly. > > > > > > Background: We are running a dual PII 450 system with a 45 > > > gig raid array, > > > controlled by a DPT PM334. > > > > > > The O/S: FreeBSD 3.1-STABLE #1 > > > > > > For several months this has been rock solid. However, in > > > the past three > > > weeks, we've had a number of crashes, most of which seem to > > > be related to > > > mysql queries. The system would be totally unresponsive to > > > ssh/telnet and > > > web, but would still return pings. > > > > > > The server is colocated at our ISP, so it's been tricky to > > > track down the > > > exact 'on screen' console errors. Today, shortly after we > > > upgraded our > > > mysql version, I did see the error. > > > > > > > > > (da0:dpt0:0:0:0): Invalidating Pack > > > (da0:dpt0:0:0:0): Invalidating Pack > > > devstat_end_transaction: HELP!! busy_count for da0 is > < 0 (-1)! > > > biodone: buffer already done > > > (da0:dpt0:0:0:0): Read (10). CDB: 28 0 3 87 33 1f 0 0 80 0 > > > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:20,0 > > > (da0:dpt0:0:0:0): Invalid command operation code > > > devstat_end_transaction: HELP!! busy_count for da0 is > < 0 (-1)! > > > biodone: buffer already done > > > > > > > > > Followed by a complete system freeze, including the console. > > > > > > Some hunting and searching has led us to believe that we > > > are encountering a > > > driver failure and that we should bring the OS back > to -stable. > > > > > > As I said, I haven't done this before, so I'm a little > > > anxious. Before I > > > take that step, I would be very greatful to hear some input > > > from those who > > > surely know more about this than I do. > > > > > > Is bringing the system back to -stable likely to correct > > > our problem? Am I > > > missing some indicator in the error above? Has someone > > > else encountered > > > similar trouble (and found a fix?) > > > > > > I'll be happy to take replies in private e-mail if this is > > > off topic. > > > > > > Any help would be great. > > > > > > Thanks, > > > Jeremy > > > > > > > > > > _______________________________________________________________ > > > Get Free Email and Do More On The Web. Visit http://www.msn.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 14: 9:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt011n65.san.rr.com (dt011n65.san.rr.com [204.210.13.101]) by hub.freebsd.org (Postfix) with ESMTP id 65CC614CFC for ; Sat, 7 Aug 1999 14:09:52 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA22258; Sat, 7 Aug 1999 14:06:25 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37AC9FD1.933EBC3D@gorean.org> Date: Sat, 07 Aug 1999 14:06:25 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0730 i386) X-Accept-Language: en MIME-Version: 1.0 To: tcobb@staff.circle.net Cc: freebsd-stable@FreeBSD.ORG Subject: Re: continued crashes with 3.1-Stable References: <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcobb@staff.circle.net wrote: > > I think the problem is the SMP. I've been having frequent > freezes with SMP under heavy webserver load with 3.2-R, > and 3.2-S. I'm unfortunately led to believe that FreeBSD > SMP is just not ready for primetime. Too bad the $$ we blew > on a dual PIII-550 box. We're having pretty good luck with our dual PIII-500 boxes under pretty heavy webserver load. However for various reasons we're using -current. There are some other factors to consider though. What kind of motherboards and nic cards are you using for example? Also, how heavy is heavy? And what kind of performance tuning have you done with the kernel, etc? It is of course possible that you're experiencing problems with the SMP code, but there are other places to look as well. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 14:16:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.forumone.com (orion.forumone.com [207.197.141.10]) by hub.freebsd.org (Postfix) with ESMTP id 3591714CFC for ; Sat, 7 Aug 1999 14:16:43 -0700 (PDT) (envelope-from adhir@forumone.com) Received: from orion.forumone.com (orion.forumone.com [207.197.141.10]) by mail.forumone.com (Postfix) with ESMTP id 177CCA8C0; Sat, 7 Aug 1999 17:14:25 -0400 (EDT) Date: Sat, 7 Aug 1999 17:14:25 -0400 (EDT) From: "Alok K. Dhir" To: tcobb@staff.circle.net Cc: lightningweb@hotmail.com, freebsd-stable@FreeBSD.ORG, greg@lightningweb.com, jeremy@lightningweb.com, keith@lightningweb.com, criter@lightningweb.com Subject: RE: continued crashes with 3.1-Stable In-Reply-To: <307D63ED6749CF11AAE9005004461A5B3FB8@FREYA> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You may want to try Solaris x86 on that same box... On Sat, 7 Aug 1999 tcobb@staff.circle.net wrote: > I think the problem is the SMP. I've been having frequent > freezes with SMP under heavy webserver load with 3.2-R, > and 3.2-S. I'm unfortunately led to believe that FreeBSD > SMP is just not ready for primetime. Too bad the $$ we blew > on a dual PIII-550 box. > > -Troy Cobb > Circle Net, Inc. > http://www.circle.net > > > -----Original Message----- > > From: lweb Lightningweb [mailto:lightningweb@hotmail.com] > > Sent: Friday, August 06, 1999 11:33 PM > > To: freebsd-stable@FreeBSD.ORG > > Cc: greg@lightningweb.com; jeremy@lightningweb.com; > > keith@lightningweb.com; criter@lightningweb.com > > Subject: continued crashes with 3.1-Stable > > > > > > We have not resolved our problem with frequent freezes with > > our web server. > > We had two responses to our first mail to this list, but > > neither one was the > > solution. The problem is that the server will stop > > responding to ANYTHING > > except pings. No telnet, no ssh, no web, no ftp, nothing. > > Open telnet > > sessions don't drop, there's just no response to keyboard activity. > > > > One suggestion was to fix the "pthreads library," whic we > > did. The other > > was: "You may have hardware problems." > > > > This server is going down more frequently. Three times so > > far today. There > > is no apparant pattern to the crashes. They seem to happen > > most often > > during an Mysql database query, but it's happened many > > times without any > > queries (a few times just by running "pine" with a large > > mailbox file). > > > > We cannot recreate the crash when we want, it just crashes > > at random times. > > We've tried hammering it with web, database queries, and > > benchamrking > > programs that slam the RAID array and memory and > > processors, but it chuggs > > right along. > > > > We have replaced drives in the RAID array, we are now > > replacing drive > > caddies. Next step I think will be the RAID controller. I > > have a strong > > gut feeling that it is software however. There's nothing > > to substantiate > > this, except that that more often than not, the crash > > happens during an > > MySQL query. > > > > Some (NOT ALL) of the suspect errors that we've recorded > > from the console > > during a crash are: > > > > (da0:dpt0:0:0:0): Invalidating pack > > biodone: buffer already done > > spec_getpages: I/O read failure: (error code=6) > > size: 32768, resid: 32768, a_count: 32768, valid: 0x0 > > nread: 0, reqpage: 0, pindex: 0, pcount: 8 > > > > > > Everyone please take a second look at this and help us > > brainstorm the > > problem? I am including a list of the hardware, the > > original message we > > sent to the list, and a recent dmesg: > > > > FreeBSD 3.1-STABLE #1 > > Dual-Proc PII 450 > > 512MB RAM > > DPT PM334UW RAID controller > > - 16MB RAM > > - dual bus Ultra Wide > > - Six 9.1GB Quantum VikingII SCSI3 U2W drives > > - Three drives per bus, RAID5, one drive is hot-spare > > Intel EtherExpress Pro 10/100B Ethernet > > TOSHIBA CD-ROM XM-6201TA > > > > > > -------------- > > I've recently had the job of system administration dumped > > in my lap. I'm > > looking forward to getting on top of it, but I'm a little > > behind the 8-ball > > right now. If my subject matter varies too far from the > > allowed context of > > this list, please don't flame me too badly. > > > > Background: We are running a dual PII 450 system with a 45 > > gig raid array, > > controlled by a DPT PM334. > > > > The O/S: FreeBSD 3.1-STABLE #1 > > > > For several months this has been rock solid. However, in > > the past three > > weeks, we've had a number of crashes, most of which seem to > > be related to > > mysql queries. The system would be totally unresponsive to > > ssh/telnet and > > web, but would still return pings. > > > > The server is colocated at our ISP, so it's been tricky to > > track down the > > exact 'on screen' console errors. Today, shortly after we > > upgraded our > > mysql version, I did see the error. > > > > > > (da0:dpt0:0:0:0): Invalidating Pack > > (da0:dpt0:0:0:0): Invalidating Pack > > devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)! > > biodone: buffer already done > > (da0:dpt0:0:0:0): Read (10). CDB: 28 0 3 87 33 1f 0 0 80 0 > > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:20,0 > > (da0:dpt0:0:0:0): Invalid command operation code > > devstat_end_transaction: HELP!! busy_count for da0 is < 0 (-1)! > > biodone: buffer already done > > > > > > Followed by a complete system freeze, including the console. > > > > Some hunting and searching has led us to believe that we > > are encountering a > > driver failure and that we should bring the OS back to -stable. > > > > As I said, I haven't done this before, so I'm a little > > anxious. Before I > > take that step, I would be very greatful to hear some input > > from those who > > surely know more about this than I do. > > > > Is bringing the system back to -stable likely to correct > > our problem? Am I > > missing some indicator in the error above? Has someone > > else encountered > > similar trouble (and found a fix?) > > > > I'll be happy to take replies in private e-mail if this is > > off topic. > > > > Any help would be great. > > > > Thanks, > > Jeremy > > > > > > _______________________________________________________________ > > Get Free Email and Do More On The Web. Visit http://www.msn.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 14:17:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 8BA6A14DEF for ; Sat, 7 Aug 1999 14:17:29 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by FREYA with Internet Mail Service (5.5.2448.0) id ; Sat, 7 Aug 1999 17:12:35 -0400 Message-ID: <307D63ED6749CF11AAE9005004461A5B3FC9@FREYA> From: tcobb@staff.circle.net To: Doug@gorean.org Cc: freebsd-stable@FreeBSD.ORG Subject: RE: continued crashes with 3.1-Stable Date: Sat, 7 Aug 1999 17:12:34 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Heavy" is about 400-500 kbytes/second pushed out through the NIC from 170-200 simultaneous apache processes. The box runs just apache and stronghold, with database served from a UP PIII 550 machine that's separate. NIC is a 3COM 3C905B. Kernel is customized, but maxusers is set to 128 with NMBCLUSTERS to 8192. We never get close to using all the clusters. Motherboard is a Supermicro P6SBU with 1GB ECC RAM. I've pushed more traffic than this on a UP machine, with a slower processor and less memory and the same NIC. That leaves potential hardware/configuration problems being related to: DPT controller (I've used this several times, though not an a 3.2-era machine) 1GB memory (first time with this much memory in a box) Dual processor -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Doug [mailto:Doug@gorean.org] > Sent: Saturday, August 07, 1999 5:06 PM > To: tcobb@staff.circle.net > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: continued crashes with 3.1-Stable > > > tcobb@staff.circle.net wrote: > > > > I think the problem is the SMP. I've been having frequent > > freezes with SMP under heavy webserver load with 3.2-R, > > and 3.2-S. I'm unfortunately led to believe that FreeBSD > > SMP is just not ready for primetime. Too bad the $$ we blew > > on a dual PIII-550 box. > > We're having pretty good luck with our dual PIII-500 > boxes under pretty > heavy webserver load. However for various reasons we're > using -current. > There are some other factors to consider though. What kind > of motherboards > and nic cards are you using for example? Also, how heavy is > heavy? And what > kind of performance tuning have you done with the kernel, > etc? It is of > course possible that you're experiencing problems with the > SMP code, but > there are other places to look as well. > > Doug > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Aug 7 16:25: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dialup124.zpr.uni-koeln.de (1-137.K.dial.o-tel-o.net [212.144.1.137]) by hub.freebsd.org (Postfix) with ESMTP id 384AD14C8B; Sat, 7 Aug 1999 16:24:49 -0700 (PDT) (envelope-from se@zpr.uni-koeln.de) Received: by dialup124.zpr.uni-koeln.de (Postfix, from userid 200) id C3FECD4D; Sat, 7 Aug 1999 13:43:07 +0200 (CEST) Date: Sat, 7 Aug 1999 13:43:07 +0200 From: Stefan Esser To: Rod Taylor Cc: jkh@zippy.cdrom.com, freebsd-stable@FreeBSD.ORG, Stefan Esser Subject: Re: continued crashes with 3.1-Stable Message-ID: <19990807134307.A868@dialup124.zpr.uni-koeln.de> Reply-To: se@freebsd.org References: <2602.934003898@localhost> <99080703410000.01685@a11.idiotswitch.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <99080703410000.01685@a11.idiotswitch.org>; from Rod Taylor on Sat, Aug 07, 1999 at 03:39:14AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-08-07 03:39 -0400, Rod Taylor wrote: > On Sat, 07 Aug 1999, Jordan K. Hubbard wrote: > > I wonder why this doesn't happen to Yahoo's SMP boxes then. > > They run -stable and would be screaming blue murder if their > > webservers were doing the same thing. So, for that matter, > > would Hotmail. > > > > Perhaps someone should try to find out what hardware on their systems works. > Is it possible that FreeBSD supports one SMP mobo brand better than others? One thing to look out for are kernel modifications that are not SMP safe. (I found out the hard way, when I tried the IPsec code ported from OpenBSD to FreeBSD half a year ago. It made SMP systems crash under load!) I am only aware of one more kernel option that is not SMP safe: The CODA file system code. The developers just don't consider SMP a prime objective. But there might be other exotic drivers or options (or local modifications) in your kernel, that miss some SMP locks. Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message