From owner-freebsd-current Sun Feb 1 03:57:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA28087 for current-outgoing; Sun, 1 Feb 1998 03:57:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA28082 for ; Sun, 1 Feb 1998 03:57:12 -0800 (PST) (envelope-from Matthew.Thyer@dsto.defence.gov.au) Received: from exchsa1.dsto.defence.gov.au (exchsa1.dsto.defence.gov.au [131.185.2.94]) by digger1.defence.gov.au (8.7.5/8.7.3) with ESMTP id WAA19978 for ; Sun, 1 Feb 1998 22:26:47 +1030 (CST) Received: from fang.dsto.defence.gov.au ([131.185.2.5]) by exchsa1.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.1960.3) id 1B0FWQ85; Sun, 1 Feb 1998 22:26:21 +1030 Received: from eddie.dsto.defence.gov.au (eddie.dsto.defence.gov.au [131.185.2.111]) by fang.dsto.defence.gov.au (8.8.5/8.8.5) with ESMTP id WAA29536 for ; Sun, 1 Feb 1998 22:26:27 +1030 (CST) Received: from eddie.dsto.defence.gov.au (localhost [127.0.0.1]) by eddie.dsto.defence.gov.au (8.8.8/8.8.5) with SMTP id WAA13116 for ; Sun, 1 Feb 1998 22:26:27 +1030 (CST) Message-ID: <34D462EB.41C67EA6@dsto.defence.gov.au> Date: Sun, 01 Feb 1998 22:26:27 +1030 From: Matthew Thyer X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: make world breakage on -CURRENT ctm-src-cur.3233 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" FreeBSD-CURRENT does not make world as at CTM delta src-cur.3233. The kernel builds and runs fine. Note: This could be NFS breakage as both /usr/src and /usr/obj are NFS mounted from Solaris 2.5.1 server. ===> lkm/nullfs @ -> /usr/src/sys machine -> /usr/src/sys/i386/include sh /usr/src/lkm/nullfs/../../sys/kern/vnode_if.sh /usr/src/lkm/nullfs/../../sys/ kern/vnode_if.src rm -f .depend mkdep -f .depend -a -DNULLFS -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/obj/usr/ src/lkm/nullfs -I/usr/obj/usr/src/lkm/nullfs/@ -I/usr/obj/usr/src/tmp/usr/includ e -DVFS_LKM -DMODVNOPS=null_modvnops /usr/src/lkm/nullfs/../../sys/miscfs/nullf s/null_subr.c /usr/src/lkm/nullfs/../../sys/miscfs/nullfs/null_vfsops.c /usr/src /lkm/nullfs/../../sys/miscfs/nullfs/null_vnops.c /usr/src/lkm/nullfs/../../sys/miscfs/nullfs/null_subr.c:41: opt_debug_nullfs.h: No such file or directory /usr/src/lkm/nullfs/../../sys/miscfs/nullfs/null_vfsops.c:47: opt_debug_nullfs.h : No such file or directory /usr/src/lkm/nullfs/../../sys/miscfs/nullfs/null_vnops.c:177: opt_debug_nullfs.h : No such file or directory mkdep: compile failed *** Error code 1 Stop. -- Matthew Thyer Phone: +61 8 8259 7249 Corporate Information Systems Fax: +61 8 8259 5537 Defence Science and Technology Organisation, Salisbury PO Box 1500 Salisbury South Australia 5108 From owner-freebsd-current Sun Feb 1 04:44:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA03299 for current-outgoing; Sun, 1 Feb 1998 04:44:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA03294; Sun, 1 Feb 1998 04:44:06 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <9245-22629>; Sun, 1 Feb 1998 13:44:01 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.8/8.8.8) with ESMTP id NAA00908; Sun, 1 Feb 1998 13:32:34 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id NAA25546; Sun, 1 Feb 1998 13:31:59 +0100 (MET) Message-Id: <199802011231.NAA25546@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: <199801312358.SAA02250@dyson.iquest.net> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Sun, 1 Feb 98 13:31:57 +0100 To: dyson@FreeBSD.ORG Subject: Re: -current locks my machine frequently cc: freebsd-current@FreeBSD.ORG Reply-To: ben@stuyts.nl References: <199801312358.SAA02250@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Sat, 31 Jan 1998, "John S. Dyson" wrote: > Mike Smith said: > > > > > > John Dyson made some changes last night that I had hoped would finally > > > fix the problem, but I just had the machine lock up again a few minutes > > > ago. It always seems to occur when X is running (usually when Netscape > > > starts to swap heavily). > I'm going to take some more stabs at the problem. Donald, if you haven't > send me a copy of your config, would you please do so. Also, the dmesg > output could also be helpful... John, I'm taking the liberty of sending the same data for my machine, because I'm having the same problem. Maybe it is a SMP specific problem, but it also started a few weeks ago. The machine just locks solid. Last night I've cvsupped, one hour later is locked up. Please let me know if you need more information or if I can help in any other way. (Except buying the obligatory beer when you're in Holland. B-) It is a Gigabyte 586DX with dual 166 MMX, 64 MB ram, on-board 7880 scsi controller, SMC network card with DEC chip, Diamond Stealth 3440 video card with 4 MB vram, soundblaster awe32 and an additional isa card with two uarts. Here's dmesg: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Sat Jan 31 22:52:58 MET 1998 benst@terminus.stuyts.nl:/usr/source/src/sys/compile/TERMINUS-SMP CPU: Pentium (586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8003bf real memory = 67108864 (65536K bytes) avail memory = 62713856 (61244K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 de0: rev 0x11 int a irq 17 on pci0.9.0 de0: SMC 21041 [10Mb/s] pass 1.1 de0: address 00:00:c0:1f:54:e8 vga0: rev 0x02 int a irq 18 on pci0.10.0 ahc0: rev 0x00 int a irq 19 on pci0.12.0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 1 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4134MB (8467200 512 byte sectors) sd0: with 8205 cyls, 6 heads, and an average 171 sectors/track sd1 at scbus0 target 3 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 810MB (1660299 512 byte sectors) sd1: with 3653 cyls, 4 heads, and an average 113 sectors/track cd0 at scbus0 target 4 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM can't get the size worm0 at scbus0 target 5 lun 0 worm0: type 5 removable SCSI 2 worm0: Write-Once Probing for PnP devices: CSN 1 Vendor ID: CTL0039 [0x39008c0e] Serial 0x00020ddb Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 at 0x3e8-0x3ef irq 10 on isa sio2: type 16550A sio3 at 0x2e8-0x2ef irq 9 on isa sio3: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: Intel Pentium F00F detected, installing workaround APIC_IO: routing 8254 via 8259 on pin 0 SMP: AP CPU #1 Launched! sio3: 64 events for device with no tp Here's my config: machine "i386" cpu "I586_CPU" ident TERMINUS-SMP maxusers 10 # Create a SMP capable kernel (mandatory options): options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Lets always enable the kernel debugger for SMP. options DDB options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options MFS #Memory File System options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG options "VM86" config kernel root on sd0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 controller ahc0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows device worm0 at scbus? # SCSI worm options SCSI_REPORT_GEOMETRY controller pnp0 device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device apm0 at isa? disable flags 0x31 # Advanced Power Management device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 10 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr device de0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device bpfilter 4 #Berkeley packet filter options KTRACE #kernel tracing # Controls all sound devices controller snd0 device sb0 at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 Best regards, Ben From owner-freebsd-current Sun Feb 1 05:06:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA05147 for current-outgoing; Sun, 1 Feb 1998 05:06:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA05141 for ; Sun, 1 Feb 1998 05:06:22 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id OAA20155 for freebsd-current@FreeBSD.ORG; Sun, 1 Feb 1998 14:06:17 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id NAA25225; Sun, 1 Feb 1998 13:34:18 +0100 (CET) (envelope-from roberto) Message-ID: <19980201133418.10436@keltia.freenix.fr> Date: Sun, 1 Feb 1998 13:34:18 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: -current locks my machine frequently Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <199801311103.MAA05035@muon.xs4all.nl> <19980131184543.57933@scsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <19980131184543.57933@scsn.net>; from Donald J. Maddox on Sat, Jan 31, 1998 at 06:45:43PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4019 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" According to Donald J. Maddox: > John Dyson made some changes last night that I had hoped would finally > fix the problem, but I just had the machine lock up again a few minutes > ago. It always seems to occur when X is running (usually when Netscape > starts to swap heavily). My machine -- I'm using a K6 -- is working very fine. I've seen a slowdown sometimes when it is beginning to access the disk rather heavily but it may be related to other things. My kernel is from Jan, 26th though. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #54: Mon Jan 26 20:29:17 CET 1998 From owner-freebsd-current Sun Feb 1 05:41:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA09051 for current-outgoing; Sun, 1 Feb 1998 05:41:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sinbin.demos.su (sinbin.demos.su [194.87.5.31]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA09045 for ; Sun, 1 Feb 1998 05:41:52 -0800 (PST) (envelope-from bag@sinbin.demos.su) Received: by sinbin.demos.su id QAA15231; (8.6.12/D) Sun, 1 Feb 1998 16:41:17 +0300 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199802011341.QAA15231@sinbin.demos.su> Subject: Re: RAID controllers - folks, check this thing out In-Reply-To: <19980130233604.57426@mcs.net> from "Karl Denninger" at "Jan 30, 98 11:36:04 pm" X-ELM-OSV: (Our standard violations) no-mime=1; no-hdr-encoding=1 To: karl@mcs.net (Karl Denninger) Date: Sun, 1 Feb 1998 16:41:17 +0300 (MSK) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > Remember a bit ago I was asking about RAID controllers? > > Well, I found one. > > Talk to Pacific Computer Expansions, a gentleman by the name of Warren at > 800-458-5058. > > You want the CRD-5440. > > This is a RAID 0, 0+1, 4 or 5 free-standing SCSI device. It accepts cache > memory, and also has battery backup capabilities (attach a 6V Gelcel to it). we use INFORTRAND scsi-scsi RAID's (www.infortrand.com) cache up to 128MB (2 SIMM) 6 ultra-wide channels (3 chanels - base and 3 - extension board) backup battery for cache (up to 100h) serial interface (ansi, vt100 terminal) cpu 486dx2-66 (model with P5 is also available) up to 64 logical drivers (up to 8 raids, up-to 8 partition each) accordin to Justin T. Gibbs nonCAM distributions have problem with multiple LUN's Justin T. Gibbs: "Yes, this is a long standing bug having to do with multi-lun devices in the aic7xxx driver. It has been corrected in the CAM version of the driver, but the changes are too invasive to attempt to port them into the driver in either current or stable. Since this kinds of devices that trigger this problem are rare, it seldom causes problems. Yours is the first bug report I've seen about this issue." without CAM you can only use one logical drive per host channel Alex. > > I have MEASURED *filesystem* I/O rates in excess of 10MB (yes, that is > megaBYTES/second) through this thing on a 5-disk array running RAID 5 > doing *WRITES*. > > RAW I/O is considerably faster, as you might expect, and reads are even > faster. Reads appear to be limted by the Ultra SCSI interface. > > This thing has 4 SCSI channels; any number can be delegated to disk and/or > host use. Its ultra/wide, and comes in both a differential and single-ended > version. Fits in a half-height drive bay (!), powered by a 40Mhz MIPS R3000 > processor. It accepts one or two 72-pin SIMMs with up to 512MB (!) of cache > memory; the cache, needless to say, grossly improves the performance, > especially in a read-intensive environment. > > It has both a front panel and serial interface (you need to hook up a > terminal to configure it, but alarm reporting and rebuild control can be > done from the front panel). > > One catch - you MUST HAVE either a UPS interfaced to this, or a gelcell. > The reason is the cache RAM - without one of those two it will refuse to > go "online", because a power loss will screw you badly. With the UPS > interfaced to it the "low power alarm" will quiesce the host channel and > flush the cache, then shut down the controller - leading to a safe > power-down. If you have the battery, then a power loss is also not > catastrophic (as long as the backup lasts at least). > > The controller can handle up to 45 devices (!) in multiple RAID sets, > appears as a single target per host channel, and can be partitioned to > show multiple LUNs if you'd like. Both hot and warm spare capabilities > are supported. > > FreeBSD will boot from it just like any other disk. Right now I have a > ~30GB "disk" configured on this thing - 5 9G drives in a Raid 5 > configuration. It works right out of the box. > > Its about a $2500 device, but given what it does, and the performance > levels it attains, its VERY reasonable. > > I'm ordering six more of these for our server farm next week; for the money > its basically impossible to beat the performance and operational capabilities, > at least from what I've seen so far. In the area of "small" RAID adapters > I've not seen anything that can come anywhere close to this thing's > performance levels. > > -- > -- > Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin > http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service > | NEW! K56Flex support on ALL modems > Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS > Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost > From owner-freebsd-current Sun Feb 1 06:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA12055 for current-outgoing; Sun, 1 Feb 1998 06:10:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from plugcom.ru (uucp@radiance.plugcom.ru [195.2.73.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA12049 for ; Sun, 1 Feb 1998 06:10:11 -0800 (PST) (envelope-from tarkhil@minas-tirith.pol.ru) Received: from minas-tirith.pol.ru (uucp@localhost) by plugcom.ru (8.8.7/8.8.6) with UUCP id RAA10513 for freebsd.org!freebsd-current; Sun, 1 Feb 1998 17:10:06 +0300 (MSK) Received: from minas-tirith.pol.ru (tarkhil@tarkhil.pol.ru [127.0.0.1]) by minas-tirith.pol.ru (8.8.7/8.8.7) with ESMTP id PAA11987 for ; Sun, 1 Feb 1998 15:34:28 +0300 (MSK) (envelope-from tarkhil@minas-tirith.pol.ru) Message-Id: <199802011234.PAA11987@minas-tirith.pol.ru> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd.org!freebsd-current@minas-tirith.pol.ru Subject: File locked after execution Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Feb 1998 15:34:23 +0300 From: Alex Povolotsky Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hello! Installation of lout fails several days ago on my 3.0-SNAP, I've investigated the case and found that for some time after execution file is locked. strip, for instance, fails. I guess it's no right way, file write access shouldn't be denied, but should instead unload file image from memory. Alex. From owner-freebsd-current Sun Feb 1 07:51:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA23888 for current-outgoing; Sun, 1 Feb 1998 07:51:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA23862 for ; Sun, 1 Feb 1998 07:51:43 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.8/8.8.8) with ESMTP id QAA10509 for ; Sun, 1 Feb 1998 16:51:28 +0100 (MET) Received: from curry.mchp.siemens.de (daemon@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.8/8.8.5) with ESMTP id QAA17324 for ; Sun, 1 Feb 1998 16:51:30 +0100 (CET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id QAA16211 for ; Sun, 1 Feb 1998 16:51:30 +0100 (CET) From: Andre Albsmeier Message-Id: <199802011551.QAA18953@intern> Subject: Re: File Size limit? In-Reply-To: <199801312325.RAA08750@home.dragondata.com> from Kevin Day at "Jan 31, 98 05:25:55 pm" To: toasty@home.dragondata.com (Kevin Day) Date: Sun, 1 Feb 1998 16:51:22 +0100 (CET) Cc: dyson@FreeBSD.ORG, karl@mcs.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > > > Good, because I am dangerously close to 2G files in my Rdbms right now :-) > > > > > I suspect that you won't have any problems until at least 32GB. Theoretically, > > we can support .5TB, but it hasn't been adequately tested, and I believe > > that there are some known overflow problems before there. > > > > We've passed 4G on our httpd log files with no adverse side effects. (analog > freaked out past 2G, but I can reliably read/write at least that far) > > -rw-r--r-- 1 root bin 4937477849 Jan 31 17:24 httpd-access.log JFYI, when doing backups, I tar all files into a single tarfile on a seperate holding disk. I have been above 16GB already without any visible side effects (2.2.5-stable). However, deleting that file takes a little bit :-). -Andre From owner-freebsd-current Sun Feb 1 07:59:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25023 for current-outgoing; Sun, 1 Feb 1998 07:59:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tigger.chameleon.com (root@ts24-01.vcr.istar.ca [204.191.154.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25016 for ; Sun, 1 Feb 1998 07:59:22 -0800 (PST) (envelope-from teisler@istar.ca) Received: from tigger.chameleon.com (teisler@localhost.chameleon.com [127.0.0.1]) by tigger.chameleon.com (8.8.5/8.8.5) with SMTP id IAA06334 for ; Sun, 1 Feb 1998 08:07:00 -0800 (PST) Message-ID: <34D49DA4.41C67EA6@istar.ca> Date: Sun, 01 Feb 1998 08:07:00 -0800 From: Troi Eisler Organization: Chameleon Consulting Inc. X-Mailer: Mozilla 3.0Gold (X11; U; BSD/OS 3.1 i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: unsubscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" unsubscribe From owner-freebsd-current Sun Feb 1 11:43:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA21900 for current-outgoing; Sun, 1 Feb 1998 11:43:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21813 for ; Sun, 1 Feb 1998 11:42:43 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by mantar.slip.netcom.com (8.8.8/8.8.8) with SMTP id LAA01914 for ; Sun, 1 Feb 1998 11:41:59 -0800 (PST) (envelope-from root@mantar.slip.netcom.com) Date: Sun, 1 Feb 1998 11:41:58 -0800 (PST) From: Manfred Antar To: current@FreeBSD.ORG Subject: current kernel build fails Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" new version of scsi_ioctl.c breaks kernel build : this is with a SMP machine with scsi disk, scsi tape,an scsi cdrom and a Buslogic 74xB SCSI host adapter, no ide. this is the version: scsi_ioctl.c,v 1.28 1998/02/01 04:13:00 older version works: scsi_ioctl.c,v 1.27 1997/12/02 21:07:01 cc -c -O2 -pipe -m486 -fno-strength-reduce -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -nostdinc -I- -I. -I../.. -I../../../include -DPQ_LARGECACHE -DLKM -DSYSVSMG -DSYSVIPC -DCLK_USE_I586_CALIBRATION -DKERNEL -include opt_global.h ../../scsi/scsi_ioctl.c ../../scsi/scsi_ioctl.c: In function `scsi_do_ioctl': ../../scsi/scsi_ioctl.c:259: `SCSIOCGETDEVINFO' undeclared (first use this function) ../../scsi/scsi_ioctl.c:259: (Each undeclared identifier is reported only once ../../scsi/scsi_ioctl.c:259: for each function it appears in.) ../../scsi/scsi_ioctl.c:370: dereferencing pointer to incomplete type ../../scsi/scsi_ioctl.c:370: dereferencing pointer to incomplete type ../../scsi/scsi_ioctl.c:371: dereferencing pointer to incomplete type ../../scsi/scsi_ioctl.c:373: dereferencing pointer to incomplete type *** Error code 1 Manfred ============================== || mantar@netcom.com || || Ph. (415) 681-6235 || ============================== From owner-freebsd-current Sun Feb 1 12:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25215 for current-outgoing; Sun, 1 Feb 1998 12:06:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.scsn.net (scsn.net [206.25.246.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25210 for ; Sun, 1 Feb 1998 12:06:35 -0800 (PST) (envelope-from dmaddox@scsn.net) Received: from rhiannon.scsn.net ([208.133.153.64]) by mail.scsn.net (Post.Office MTA v3.1.2 release (PO205-101c) ID# 0-41950U6000L1100S0) with ESMTP id AAA139; Sun, 1 Feb 1998 15:04:13 -0500 Received: (from root@localhost) by rhiannon.scsn.net (8.8.8/8.8.7) id PAA03234; Sun, 1 Feb 1998 15:05:57 -0500 (EST) (envelope-from root) Message-ID: <19980201150556.61675@scsn.net> Date: Sun, 1 Feb 1998 15:05:56 -0500 From: dmaddox@scsn.net (Donald J. Maddox) To: Manfred Antar , current@FreeBSD.ORG Subject: Re: current kernel build fails Reply-To: dmaddox@scsn.net Mail-Followup-To: Manfred Antar , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Manfred Antar on Sun, Feb 01, 1998 at 11:41:58AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Sun, Feb 01, 1998 at 11:41:58AM -0800, Manfred Antar wrote: > > new version of scsi_ioctl.c breaks kernel build : > this is with a SMP machine with scsi disk, scsi tape,an scsi cdrom > and a Buslogic 74xB SCSI host adapter, no ide. I beleive Garrett already committed a fix for this. You should get the fix now if you cvsup again. From owner-freebsd-current Sun Feb 1 12:14:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26964 for current-outgoing; Sun, 1 Feb 1998 12:14:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mantar.slip.netcom.com (mantar.slip.netcom.com [192.187.167.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26921 for ; Sun, 1 Feb 1998 12:14:03 -0800 (PST) (envelope-from manfred@mantar.slip.netcom.com) Received: from mantar.slip.netcom.com (localhost [127.0.0.1]) by mantar.slip.netcom.com (8.8.8/8.8.8) with ESMTP id MAA05592; Sun, 1 Feb 1998 12:13:53 -0800 (PST) (envelope-from manfred@mantar.slip.netcom.com) Message-Id: <199802012013.MAA05592@mantar.slip.netcom.com> X-Mailer: exmh version 2.0.1 12/23/97 To: dmaddox@scsn.net cc: Manfred Antar , current@FreeBSD.ORG Subject: Re: current kernel build fails In-reply-to: Your message of "Sun, 01 Feb 1998 15:05:56 EST." <19980201150556.61675@scsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Feb 1998 12:13:52 -0800 From: "Manfred A. Antar" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > On Sun, Feb 01, 1998 at 11:41:58AM -0800, Manfred Antar wrote: > > > > new version of scsi_ioctl.c breaks kernel build : > > this is with a SMP machine with scsi disk, scsi tape,an scsi cdrom > > and a Buslogic 74xB SCSI host adapter, no ide. > > I beleive Garrett already committed a fix for this. You should get > the fix now if you cvsup again. > > No sooner than i sent that off. I resuped and got it. Thanks Manfred -- ================================== || mantar@netcom.com || || Ph. (415) 647-4843 || ================================== From owner-freebsd-current Sun Feb 1 12:15:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27224 for current-outgoing; Sun, 1 Feb 1998 12:15:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27216 for ; Sun, 1 Feb 1998 12:15:17 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from bonsai.hiwaay.net (max2-131.HiWAAY.net [208.147.145.131]) by fly.HiWAAY.net (8.8.8/8.8.6) with SMTP id OAA06929; Sun, 1 Feb 1998 14:15:04 -0600 (CST) Message-ID: <34D4D7EC.6201DD56@hiwaay.net> Date: Sun, 01 Feb 1998 14:15:40 -0600 From: Steve Price X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Manfred Antar CC: current@FreeBSD.ORG Subject: Re: current kernel build fails References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Manfred Antar wrote: > > new version of scsi_ioctl.c breaks kernel build : > this is with a SMP machine with scsi disk, scsi tape,an scsi cdrom > and a Buslogic 74xB SCSI host adapter, no ide. > > this is the version: scsi_ioctl.c,v 1.28 1998/02/01 04:13:00 > older version works: scsi_ioctl.c,v 1.27 1997/12/02 21:07:01 > [errors elided] This was fixed in the following commit earlier today. wollman 1998/02/01 10:09:50 PST Modified files: sys/scsi scsi_ioctl.c sys/sys scsiio.h Log: Serves me right for committing code late at night... Fix the SCIOCGETDEVINFO code so that it compiles, and while I'm at it, add support for human-readable device names so that I don't have to call devname(3) on the scd->dev to get it. Revision Changes Path 1.29 +9 -3 src/sys/scsi/scsi_ioctl.c 1.10 +5 -3 src/sys/sys/scsiio.h Steve > Manfred > > ============================== > || mantar@netcom.com || > || Ph. (415) 681-6235 || > ============================== From owner-freebsd-current Sun Feb 1 18:45:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18144 for current-outgoing; Sun, 1 Feb 1998 18:45:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from miro.bestweb.net (miro.bestweb.net [209.94.100.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18136 for ; Sun, 1 Feb 1998 18:44:58 -0800 (PST) (envelope-from aryder@bestweb.net) Received: from monet.bestweb.net (aryder@monet.bestweb.net [209.94.100.120]) by miro.bestweb.net (8.8.8/8.8.8) with SMTP id VAA16890; Sun, 1 Feb 1998 21:44:19 -0500 (EST) Date: Sun, 1 Feb 1998 21:44:31 -0500 (EST) From: Andrew Ryder To: Mark Murray cc: current@FreeBSD.ORG Subject: Re: Linux emulation and name resolution In-Reply-To: <199801312153.XAA08138@greenpeace.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Theres a FreeBSD real audio player for download on www.real.com... --- Andrew Ryder aryder@bestweb.net BestWeb Support Team support@bestweb.net "New Yorks Best Internet Service Provider" www.bestweb.net On Sat, 31 Jan 1998, Mark Murray wrote: > Hi > > I could have sworn this was working a few weeks ago. I am running > 3.0-CURRENT (Really recent), and the RealPlayer Linux 5.0p3 will not > work if it has to look up names (such as > pnm://ra.webmonster.net/wew/spamdebate.ra). It works fine if the file > is local, and if I blat /conpat/etc/resolv.conf, then the progroam just > hangs, otherwise it complains that the server "is invalid". > > Any suggestions? > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > From owner-freebsd-current Sun Feb 1 20:16:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27237 for current-outgoing; Sun, 1 Feb 1998 20:16:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (dacole@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27211 for ; Sun, 1 Feb 1998 20:16:29 -0800 (PST) (envelope-from dacole@netcom.ca) Received: from localhost (dacole@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id XAA26271 for ; Sun, 1 Feb 1998 23:16:27 -0500 (EST) X-Authentication-Warning: tor-adm1.nbc.netcom.ca: dacole owned process doing -bs Date: Sun, 1 Feb 1998 23:16:27 -0500 (EST) From: Dave Cole X-Sender: dacole@tor-adm1 cc: current@FreeBSD.ORG Subject: Re: Linux emulation and name resolution In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Sun, 1 Feb 1998, Andrew Ryder wrote: -Theres a FreeBSD real audio player for download on www.real.com... Last I looked, there wasn't a realaudio 5.0 player, only a 3.0 player for FreeBSD. I've seen a number of sites that refuse to talk to a 3.0 player. -> Hi -> -> I could have sworn this was working a few weeks ago. I am running -> 3.0-CURRENT (Really recent), and the RealPlayer Linux 5.0p3 will not -> work if it has to look up names (such as -> pnm://ra.webmonster.net/wew/spamdebate.ra). It works fine if the file -> is local, and if I blat /conpat/etc/resolv.conf, then the progroam just -> hangs, otherwise it complains that the server "is invalid". ------------------------------------------------------------- Dave Cole (DC1110) | dacole@netcom.ca Systems Administrator | dacole@vex.net | office/~dacole/ Netcom Canada | www.vex.net/~dacole/ 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725 From owner-freebsd-current Mon Feb 2 01:31:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA02816 for current-outgoing; Mon, 2 Feb 1998 01:31:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from beast.gu.net (beast.gu.net [194.93.190.196]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA02810 for ; Mon, 2 Feb 1998 01:31:16 -0800 (PST) (envelope-from stesin@gu.net) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by beast.gu.net (8.8.7/8.7.3) with SMTP id LAA17457; Mon, 2 Feb 1998 11:30:52 +0200 (EET) Date: Mon, 2 Feb 1998 11:30:51 +0200 (EET) From: Andrew Stesin Reply-To: stesin@gu.net To: Garrett Wollman cc: freebsd-current@FreeBSD.ORG Subject: Re: LFS is nuked? In-Reply-To: <199801310108.UAA23804@khavrinen.lcs.mit.edu> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Fri, 30 Jan 1998, Garrett Wollman wrote: > > Of course, we all know that once something is in the attic, it's > > bound to be studiosly attended to, just like the XNS, ISO, and > > X.25 code have all been fixed... > > But unlike XNS, ISO-CLNS, and X.25, LFS might actually be of value to > real users. LFS _is_ of value, unionfs also is, and X.25 also is for someone... Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-current Mon Feb 2 03:26:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14021 for current-outgoing; Mon, 2 Feb 1998 03:26:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14006; Mon, 2 Feb 1998 03:26:30 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id GAA03464; Mon, 2 Feb 1998 06:26:22 -0500 (EST) (envelope-from toor) Message-Id: <199802021126.GAA03464@dyson.iquest.net> Subject: Re: -current locks my machine frequently In-Reply-To: <199802011231.NAA25546@daneel.stuyts.nl> from Ben Stuyts at "Feb 1, 98 01:31:57 pm" To: ben@stuyts.nl Date: Mon, 2 Feb 1998 06:26:22 -0500 (EST) Cc: dyson@FreeBSD.ORG, freebsd-current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" To the gang that has been helping me find the problems with -current: I have found another problem that I can reproduce. It is likely the X crash problem. I will be working on it. (Things are so much easier when I can reproduce problems, and anytime you'all send me the maximal amount of info, it gives me a better chance of finding things... Thanks again!!! Ben Stuyts said: > On Sat, 31 Jan 1998, "John S. Dyson" wrote: > > > Mike Smith said: > > > > > > > > John Dyson made some changes last night that I had hoped would finally > > > > fix the problem, but I just had the machine lock up again a few minutes > > > > ago. It always seems to occur when X is running (usually when Netscape > > > > starts to swap heavily). > > > I'm going to take some more stabs at the problem. Donald, if you haven't > > send me a copy of your config, would you please do so. Also, the dmesg > > output could also be helpful... > > John, > > I'm taking the liberty of sending the same data for my machine, because I'm > having the same problem. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Feb 2 03:54:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA17175 for current-outgoing; Mon, 2 Feb 1998 03:54:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.ftf.dk (root@mail.ftf.dk [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA17148; Mon, 2 Feb 1998 03:54:19 -0800 (PST) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.2]) by firewall.ftf.dk (8.7.6/8.7.3) with ESMTP id OAA10842; Mon, 2 Feb 1998 14:39:52 +0100 Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.5/8.8.5/prosa-1.1) with ESMTP id MAA05043; Mon, 2 Feb 1998 12:57:14 +0100 (CET) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.7/8.8.5/prosa-1.1) id MAA10293; Mon, 2 Feb 1998 12:53:19 +0100 (CET) Message-ID: <19980202125319.19336@deepo.prosa.dk> Date: Mon, 2 Feb 1998 12:53:19 +0100 From: Philippe Regnauld To: security@FreeBSD.ORG, current@FreeBSD.ORG Subject: Fwd: "Re: Ssyslog licensing" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e X-Operating-System: FreeBSD 2.2.5-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" [cross posted to -current and -security] I've been exchanging a few emails with the people from CORE SDI, who've released a piece of software called ssyslog, which uses crypted transactions to protect from forgery and tampering with remote logs. The software is available with sources, but the license has some restrictions (i.e.: can't be used in commercial software, but apparently can be distributed as binaries in a CD distrib, as long as the sources are included). FreeBSD port under way. -----Forwarded message from "Jonatan Altszul (CORE SDI S.A.)" ----- Date: Thu, 29 Jan 1998 14:32:16 -0700 (MST) From: "Jonatan Altszul (CORE SDI S.A.)" To: Philippe Regnauld cc: "Jonatan Altszul (CORE SDI S.A.)" Subject: Re: Ssyslog licensing On Thu, 29 Jan 1998, Philippe Regnauld wrote: > Jonatan Altszul (CORE SDI S.A.) writes: > > > Well, the software is completly free as long as you keep all the > > copyrights in place. You can use use it (or part of it) only in a > > non-commercial way. > > Ok -- but see below: > > > At the moment, we are planning to release a few more ports in > > the next couple of weeks (that will include for sure FreeBSD, Solaris 2.X > > and more). In case that you need now a specific port, just tell me and I > > might be able to send you it before the official release. > > Yes, I am interested -- so would the FreeBSD people in general, > I think. > > > Regarding your question about shipping our ssyslog with a > > commercial distribution of UNIX or using it in any other commercial > > application: the source code itself is free to be distributed in a > > non-commercial way. If you want to include it on a commercial package you > > have to contact us. Probably we wont charge you anything for using it, but > > it actually depends on the kind of commercial use that you are going to do > > with ssyslog. > > Typically, Walnut Creek CDROM is an example: they partly sponsor > the FreeBSD project, and they sell the FreeBSD CD-ROMs for $39, > but FreeBSD is also available anywhere by ftp. > (This is comparable to Infomagic CDs of Linux, for instance). > > What happens then ? Of course, the "ports" mechanism > of FreeBSD will allow for easy retrieval of the sources, eventual > patching, compiling and installation of the resulting binaries. > > But what about a binary distribution, as a "package" (pre-bundled > .tar.gz with the binaries ready-to-run) ? > > Thank you for any further input. There is no problem including ssyslog in the FreeBSD..Walnut Creek or any other distrib. What we ask you to is to include the sources in case of distributing the binaries. I'll be sending you a FreeBSD port soon. > > thank you very much and I'm very glad you liked our ssyslog. > > Well, we've needed something like it for some time -- if you send > me a port, I will see to it that it is integrated in the ports-collection. > [...] -----End of forwarded message----- -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- "Pluto placed his bad dog at the entrance of Hades to keep the dead IN and the living OUT! The archetypical corporate firewall?" - S. Kelly Bootle, about Cerberus ["MYTHOLOGY", in Marutukku distrib] - From owner-freebsd-current Mon Feb 2 04:05:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19899 for current-outgoing; Mon, 2 Feb 1998 04:05:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA19891 for ; Mon, 2 Feb 1998 04:05:00 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg by adelphi.physics.adelaide.edu.au (5.65/AndrewR-930902) id AA05232; Mon, 2 Feb 1998 22:34:57 +1030 Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA11736; Mon, 2 Feb 1998 22:36:04 +1030 Date: Mon, 2 Feb 1998 22:36:04 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: current problems - false alarm? Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" After a recent cvsup back to dec 23 (the "last stable current" before John's recent fixes to the problems of early January), my problems with spurious sig-11s remained - the last time I ran this era kernel everything was fine. So basically this is what has happened to my system in the past month or so: pre-dec 23, everything fine. post-dec 23, imake SIGBUSes, etc cvsupped back to dec 23, problems solved mailing list indicated -current problems may be fixed, I cvsup back to latest tree, suffer spontaneous coredumps, compilation failures, etc. cvsup back to dec 23, problems remain. What I didnt mention earlier (deliberately - to avoid charges of "ah, well, thats /obviously/ your problem then" - I only spoke up after others had reported the same phenomenon :) was that I was running an overclocked P120 at 133. At about the time I cvsupped back to the latest tree, we were going through the height of summer (and still are, for that matter :) I'm guessing the poor motherboard didnt like living in temperatures of 30C as it sometimes is here in my non-airconditioned computer room :/ (I hadnt had any problems at all in the months before summer when I was running at this speed). I dropped back to 120, and the dec 23 sources compiled fine (did a complete make world; before it couldnt even finish compiling gcc). I'm now in the process of make worlding the latest source tree, but I suspect my problems might be fixed for now. John: sorry to have caused any unnecessary frustration - I guess you can cross this data point off your list. Out of interest, I wonder if any of the other problem systems were overclocked and/or in the southern hemisphere? :-) Kris WOWBO /\ . Through the darkness of future past, /\ . BWOWB OBWOW /##\/#\ The Magician longs to see. /##\/#\ BOBWO WBOBW / \ One chance out between two worlds, / \ OWBOB WOWBO / \ Fire, Walk with me! / \ BWOWB From owner-freebsd-current Mon Feb 2 09:59:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01643 for current-outgoing; Mon, 2 Feb 1998 09:59:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sendero.simon-shapiro.org (sendero-fxp0.Simon-Shapiro.ORG [206.190.148.34]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA01598 for ; Mon, 2 Feb 1998 09:59:14 -0800 (PST) (envelope-from shimon@sendero-fxp0.simon-shapiro.org) Received: (qmail 24849 invoked by uid 1000); 30 Jan 1998 23:57:47 -0000 Message-ID: X-Mailer: XFMail 1.3-alpha-012698 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 30 Jan 1998 15:57:47 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Jaye Mathisen Subject: Re: -current, goliath, smp -- problems Cc: current , Steve Passe , Alex , Jason Evans Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On 11-Dec-97 Jaye Mathisen wrote: > > > On Tue, 9 Dec 1997, Jason Evans wrote: > >> On Mon, 8 Dec 1997, Alex wrote: >> in the neighborhood of 500 MB/sec, which is enough to feed 4 processors, >> but quite inadequate for 8. So, even though there are twice as many >> processors, the performance gain is not impressive. >> >> If there's anyone else out there that knows any better, please correct >> me. >> =) > > While I can't correct you, I have a couple DEC ZX6000's, that when using > the add-on memory boards, so there's something like 4GB of SIMMS, the > memory path becomes 256bit wide, 4 way interleaved, and runs at some > hellacious rate, and I remember the memory bandwidth being significantly > higher than 500MB/s. A number I remember for the P6 bus is 562MB/Sec, as far as the P6 bus is converned. Regardless of the DRAM memory bus itself. > > Heck, if somebody knows of some memory benchmarking software, I'd be > happy > to try it out. > ---------- Sincerely Yours, Simon Shapiro Shimon@Simon-Shapiro.ORG Voice: 503.799.2313 From owner-freebsd-current Mon Feb 2 10:39:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA08488 for current-outgoing; Mon, 2 Feb 1998 10:39:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from iconmail.bellatlantic.net (iconmail.bellatlantic.net [199.173.162.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA08468; Mon, 2 Feb 1998 10:39:41 -0800 (PST) (envelope-from dmm125@bellatlantic.net) Received: from myname.my.domain (client201-122-21.bellatlantic.net [151.201.122.21]) by iconmail.bellatlantic.net (IConNet Sendmail) with SMTP id NAA07502; Mon, 2 Feb 1998 13:39:40 -0500 (EST) Date: Mon, 2 Feb 1998 13:38:53 +0000 (GMT) From: Donn Miller X-Sender: dmm125@myname.my.domain To: current@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: netscape/swap_pager causing problems with syscons Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" This problem was alluded to before. When running X windows, say you start netscape. Then you run out of swap space. What happens next is that X windows lock the computer solid, or X windows crashes, leaving me with a blank screen. None of the virtual terminals work then, but I know the system is still running, because ctrl+alt+delete reboots (shuts down) the system. But I still see nothing on the screen. Jordan hinted to this as a problem with syscons in one posting I saw. I would have to agree. In general, running out of swap space with netscape and X running wrecks havoc on syscons. I was wondering if anyone has experience with this problem and a possible solution as to how to get syscons responding again. I can't login by way of serial console so I guess the only choice is to just ctrl+alt+delete Thank you Donn From owner-freebsd-current Mon Feb 2 10:44:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA09353 for current-outgoing; Mon, 2 Feb 1998 10:44:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailhost (user-38lcbjh.dialup.mindspring.com [209.86.46.113]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA09345 for ; Mon, 2 Feb 1998 10:44:24 -0800 (PST) (envelope-from rlb@mindspring.com) Received: from mindspring.com by mailhost with smtp (Smail3.1.29.1 #1) id m0xzQqS-000G5UC; Mon, 2 Feb 98 13:43 EST Message-ID: <34D613E8.3C3D3522@mindspring.com> Date: Mon, 02 Feb 1998 13:43:52 -0500 From: Ron Bolin X-Mailer: Mozilla 4.04 [en] (X11; I; SunOS 5.6 i86pc) MIME-Version: 1.0 To: FreeBSD Current Mailing List Subject: Current and X11R6 Signal 11 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I am back running current as of 1-31-98 cvsup. I am no longer experiencing X server signal 11 aborts. This is because I stopped the 2.11 version of xscreensaver from running. I'll have to find out which screensaver program makes the server abort and report back to see if anyone else has experienced the problem. Ron -- ------------------------------------------------------------------------------- Ron Bolin, Sr. Software Eng, NetChannel Web: http://www.netchannel.net E-mail: rbolin@netchannel.net Web: http://www.gsu.edu/~gs01rlb Ph: 770-729-2929 Ext 249 Hm: 770-992-8877 Web: http://www.mindspring.com/~rlb ------------------------------------------------------------------------------- From owner-freebsd-current Mon Feb 2 11:44:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24745 for current-outgoing; Mon, 2 Feb 1998 11:44:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA24704 for ; Mon, 2 Feb 1998 11:44:02 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA00727; Mon, 2 Feb 1998 14:43:46 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802021943.OAA00727@dyson.iquest.net> Subject: Re: Current and X11R6 Signal 11 In-Reply-To: <34D613E8.3C3D3522@mindspring.com> from Ron Bolin at "Feb 2, 98 01:43:52 pm" To: rlb@mindspring.com (Ron Bolin) Date: Mon, 2 Feb 1998 14:43:46 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Ron Bolin said: > I am back running current as of 1-31-98 cvsup. I am no longer > experiencing X server > signal 11 aborts. This is because I stopped the 2.11 version of > xscreensaver from running. > > I'll have to find out which screensaver program makes the server abort > and report back to > see if anyone else has experienced the problem. > It might be that the screensaver just barely pushes the pageout daemon into operation. There is a deadlock that I now have a traceback for, that will take more than 10mins, but less than 2Hrs to fix. I'll probably start working on it in a few hours. (It is an algorithmic problem, and not a wierd timing problem, so it should be relatively easy to fix.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Feb 2 13:34:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12866 for current-outgoing; Mon, 2 Feb 1998 13:34:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chico.franken.de (dns.franken.de [193.175.24.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA12849 for ; Mon, 2 Feb 1998 13:34:44 -0800 (PST) (envelope-from scratchy@yavin.franken.de) Received: by chico.franken.de via sendmail with stdio id for current@FreeBSD.ORG; Mon, 2 Feb 1998 22:34:39 +0100 (MET) (Smail-3.2 1996-Jul-4 #2 built DST-Sep-8) Received: from vulcan.franken.de(194.94.248.10) via SMTP by chico, id smtpd029715; Mon Feb 2 22:34:32 1998 Received: from yavin.franken.de (yavin.franken.de [194.94.248.13]) by vulcan.franken.de (8.8.8/8.8.5) with ESMTP id WAA00931 for ; Mon, 2 Feb 1998 22:34:39 +0100 (CET) Received: from yavin.franken.de (localhost [127.0.0.1]) by yavin.franken.de (8.8.8/8.8.5) with ESMTP id WAA04759 for ; Mon, 2 Feb 1998 22:33:47 +0100 (CET) Message-Id: <199802022133.WAA04759@yavin.franken.de> X-Mailer: exmh version 2.0.1 12/23/97 To: current@FreeBSD.ORG Subject: current is still freezing... Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Feb 1998 22:33:46 +0100 From: Volker Paepcke Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hi John! I would like to give you some more hints and feedback to find the "freezing" bug :-) I'm know testing the SMP-kernel since 20th Jan almost every day, and I have the same problem all the time: Running X and under heavy load the system freezes, the screen doesn't update anymore, the mouse freezes a few seconds later and ca. at the same time the disks stop working. There is no panic (I'm using a COM-Console) and I can't call the DDB, only a ping still works. My machine is running very stable under FBSD-stable (of course :-) and relativly stable with an old kernel from december. I can't reproduce the freezing X-bug with an old SMP-kernel! To reproduce the X-freeze I'm compiling a kernel with -j10 in the background, running some java applets with the new jdk1.1.5 port (which is very nice btw) and an xv showing some jpegs in an automatic loop. Under this load, the system freezes after only a few minutes. Under normal load I can work for many hours without a crash (I'm doing some java-development with xemacs, hotjava, netscape und jdk1.1.5) With your speed improvements lately I can run make buildworld now in less than an hour (options: -j8 -DNOPROFILE -DNOCLEAN -DNOTCL, /usr/src and /usr/obj on different disks (sd1 and sd2) mounted with async and noatime option), great work!! hardware: ========= Tyan Titan Pro dual PPRO (200Mhz, 256KB) Adpatec 2940 64MB EDO-Ram Matrox Millenium 4MB 3COM 3C595 Fast Etherlink III PCI 3COM 3C509 Etherlink III Hauppauge WinCast/TV, Temic PAL tuner SoundBlaster 16 PNP dmesg: ====== Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Mon Feb 2 20:45:05 CET 1998 scratchy@yavin.franken.de:/sd2/src/sys/compile/YAVIN-SMP CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 67108864 (65536K bytes) avail memory = 62574592 (61108K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 bktr0: rev 0x12 int a irq 12 on pci0.10.0 Hauppauge WinCast/TV, Temic PAL tuner. ahc0: rev 0x00 int a irq 19 on pci0.11.0 ahc0: aic7870 Single Channel, SCSI Id=7, 16/255 SCBs scbus0 at ahc0 bus 0 ahc0: target 0 Tagged Queuing Device sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 1169MB (2395980 512 byte sectors) sd0: with 2448 cyls, 14 heads, and an average 69 sectors/track ahc0: target 1 Tagged Queuing Device sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 2050MB (4199760 512 byte sectors) sd1: with 3907 cyls, 10 heads, and an average 107 sectors/track ahc0: target 2 Tagged Queuing Device sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access 4341MB (8890760 512 byte sectors) sd2: with 5899 cyls, 10 heads, and an average 150 sectors/track vx0: <3COM 3C595 Fast Etherlink III PCI> rev 0x00 int a irq 18 on pci0.12.0 utp/tx[*tx*] address 00:a0:24:59:d4:00 vga0: rev 0x01 int a irq 17 on pci0.13.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 flags 0x10 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 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp/bnc[*BNC*] address 00:60:97:38:ff:1f npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: APIC_IO: routing 8254 via 8259 on pin 0 ccd0-3: Concatenated disk drivers changing root device to sd2a SMP: AP CPU #1 Launched! config: ======= machine "i386" ident YAVIN-SMP maxusers 10 options FAILSAFE options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on wd0 dumps on wd0 options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O cpu "I586_CPU" # aka Pentium(tm) cpu "I686_CPU" # aka Pentium Pro(tm) options "COMPAT_43" options SYSVSHM options SYSVSEM options SYSVMSG options DDB options KTRACE #kernel tracing options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device tun 1 #Tunnel driver (user process ppp(8)) pseudo-device sl 2 #Serial Line IP pseudo-device ppp 2 #Point-to-point protocol options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpfilter) options "TCP_COMPAT_42" #emulate 4.2BSD TCP bugs options FFS #Fast filesystem options NFS #Network File System options "CD9660" #ISO 9660 filesystem options MFS #Memory File System options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options NFS_ROOT #NFS usable as root device controller scbus0 #base SCSI code device sd0 #SCSI disks device st0 #SCSI tapes device cd0 #SCSI CD-ROMs options SCSI_REPORT_GEOMETRY pseudo-device pty 32 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device ccd 4 #Concatenated disk driver controller isa0 options "AUTO_EOI_1" device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr options MAXCONS=16 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines device npx0 at isa? port "IO_NPX" iosiz 0x0 flags 0x0 irq 13 vector npxintr controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 device lpt0 at isa? port? tty irq 7 vector lptintr device sio0 at isa? port "IO_COM1" tty flags 0x00 irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty flags 0x10 irq 3 vector siointr options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to device ep0 at isa? port 0x300 net irq 10 vector epintr controller snd0 device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr device sbxvi0 at isa? drq 5 device sbmidi0 at isa? port 0x330 device opl0 at isa? port 0x388 options AHC_TAGENABLE options AHC_SCBPAGING_ENABLE options AHC_ALLOW_MEMIO controller pci0 controller ahc1 device vx0 device bktr0 options COMPAT_LINUX options SHOW_BUSYBUFS # List buffers that prevent root unmount If you want me to test something special or try some new patches I would like to offer my help because I have some time right now! Hope this helps... bye, volker From owner-freebsd-current Mon Feb 2 14:20:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19841 for current-outgoing; Mon, 2 Feb 1998 14:20:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19812; Mon, 2 Feb 1998 14:20:10 -0800 (PST) (envelope-from plm@muon.xs4all.nl) Received: from asterix.xs4all.nl (root@asterix.xs4all.nl [194.109.6.11]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id XAA19281; Mon, 2 Feb 1998 23:20:06 +0100 (MET) Received: from muon.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.8.6/8.8.6) with UUCP id XAA22838; Mon, 2 Feb 1998 23:11:49 +0100 (MET) Received: (from plm@localhost) by muon.xs4all.nl (8.8.8/8.7.3) id XAA07527; Mon, 2 Feb 1998 23:05:09 +0100 (MET) To: Donn Miller Cc: current@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: netscape/swap_pager causing problems with syscons References: From: Peter Mutsaers Date: 02 Feb 1998 23:05:09 +0100 In-Reply-To: Donn Miller's message of Mon, 2 Feb 1998 13:38:53 +0000 (GMT) Message-ID: <87pvl5u0h6.fsf@muon.xs4all.nl> Lines: 30 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" >> On Mon, 2 Feb 1998 13:38:53 +0000 (GMT), Donn Miller >> said: DM> This problem was alluded to before. When running X windows, DM> say you start netscape. Then you run out of swap space. What DM> happens next is that X windows lock the computer solid, or X DM> windows crashes, leaving me with a blank screen. None of the DM> virtual terminals work then, but I know the system is still DM> running, because ctrl+alt+delete reboots (shuts down) the DM> system. But I still see nothing on the screen. The problem that I reported before is not this one: I'm sure my swapspace was not depleted, and also the lock is thus that I get a sponaneous reboot (no ctrl+alt+delete needed). Last night I was working from an X-terminal (remotely) on my computer, again with netscape, emacs and lots of other windows at the same time open. The only difference: no X running locally, and also no mouse events on the mousedriver. There was no crash at all. I suspect the problem is with the psm0 driver, because since I started to use a PS/2 mouse instead of a serial one it seems to have started; but that might be coincidence and maybe the X server is causing it. -- /\_/\ ( o.o ) Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know ) ^ ( plm@xs4all.nl | the Netherlands | what I'm doing. From owner-freebsd-current Mon Feb 2 15:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02481 for current-outgoing; Mon, 2 Feb 1998 15:11:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lst01.wxs.nl (lst01.wxs.nl [195.121.6.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02473 for ; Mon, 2 Feb 1998 15:11:01 -0800 (PST) (envelope-from karl@mcs.net) Date: Mon, 2 Feb 1998 15:11:01 -0800 (PST) From: karl@mcs.net Message-Id: <199802022311.PAA02473@hub.freebsd.org> Received: from [195.121.6.61] by lst01.wxs.nl (Netscape Messaging Server 3.0) with SMTP id AAA6564 for ; Mon, 2 Feb 1998 23:55:12 +0100 Received: from mailhost.pi.net ([145.220.3.9]) by smtp01.wxs.nl (Netscape Messaging Server 3.5) with ESMTP id AAA176B for ; Sat, 31 Jan 1998 06:39:07 +0100 Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by mailhost.pi.net (8.8.3/8.7.1) with ESMTP id GAA20956 for ; Sat, 31 Jan 1998 06:38:55 +0100 (MET) Posted-Date: Sat, 31 Jan 1998 06:38:55 +0100 (MET) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA18665; Fri, 30 Jan 1998 21:38:18 -0800 (PST) (envelope-from owner-freebsd-current) Received: by hub.freebsd.org (bulk_mailer v1.6); Fri, 30 Jan 1998 21:36:07 -0800 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18188 for current-outgoing; Fri, 30 Jan 1998 21:36:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18182 for ; Fri, 30 Jan 1998 21:36:05 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id XAA05626 for ; Fri, 30 Jan 1998 23:36:05 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id XAA22835; Fri, 30 Jan 1998 23:36:04 -0600 (CST) Message-ID: <19980130233604.57426@mcs.net> Date: Fri, 30 Jan 1998 23:36:04 -0600 From: Karl Denninger To: current@FreeBSD.ORG Subject: RAID controllers - folks, check this thing out Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Remember a bit ago I was asking about RAID controllers? To: undisclosed-recipients:; Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Well, I found one. Talk to Pacific Computer Expansions, a gentleman by the name of Warren at 800-458-5058. You want the CRD-5440. This is a RAID 0, 0+1, 4 or 5 free-standing SCSI device. It accepts cache memory, and also has battery backup capabilities (attach a 6V Gelcel to it). I have MEASURED *filesystem* I/O rates in excess of 10MB (yes, that is megaBYTES/second) through this thing on a 5-disk array running RAID 5 doing *WRITES*. RAW I/O is considerably faster, as you might expect, and reads are even faster. Reads appear to be limted by the Ultra SCSI interface. This thing has 4 SCSI channels; any number can be delegated to disk and/or host use. Its ultra/wide, and comes in both a differential and single-ended version. Fits in a half-height drive bay (!), powered by a 40Mhz MIPS R3000 processor. It accepts one or two 72-pin SIMMs with up to 512MB (!) of cache memory; the cache, needless to say, grossly improves the performance, especially in a read-intensive environment. It has both a front panel and serial interface (you need to hook up a terminal to configure it, but alarm reporting and rebuild control can be done from the front panel). One catch - you MUST HAVE either a UPS interfaced to this, or a gelcell. The reason is the cache RAM - without one of those two it will refuse to go "online", because a power loss will screw you badly. With the UPS interfaced to it the "low power alarm" will quiesce the host channel and flush the cache, then shut down the controller - leading to a safe power-down. If you have the battery, then a power loss is also not catastrophic (as long as the backup lasts at least). The controller can handle up to 45 devices (!) in multiple RAID sets, appears as a single target per host channel, and can be partitioned to show multiple LUNs if you'd like. Both hot and warm spare capabilities are supported. FreeBSD will boot from it just like any other disk. Right now I have a ~30GB "disk" configured on this thing - 5 9G drives in a Raid 5 configuration. It works right out of the box. Its about a $2500 device, but given what it does, and the performance levels it attains, its VERY reasonable. I'm ordering six more of these for our server farm next week; for the money its basically impossible to beat the performance and operational capabilities, at least from what I've seen so far. In the area of "small" RAID adapters I've not seen anything that can come anywhere close to this thing's performance levels. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly to FULL DS-3 Service | NEW! K56Flex support on ALL modems Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost From owner-freebsd-current Mon Feb 2 15:13:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02857 for current-outgoing; Mon, 2 Feb 1998 15:13:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02847 for ; Mon, 2 Feb 1998 15:12:59 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id JAA21350; Tue, 3 Feb 1998 09:42:42 +1030 (CST) Message-Id: <199802022312.JAA21350@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Kris Kennaway cc: current@FreeBSD.ORG Subject: Re: current problems - false alarm? In-reply-to: Your message of "Mon, 02 Feb 1998 22:36:04 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Feb 1998 09:42:42 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > John: sorry to have caused any unnecessary frustration - I guess you can > cross this data point off your list. Out of interest, I wonder if any of > the other problem systems were overclocked and/or in the southern > hemisphere? :-) My Cyrix 6x86 166+ isn't over clocked, but I live in Adelaide :) I was getting sigsev/sigbus when compiling, but going back to Dec 20 fixed them... Weird.. Might be the phase of the moon =) --------------------------------------------------------------------- |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 | --------------------------------------------------------------------- From owner-freebsd-current Mon Feb 2 15:29:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05826 for current-outgoing; Mon, 2 Feb 1998 15:29:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05788 for ; Mon, 2 Feb 1998 15:29:43 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id JAA21717 for ; Tue, 3 Feb 1998 09:59:22 +1030 (CST) Message-Id: <199802022329.JAA21717@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: current@FreeBSD.ORG Subject: IJPPP stuff Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Feb 1998 09:59:21 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hi, I just recently got a new internet connection, and I have managed to get IJPPP to talk to it, but I had to diable LQR's, otherwise it would hang up about 10 seconds after making a connection. What I think is happening is that since the other end is denying LQR's, IJPPP isn't receiving them, and since I haven't explicitly disabled them, hanging up after a certain timeout. IMO this behaviour is a bit dubious :) --------------------------------------------------------------------- |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 | --------------------------------------------------------------------- From owner-freebsd-current Mon Feb 2 15:47:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10360 for current-outgoing; Mon, 2 Feb 1998 15:47:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA10347 for ; Mon, 2 Feb 1998 15:47:47 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xzVaO-0006U7-00; Mon, 2 Feb 1998 15:47:33 -0800 Date: Mon, 2 Feb 1998 15:47:30 -0800 (PST) From: Tom To: "Daniel O'Connor" cc: current@FreeBSD.ORG Subject: Re: IJPPP stuff In-Reply-To: <199802022329.JAA21717@cain.gsoft.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Tue, 3 Feb 1998, Daniel O'Connor wrote: > Hi, > I just recently got a new internet connection, and I have managed to get IJPPP > to talk to it, but I had to diable LQR's, otherwise it would hang up about 10 > seconds after making a connection. > What I think is happening is that since the other end is denying LQR's, IJPPP > isn't receiving them, and since I haven't explicitly disabled them, hanging up > after a certain timeout. > IMO this behaviour is a bit dubious :) Not necessarily. A common terminal server brand, running old software will accept LQR negotiation but won't always respond to LQR requests. So few implementations actually default to LQR on, or even support LQR this was never seen as much of problem. I suspect that the ISP in question is using Livingston Portmasters with pre-3.7.2 software. If so, they upgrade for this and other reasons. > --------------------------------------------------------------------- > |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 | > --------------------------------------------------------------------- > Tom From owner-freebsd-current Mon Feb 2 15:49:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10746 for current-outgoing; Mon, 2 Feb 1998 15:49:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA10724 for ; Mon, 2 Feb 1998 15:49:23 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA18227; Tue, 3 Feb 1998 08:35:37 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id IAA10089; Tue, 3 Feb 1998 08:43:19 +0900 (JST) Message-Id: <199802022343.IAA10089@zodiac.mech.utsunomiya-u.ac.jp> To: Donn Miller Cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: netscape/swap_pager causing problems with syscons In-Reply-To: Your message of "Mon, 02 Feb 1998 13:38:53 GMT." References: Date: Tue, 03 Feb 1998 08:43:13 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" When the X server crashes badly, there is no way for syscons to recover the screen. The X server manipulates various registers on the video chip to get acceleration. Syscons knows only about the standard VGA registers, thus, it is impossible for it to set appropriate values to all those extended registers and get the video card back into the text mode. Syscons could program the standard registers and pretend the screen came back to the text mode in the event of X crash. But, this would be disastrous not only that the screen wouldn't probably be restored because of extended registers, but also that leaving the video chip in an arbitrary state (the standard registers programmed to the text mode while the extended registers programmed to the graphics mode) might damage your hardware (monitor)! That's my understanding. I don't think we would like to break the user's monitor by running a piece of code which is known to be insufficient. I guess it's time to ask XFree86 people to write a utility to restore video state after the X server crash. Afterall, information is there in XF86Config; which video chip we are dealing with... # When I find time, I might do it myself. But, I don't promise :-) Kazu >This problem was alluded to before. When running X windows, say you start >netscape. Then you run out of swap space. What happens next is that X >windows lock the computer solid, or X windows crashes, leaving me with a >blank screen. None of the virtual terminals work then, but I know the >system is still running, because ctrl+alt+delete reboots (shuts down) the >system. But I still see nothing on the screen. > >Jordan hinted to this as a problem with syscons in one posting I saw. I >would have to agree. In general, running out of swap space with netscape >and X running wrecks havoc on syscons. I was wondering if anyone has >experience with this problem and a possible solution as to how to get >syscons responding again. I can't login by way of serial console so I >guess the only choice is to just ctrl+alt+delete > >Thank you > > Donn From owner-freebsd-current Mon Feb 2 15:49:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10825 for current-outgoing; Mon, 2 Feb 1998 15:49:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA10754 for ; Mon, 2 Feb 1998 15:49:28 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: by outmail.utsunomiya-u.ac.jp id AA18059; Tue, 3 Feb 1998 08:42:49 +0900 Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id IAA10205; Tue, 3 Feb 1998 08:50:27 +0900 (JST) Message-Id: <199802022350.IAA10205@zodiac.mech.utsunomiya-u.ac.jp> To: Peter Mutsaers Cc: Donn Miller , current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: netscape/swap_pager causing problems with syscons In-Reply-To: Your message of "02 Feb 1998 23:05:09 +0100." <87pvl5u0h6.fsf@muon.xs4all.nl> References: <87pvl5u0h6.fsf@muon.xs4all.nl> Date: Tue, 03 Feb 1998 08:50:21 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" >The problem that I reported before is not this one: I'm sure my >swapspace was not depleted, and also the lock is thus that I get a >sponaneous reboot (no ctrl+alt+delete needed). > >Last night I was working from an X-terminal (remotely) on my computer, >again with netscape, emacs and lots of other windows at the same time >open. > >The only difference: no X running locally, and also no mouse events on >the mousedriver. There was no crash at all. > >I suspect the problem is with the psm0 driver, because since I started >to use a PS/2 mouse instead of a serial one it seems to have started; >but that might be coincidence and maybe the X server is causing it. Would you possibly send me `dmesg' output after you boot the system with `-v' boot option so that I can know the state of the psm0 driver? Do you run `moused'? Or, do you let the X server access the psm0 device directly? Do you think you can reproduce your problem by running moused on psm0, and login from the remote X-terminal and do some heavy work? I prefer you twiddle the PS/2 mouse at the same time if possible. Kazu yokota@freebsd.org From owner-freebsd-current Mon Feb 2 15:53:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11981 for current-outgoing; Mon, 2 Feb 1998 15:53:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11974 for ; Mon, 2 Feb 1998 15:53:19 -0800 (PST) (envelope-from doconnor@cain.gsoft.com.au) Received: from cain (localhost [127.0.0.1]) by cain.gsoft.com.au (8.8.8/8.6.9) with ESMTP id KAA23384; Tue, 3 Feb 1998 10:22:41 +1030 (CST) Message-Id: <199802022352.KAA23384@cain.gsoft.com.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom cc: "Daniel O'Connor" , current@FreeBSD.ORG Subject: Re: IJPPP stuff In-reply-to: Your message of "Mon, 02 Feb 1998 15:47:30 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Feb 1998 10:22:41 +1030 From: "Daniel O'Connor" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > > after a certain timeout. > > IMO this behaviour is a bit dubious :) > Not necessarily. A common terminal server brand, running old software > will accept LQR negotiation but won't always respond to LQR requests. So > few implementations actually default to LQR on, or even support LQR this > was never seen as much of problem. Hmm, but the log messages from PPP say the they did not negotiate LQR's. The provider is Telstra, and AFAIK they use Cisco's. --------------------------------------------------------------------- |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 | --------------------------------------------------------------------- From owner-freebsd-current Mon Feb 2 16:28:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16437 for current-outgoing; Mon, 2 Feb 1998 16:28:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16256; Mon, 2 Feb 1998 16:27:03 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA00389; Mon, 2 Feb 1998 17:32:52 -0500 (EST) (envelope-from toor) Message-Id: <199802022232.RAA00389@dyson.iquest.net> Subject: Re: netscape/swap_pager causing problems with syscons In-Reply-To: <87pvl5u0h6.fsf@muon.xs4all.nl> from Peter Mutsaers at "Feb 2, 98 11:05:09 pm" To: plm@xs4all.nl (Peter Mutsaers) Date: Mon, 2 Feb 1998 17:32:51 -0500 (EST) Cc: dmm125@bellatlantic.net, current@FreeBSD.ORG, bugs@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Peter Mutsaers said: > The problem that I reported before is not this one: I'm sure my > swapspace was not depleted, and also the lock is thus that I get a > sponaneous reboot (no ctrl+alt+delete needed). I am working on the problem, and understand and am working the problem right now. Should be a reboot or two away from working :-). The problem also exists in 2.2.X (I think.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Feb 2 16:41:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18037 for current-outgoing; Mon, 2 Feb 1998 16:41:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA18032 for ; Mon, 2 Feb 1998 16:41:20 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xzWQO-0004Nt-00; Mon, 2 Feb 1998 16:41:16 -0800 Date: Mon, 2 Feb 1998 16:41:14 -0800 (PST) From: Tom To: Karl Denninger cc: current@FreeBSD.ORG Subject: Re: RAID controllers - folks, check this thing out In-Reply-To: <19980130233604.57426@mcs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Fri, 30 Jan 1998, Karl Denninger wrote: > Remember a bit ago I was asking about RAID controllers? > > Well, I found one. > > Talk to Pacific Computer Expansions, a gentleman by the name of Warren at > 800-458-5058. > > You want the CRD-5440. > > This is a RAID 0, 0+1, 4 or 5 free-standing SCSI device. It accepts cache > memory, and also has battery backup capabilities (attach a 6V Gelcel to it). Just a standard SCSI-to-SCSI RAID device. These have been around for years. DEC, Mylex, and others have been making them for some time. > I have MEASURED *filesystem* I/O rates in excess of 10MB (yes, that is > megaBYTES/second) through this thing on a 5-disk array running RAID 5 > doing *WRITES*. Details? I can get speeds up to 50MB/s with my DPT, but it doesn't mean it is representative of "normal" use. RAID systems need to be optimized for your typical use. On large sequentional writes, my current DPT controler only gets about 5MB/s, but it screams on random-access read-write. PCI-SCSI RAID controllers are generally faster than SCSI-SCSI. I'm sure that a DPT card would bury the CRD. SCSI-to-SCSI controllers bring up the question of what SCSI card to use. The 2940UW is probably the fastest UW card, but the driver isn't very robust yet (maybe the CAM stuff is better). The DPT driver has no such problems. I've got two nearly identical servers, one with a 3940 and one with a DPT PM334. The 3940 has a SCSI hang every 4 to 6 weeks. Tom From owner-freebsd-current Mon Feb 2 17:10:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA22302 for current-outgoing; Mon, 2 Feb 1998 17:10:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA22286; Mon, 2 Feb 1998 17:10:26 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id SAA19151; Mon, 2 Feb 1998 18:07:45 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA00314; Mon, 2 Feb 1998 18:07:42 -0700 Date: Mon, 2 Feb 1998 18:07:42 -0700 Message-Id: <199802030107.SAA00314@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: dyson@FreeBSD.ORG Cc: plm@xs4all.nl (Peter Mutsaers), dmm125@bellatlantic.net, current@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: netscape/swap_pager causing problems with syscons In-Reply-To: <199802022232.RAA00389@dyson.iquest.net> References: <87pvl5u0h6.fsf@muon.xs4all.nl> <199802022232.RAA00389@dyson.iquest.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > > The problem that I reported before is not this one: I'm sure my > > swapspace was not depleted, and also the lock is thus that I get a > > sponaneous reboot (no ctrl+alt+delete needed). > > I am working on the problem, and understand and am working the problem > right now. Should be a reboot or two away from working :-). The problem > also exists in 2.2.X (I think.) Cool. So does that mean you're going to provide a fix to the 2.2.* code-base? (Last time I asked, you told me to go ahead and backport the changes (FAT CHANCE!), but I'm hoping that won't happen this time. :) Nate From owner-freebsd-current Mon Feb 2 17:18:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24050 for current-outgoing; Mon, 2 Feb 1998 17:18:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23993; Mon, 2 Feb 1998 17:18:43 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id UAA02460; Mon, 2 Feb 1998 20:18:31 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802030118.UAA02460@dyson.iquest.net> Subject: Re: netscape/swap_pager causing problems with syscons In-Reply-To: <199802030107.SAA00314@mt.sri.com> from Nate Williams at "Feb 2, 98 06:07:42 pm" To: nate@mt.sri.com (Nate Williams) Date: Mon, 2 Feb 1998 20:18:31 -0500 (EST) Cc: dyson@FreeBSD.ORG, plm@xs4all.nl, dmm125@bellatlantic.net, current@FreeBSD.ORG, bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Nate Williams said: > > > The problem that I reported before is not this one: I'm sure my > > > swapspace was not depleted, and also the lock is thus that I get a > > > sponaneous reboot (no ctrl+alt+delete needed). > > > > I am working on the problem, and understand and am working the problem > > right now. Should be a reboot or two away from working :-). The problem > > also exists in 2.2.X (I think.) > > Cool. So does that mean you're going to provide a fix to the 2.2.* > code-base? (Last time I asked, you told me to go ahead and backport the > changes (FAT CHANCE!), but I'm hoping that won't happen this time. :) > Try out the change I just made to swap_pager for -current. If the motivation is solid enough, I can give the 2.2.5-2.2.6 changes a try, but it is exceedingly difficult for me to manage my machines as they are now. I have to run other OSen also. When I run other U**X clones, it makes me realize, even with our bugs, our stuff is much more advanced (bugfixes and robust.) There is a serious difference in personalities amongst the various U**X clones!!! -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Feb 2 17:30:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26098 for current-outgoing; Mon, 2 Feb 1998 17:30:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (root@alex-va-n008c243.moon.jic.com [206.156.18.253]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25967; Mon, 2 Feb 1998 17:29:35 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id UAA16428; Mon, 2 Feb 1998 20:28:07 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Donn Miller cc: current@FreeBSD.ORG, bugs@FreeBSD.ORG From: "Gary Palmer" Subject: Re: netscape/swap_pager causing problems with syscons In-reply-to: Your message of "Mon, 02 Feb 1998 13:38:53 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Feb 1998 20:28:06 -0500 Message-ID: <16424.886469286@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Donn Miller wrote in message ID : > Jordan hinted to this as a problem with syscons in one posting I saw. I > would have to agree. In general, running out of swap space with netscape > and X running wrecks havoc on syscons. I was wondering if anyone has > experience with this problem and a possible solution as to how to get > syscons responding again. I can't login by way of serial console so I > guess the only choice is to just ctrl+alt+delete The problem is that the X server reprograms the chipset on the video card to do what *it* wants. Syscons has no idea of the original settings, and therefore can't restore them if X exits abnormally (i.e. running out of swap and the kernel killing the server) The only possible solution is telling the console code how to reprogram the video chipset, and making X indirect through the console code for paramater changes. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-current Mon Feb 2 18:15:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02995 for current-outgoing; Mon, 2 Feb 1998 18:15:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02975; Mon, 2 Feb 1998 18:15:09 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id SAA14583; Mon, 2 Feb 1998 18:10:13 -0800 (PST) To: Donn Miller cc: current@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: netscape/swap_pager causing problems with syscons In-reply-to: Your message of "Mon, 02 Feb 1998 13:38:53 GMT." Date: Mon, 02 Feb 1998 18:10:13 -0800 Message-ID: <14579.886471813@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > This problem was alluded to before. When running X windows, say you start > netscape. Then you run out of swap space. What happens next is that X > windows lock the computer solid, or X windows crashes, leaving me with a > blank screen. None of the virtual terminals work then, but I know the > system is still running, because ctrl+alt+delete reboots (shuts down) the > system. But I still see nothing on the screen. > > Jordan hinted to this as a problem with syscons in one posting I saw. I Nope, it's not a "problem" with syscons - it's just what happens when an X server is rudely shot down and has no chance to clean up. And I'm sure that Terry will have some suggestion about how state changes should be pushed and restored in syscons but it's unlikely that this will every happen unless somebody actually figures out how to implement it and has the free time to do the work involved. Don't hold your breath though and allocate more swap space instead. ;-) Jordan From owner-freebsd-current Mon Feb 2 18:22:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03974 for current-outgoing; Mon, 2 Feb 1998 18:22:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03957; Mon, 2 Feb 1998 18:22:07 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA02831; Mon, 2 Feb 1998 21:20:19 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802030220.VAA02831@dyson.iquest.net> Subject: Re: netscape/swap_pager causing problems with syscons In-Reply-To: <14579.886471813@time.cdrom.com> from "Jordan K. Hubbard" at "Feb 2, 98 06:10:13 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 2 Feb 1998 21:20:19 -0500 (EST) Cc: dmm125@bellatlantic.net, current@FreeBSD.ORG, bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Jordan K. Hubbard said: > > This problem was alluded to before. When running X windows, say you start > > netscape. Then you run out of swap space. What happens next is that X > > windows lock the computer solid, or X windows crashes, leaving me with a > > blank screen. None of the virtual terminals work then, but I know the > > system is still running, because ctrl+alt+delete reboots (shuts down) the > > system. But I still see nothing on the screen. > > > > Jordan hinted to this as a problem with syscons in one posting I saw. I > > Nope, it's not a "problem" with syscons - it's just what happens when > an X server is rudely shot down and has no chance to clean up. And > I'm sure that Terry will have some suggestion about how state changes > should be pushed and restored in syscons but it's unlikely that this > will every happen unless somebody actually figures out how to > implement it and has the free time to do the work involved. Don't > hold your breath though and allocate more swap space instead. ;-) > This is another need for a transitive closure of the flow graph of execution. :-). -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Mon Feb 2 23:35:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA09233 for current-outgoing; Mon, 2 Feb 1998 23:35:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA09218 for ; Mon, 2 Feb 1998 23:34:58 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.7) with ESMTP id HAA12885; Tue, 3 Feb 1998 07:24:30 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199802030724.HAA12885@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: "Daniel O'Connor" cc: Tom , current@FreeBSD.ORG Subject: Re: IJPPP stuff In-reply-to: Your message of "Tue, 03 Feb 1998 10:22:41 +1030." <199802022352.KAA23384@cain.gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Feb 1998 07:24:29 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > > > > after a certain timeout. > > > IMO this behaviour is a bit dubious :) > > Not necessarily. A common terminal server brand, running old software > > will accept LQR negotiation but won't always respond to LQR requests. So > > few implementations actually default to LQR on, or even support LQR this > > was never seen as much of problem. > Hmm, but the log messages from PPP say the they did not negotiate LQR's. > The provider is Telstra, and AFAIK they use Cisco's. Try getting the current ppp from http://www.FreeBSD.org/~brian and seeing if it continues to get things wrong. If it does, you should use send-pr :-) It *probably* is a bug (although the current ppp doesn't use LQR by default - it must be ``enable''d). > --------------------------------------------------------------------- > |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 | > --------------------------------------------------------------------- > > -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-current Tue Feb 3 00:00:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA14469 for current-outgoing; Tue, 3 Feb 1998 00:00:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Caroline.magnet.mt (caroline.magnet.mt [193.82.255.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA14436 for ; Tue, 3 Feb 1998 00:00:46 -0800 (PST) (envelope-from alex.j.chircop@magnet.mt) Received: from magnet.mt (mail.mitts.net [193.82.255.25]) by Caroline.magnet.mt (8.8.8/8.8.8) with ESMTP id IAA24946; Tue, 3 Feb 1998 08:54:12 +0100 (CET) Message-ID: <003101bd3077$8f1fa860$280e0181@magnet.mt> From: "Alex Chircop" To: "Tom" Cc: Subject: Re: RAID controllers - folks, check this thing out Date: Tue, 3 Feb 1998 08:42:45 +0100 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 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" What drivers are you using for the DPT controllers ? Regards, Alex -----Original Message----- From: Tom To: Karl Denninger Cc: current@FreeBSD.ORG Date: Tuesday, February 03, 1998 2:10 Subject: Re: RAID controllers - folks, check this thing out > >On Fri, 30 Jan 1998, Karl Denninger wrote: > >> Remember a bit ago I was asking about RAID controllers? >> >> Well, I found one. >> >> Talk to Pacific Computer Expansions, a gentleman by the name of Warren at >> 800-458-5058. >> >> You want the CRD-5440. >> >> This is a RAID 0, 0+1, 4 or 5 free-standing SCSI device. It accepts cache >> memory, and also has battery backup capabilities (attach a 6V Gelcel to it). > > Just a standard SCSI-to-SCSI RAID device. These have been around for >years. DEC, Mylex, and others have been making them for some >time. > >> I have MEASURED *filesystem* I/O rates in excess of 10MB (yes, that is >> megaBYTES/second) through this thing on a 5-disk array running RAID 5 >> doing *WRITES*. > > Details? I can get speeds up to 50MB/s with my DPT, but it doesn't mean >it is representative of "normal" use. > > RAID systems need to be optimized for your typical use. On large >sequentional writes, my current DPT controler only gets about 5MB/s, but >it screams on random-access read-write. > > PCI-SCSI RAID controllers are generally faster than SCSI-SCSI. I'm sure >that a DPT card would bury the CRD. > > SCSI-to-SCSI controllers bring up the question of what SCSI card to use. >The 2940UW is probably the fastest UW card, but the driver isn't very >robust yet (maybe the CAM stuff is better). The DPT driver has no such >problems. I've got two nearly identical servers, one with a 3940 and one >with a DPT PM334. The 3940 has a SCSI hang every 4 to 6 weeks. > >Tom > From owner-freebsd-current Tue Feb 3 00:27:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18213 for current-outgoing; Tue, 3 Feb 1998 00:27:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18205; Tue, 3 Feb 1998 00:27:09 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id BAA09720; Tue, 3 Feb 1998 01:27:07 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp02.primenet.com, id smtpd009682; Tue Feb 3 01:27:01 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA03197; Tue, 3 Feb 1998 01:26:56 -0700 (MST) From: Terry Lambert Message-Id: <199802030826.BAA03197@usr08.primenet.com> Subject: Re: netscape/swap_pager causing problems with syscons To: toor@dyson.iquest.net (John S. Dyson) Date: Tue, 3 Feb 1998 08:26:56 +0000 (GMT) Cc: jkh@time.cdrom.com, dmm125@bellatlantic.net, current@FreeBSD.ORG, bugs@FreeBSD.ORG In-Reply-To: <199802030220.VAA02831@dyson.iquest.net> from "John S. Dyson" at Feb 2, 98 09:20:19 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > > Nope, it's not a "problem" with syscons - it's just what happens when > > an X server is rudely shot down and has no chance to clean up. And > > I'm sure that Terry will have some suggestion about how state changes > > should be pushed and restored in syscons but it's unlikely that this > > will every happen unless somebody actually figures out how to > > implement it and has the free time to do the work involved. Don't > > hold your breath though and allocate more swap space instead. ;-) > > This is another need for a transitive closure of the flow graph of > execution. :-). Heh. It's called putting DDX into the kernel. And it's already been implemented... for Linux. It's interesting how much discussion about architecture on these lists finds its way into Linux first... one wonders if FreeBSD people are being abused as the architects for Linux... Demand loadable kernel modules. Generalize reference counting. ELF. Use of ELF sections to implement virtual base classes in g++. Change to a large offset instead of a single page offset so ld.so can be mapped into the image by the exec() rather than by crt0.o Token Ring drivers. SMP. DDX in the kernel. A partidge in a pear tree... 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Tue Feb 3 00:56:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA21411 for current-outgoing; Tue, 3 Feb 1998 00:56:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thunderdome.plutotech.com (thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA21179 for ; Tue, 3 Feb 1998 00:53:38 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id BAA18627; Tue, 3 Feb 1998 01:52:03 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id BAA18707; Tue, 3 Feb 1998 01:52:00 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199802030852.BAA18707@panzer.plutotech.com> Subject: Re: RAID controllers - folks, check this thing out In-Reply-To: <003101bd3077$8f1fa860$280e0181@magnet.mt> from Alex Chircop at "Feb 3, 98 08:42:45 am" To: alex.j.chircop@magnet.mt (Alex Chircop) Date: Tue, 3 Feb 1998 01:52:00 -0700 (MST) Cc: tom@uniserve.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Alex Chircop wrote... > What drivers are you using for the DPT controllers ? > > Regards, > Alex I'm sure he's using the DPT driver written by Simon Shapiro. What other DPT driver is there for FreeBSD? :) (It's in -current now, look in /sys/dev/dpt and /sys/pci/dpt_pci.c and probably a few other places.) Ken -- Kenneth Merry ken@plutotech.com From owner-freebsd-current Tue Feb 3 02:12:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00937 for current-outgoing; Tue, 3 Feb 1998 02:12:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Caroline.magnet.mt (caroline.magnet.mt [193.82.255.26]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA00928 for ; Tue, 3 Feb 1998 02:12:03 -0800 (PST) (envelope-from alex.j.chircop@magnet.mt) Received: from magnet.mt (mail.mitts.net [193.82.255.25]) by Caroline.magnet.mt (8.8.8/8.8.8) with ESMTP id JAA01449; Tue, 3 Feb 1998 09:56:51 +0100 (CET) Message-ID: <000001bd3081$a38a34a0$280e0181@magnet.mt> From: "Alex Chircop" To: "Tom" Cc: Subject: Re: RAID controllers - folks, check this thing out Date: Tue, 3 Feb 1998 08:42:45 +0100 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 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" What drivers are you using for the DPT controllers ? Regards, Alex -----Original Message----- From: Tom To: Karl Denninger Cc: current@FreeBSD.ORG Date: Tuesday, February 03, 1998 2:10 Subject: Re: RAID controllers - folks, check this thing out > >On Fri, 30 Jan 1998, Karl Denninger wrote: > >> Remember a bit ago I was asking about RAID controllers? >> >> Well, I found one. >> >> Talk to Pacific Computer Expansions, a gentleman by the name of Warren at >> 800-458-5058. >> >> You want the CRD-5440. >> >> This is a RAID 0, 0+1, 4 or 5 free-standing SCSI device. It accepts cache >> memory, and also has battery backup capabilities (attach a 6V Gelcel to it). > > Just a standard SCSI-to-SCSI RAID device. These have been around for >years. DEC, Mylex, and others have been making them for some >time. > >> I have MEASURED *filesystem* I/O rates in excess of 10MB (yes, that is >> megaBYTES/second) through this thing on a 5-disk array running RAID 5 >> doing *WRITES*. > > Details? I can get speeds up to 50MB/s with my DPT, but it doesn't mean >it is representative of "normal" use. > > RAID systems need to be optimized for your typical use. On large >sequentional writes, my current DPT controler only gets about 5MB/s, but >it screams on random-access read-write. > > PCI-SCSI RAID controllers are generally faster than SCSI-SCSI. I'm sure >that a DPT card would bury the CRD. > > SCSI-to-SCSI controllers bring up the question of what SCSI card to use. >The 2940UW is probably the fastest UW card, but the driver isn't very >robust yet (maybe the CAM stuff is better). The DPT driver has no such >problems. I've got two nearly identical servers, one with a 3940 and one >with a DPT PM334. The 3940 has a SCSI hang every 4 to 6 weeks. > >Tom > From owner-freebsd-current Tue Feb 3 04:58:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19780 for current-outgoing; Tue, 3 Feb 1998 04:58:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19774 for ; Tue, 3 Feb 1998 04:58:20 -0800 (PST) (envelope-from sasdrq@unx.sas.com) Received: from mozart (markham.southpeak.com [192.58.185.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id HAA02999 for ; Tue, 3 Feb 1998 07:58:18 -0500 (EST) Received: from gamecock.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA08374; Tue, 3 Feb 1998 07:58:17 -0500 Received: by gamecock.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA03314; Tue, 3 Feb 1998 07:58:17 -0500 From: David Quattlebaum Message-Id: <199802031258.AA03314@gamecock.unx.sas.com> Subject: Failure in debug kernel To: freebsd-current@FreeBSD.ORG (current) Date: Tue, 3 Feb 1998 07:58:17 -0500 (EST) X-Mailer: ELM [version 2.5 PL0b1] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I tried to build a debug kernel yesterday and when I booted it, it printed an error and rebooted faster than I could read the screen. This went on until we brought up kernel.old. steps I took to build the kernel (from 3.0-980128-SNAP): o cp GENERIC DEBUG o added "OPTIONS DDB" to DEBUG o config -g DEBUG o make depend && make && make install o reboot o did NOT specify any options to kernel at boot time we wanted to get control when a panic occurred. This is what kernel.old shows at startup: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-980128-SNAP #1: Fri Jan 30 05:37:50 EST 1998 root@mrose.pc.sas.com:/usr/src/sys/compile/FreeBSD CPU: Pentium Pro (264.89-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 268435456 (262144K bytes) vail memory = 258965504 (252896K bytes) Sorry I don't have any more info. Anyone else having problems with a debug kernel. -- David Quattlebaum, (sasdrq@unx.sas.com) < "Weebles wobble but they don't fall down." From owner-freebsd-current Tue Feb 3 05:23:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23409 for current-outgoing; Tue, 3 Feb 1998 05:23:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23404 for ; Tue, 3 Feb 1998 05:23:13 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id IAA01433 for current@freebsd.org; Tue, 3 Feb 1998 08:20:17 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802031320.IAA01433@dyson.iquest.net> Subject: Any feedback on my recent kernel 'fixes' To: current@FreeBSD.ORG Date: Tue, 3 Feb 1998 08:20:17 -0500 (EST) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Is paging more stable? Thanks for any feedback (either way.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Tue Feb 3 08:51:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20691 for current-outgoing; Tue, 3 Feb 1998 08:51:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20631 for ; Tue, 3 Feb 1998 08:50:13 -0800 (PST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id SAA10582; Tue, 3 Feb 1998 18:50:00 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Received: from greenpeace.grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id SAA24704; Tue, 3 Feb 1998 18:49:59 +0200 (SAST) (envelope-from mark@greenpeace.grondar.za) Message-Id: <199802031649.SAA24704@greenpeace.grondar.za> X-Mailer: exmh version 2.0.1 12/23/97 To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Feb 1998 18:49:59 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" "John S. Dyson" wrote: > Is paging more stable? > > Thanks for any feedback (either way.) My GA586DX/SMP w/ 2xP5/200 is very stable right now. A couple of weeks ago it was loking up every day or so. A typical "make world" would have to be restarted. Now, I have an uptime of 3 days (from a new kernel), and it is solid. Thanks! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org From owner-freebsd-current Tue Feb 3 10:56:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA12472 for current-outgoing; Tue, 3 Feb 1998 10:56:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA12466 for ; Tue, 3 Feb 1998 10:56:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA00799; Tue, 3 Feb 1998 10:54:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802031854.KAA00799@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' In-reply-to: Your message of "Tue, 03 Feb 1998 08:20:17 EST." <199802031320.IAA01433@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Feb 1998 10:54:48 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Not sure since I upgraded my memory from 48MB to 98MB so far my PPro looks stable. Earlier on the week prior to you committing the latest round of vm fixes my girlfriend managed to crash the system with netscape -- my wild guess is that it was the swap paging problem althought I have been compiling java over here which caused my system to swap heavily when it had 48MB of main memory and never experienced a crash. Tnks! Amancio From owner-freebsd-current Tue Feb 3 11:24:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16936 for current-outgoing; Tue, 3 Feb 1998 11:24:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.31.78.80]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16922 for ; Tue, 3 Feb 1998 11:24:17 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id OAA02717 for ; Tue, 3 Feb 1998 14:24:01 -0500 (EST) Date: Tue, 3 Feb 1998 14:24:01 -0500 (EST) From: "Matthew N. Dodd" To: current@FreeBSD.ORG Subject: Upper limit on # of CDROM drives? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I've got a -current system (supped earlier today) that I'm messing with and have a number of devices attached to various SCSI busses. ahb0 ST31230N sd0 abh1 none dpt0 NRC MBR-7.4 101 cd0 - cd6 dpt1 4 x XM-4101TA cd7 - cd10 dpt2 2 x RZ55 For whatever reason, only the first of the 4101s is probed. I've tried tweaking DK_NDRIVE in sys/dkstat.h with no success. Am I missing something? By apperances, only 7 devices are configured by /dev/MAKEDEV (I've fixed this as well on my system). The final incarnation of this machine will have more than 28 CD-ROM devices so I'm hoping to resolve this. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ From owner-freebsd-current Tue Feb 3 11:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17819 for current-outgoing; Tue, 3 Feb 1998 11:26:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17813 for ; Tue, 3 Feb 1998 11:26:55 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.7) with SMTP id NAA26015 for ; Tue, 3 Feb 1998 13:26:52 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <00ec01bd30d9$43e59dc0$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: current.freebsd.org unable to connect Date: Tue, 3 Feb 1998 13:23:53 -0600 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 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I tried to connect to the SNAP shot server yesterday and today, and was unable to get a connection. The error I am getting back is: 421 Service not available, remote server has closed connection Is there a problem with the SNAP shot servers? Thanks, Scot From owner-freebsd-current Tue Feb 3 11:33:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18892 for current-outgoing; Tue, 3 Feb 1998 11:33:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18854 for ; Tue, 3 Feb 1998 11:33:32 -0800 (PST) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.8.8/8.8.7) id VAA09531; Tue, 3 Feb 1998 21:33:13 +0200 (SAT) From: John Hay Message-Id: <199802031933.VAA09531@zibbi.mikom.csir.co.za> Subject: Re: current.freebsd.org unable to connect In-Reply-To: <00ec01bd30d9$43e59dc0$c3e0d9cf@admin.westbend.net> from "Scot W. Hetzel" at "Feb 3, 98 01:23:53 pm" To: hetzels@westbend.net (Scot W. Hetzel) Date: Tue, 3 Feb 1998 21:33:13 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > I tried to connect to the SNAP shot server yesterday and today, and was > unable to get a connection. > > The error I am getting back is: > > 421 Service not available, remote server has closed connection > > Is there a problem with the SNAP shot servers? No problem from here: ------------------------------------------------------------------------ zibbi:~ > ftp current.freebsd.org Connected to make.ican.net. 220 make.ican.net FTP server (Version wu-2.4.2-academ[BETA-13](1) Tue May 13 20:09 EDT 1997) ready. 331 Guest login ok, send your complete e-mail address as password. 230 Guest login ok, access restrictions apply. ------------------------------------------------------------------------ John -- John Hay -- John.Hay@mikom.csir.co.za From owner-freebsd-current Tue Feb 3 12:06:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24331 for current-outgoing; Tue, 3 Feb 1998 12:06:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24294 for ; Tue, 3 Feb 1998 12:06:51 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id PAA09191; Tue, 3 Feb 1998 15:06:34 -0500 (EST) Date: Tue, 3 Feb 1998 15:06:33 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Scot W. Hetzel" cc: freebsd-current@FreeBSD.ORG Subject: Re: current.freebsd.org unable to connect In-Reply-To: <00ec01bd30d9$43e59dc0$c3e0d9cf@admin.westbend.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" You should make sure that your machine's reverse lookup is happening OK. The snap server seems to tend toward the "super-paranoid". It nukes mismatches and things that just aren't reversed... Charles Sprickman spork@super-g.com ---- "I'm not a prophet or a stone-age man Just a mortal with potential of a superman I'm living on" -DB On Tue, 3 Feb 1998, Scot W. Hetzel wrote: > I tried to connect to the SNAP shot server yesterday and today, and was > unable to get a connection. > > The error I am getting back is: > > 421 Service not available, remote server has closed connection > > Is there a problem with the SNAP shot servers? > > Thanks, > > Scot > From owner-freebsd-current Tue Feb 3 12:29:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27193 for current-outgoing; Tue, 3 Feb 1998 12:29:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27134 for ; Tue, 3 Feb 1998 12:29:00 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA16223; Tue, 3 Feb 1998 11:57:40 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd016220; Tue Feb 3 11:57:33 1998 Message-ID: <34D775D6.15FB7483@whistle.com> Date: Tue, 03 Feb 1998 11:53:58 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Alex Chircop CC: Tom , current@FreeBSD.ORG Subject: Re: RAID controllers - folks, check this thing out References: <000001bd3081$a38a34a0$280e0181@magnet.mt> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Alex Chircop wrote: > > What drivers are you using for the DPT controllers ? > > Regards, > Alex > > -----Original Message----- the dpt driver is built into -current it is available from simon shapiro for 2.2.x From owner-freebsd-current Tue Feb 3 13:14:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04945 for current-outgoing; Tue, 3 Feb 1998 13:14:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04885 for ; Tue, 3 Feb 1998 13:14:26 -0800 (PST) (envelope-from pst@juniper.net) Received: (from pst@localhost) by red.juniper.net (8.8.5/8.8.5) id NAA21088; Tue, 3 Feb 1998 13:13:18 -0800 (PST) To: Alex A cc: current@FreeBSD.ORG Subject: Re: inetd patch/idea References: From: Paul Traina Date: 03 Feb 1998 13:13:18 -0800 In-Reply-To: garbanzo@hooked.net's message of 26 Jan 98 09:05:03 GMT Message-ID: <7yzpk84ck1.fsf@red.juniper.net> Lines: 9 X-Mailer: Gnus v5.4.37/XEmacs 19.16 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I won't comment on the PID cleanup code. With regard to the sighup code, I inspected it and believe it is incorrect. The "blocked" mask that is passed in all 3 calls to sigvec() specifies a list of signals you want masked while the signal handler is active. See sigvec(2). You WANT SIGHUP to be blocked at that time. Paul From owner-freebsd-current Tue Feb 3 15:41:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28541 for current-outgoing; Tue, 3 Feb 1998 15:41:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28536 for ; Tue, 3 Feb 1998 15:41:50 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA26880; Tue, 3 Feb 1998 16:41:48 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA03098; Tue, 3 Feb 1998 16:41:47 -0700 Date: Tue, 3 Feb 1998 16:41:47 -0700 Message-Id: <199802032341.QAA03098@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "John S. Dyson" Cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802031320.IAA01433@dyson.iquest.net> References: <199802031320.IAA01433@dyson.iquest.net> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > Is paging more stable? Unfortunately, I'm away on business, but I back-patched this to my 2.2.5 system which ran a heavy build overnight without any problems, but I wasn't able to test it much. Hopefully when I get back this weekend I'll be able to beat it up more. Nate From owner-freebsd-current Tue Feb 3 15:56:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00550 for current-outgoing; Tue, 3 Feb 1998 15:56:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00545 for ; Tue, 3 Feb 1998 15:56:20 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id SAA11555; Tue, 3 Feb 1998 18:56:19 -0500 (EST) (envelope-from henrich) Date: Tue, 3 Feb 1998 18:56:19 -0500 (EST) From: Charles Henrich Message-Id: <199802032356.SAA11555@crh.cl.msu.edu> To: nate@mt.sri.com, freebsd-current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' Newsgroups: lists.freebsd.current References: <6b8aec$gb5$1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 CURRENT #1 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" In lists.freebsd.current you write: >> Is paging more stable? >Unfortunately, I'm away on business, but I back-patched this to my 2.2.5 >system which ran a heavy build overnight without any problems, but I >wasn't able to test it much. Hopefully when I get back this weekend >I'll be able to beat it up more. And I was just about to do that myself ! Can I get your patches to try out on my server which keeps experiencing swapdeath? -Crh -- Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Tue Feb 3 16:35:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05681 for current-outgoing; Tue, 3 Feb 1998 16:35:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05674 for ; Tue, 3 Feb 1998 16:35:01 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA27187; Tue, 3 Feb 1998 17:34:55 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA03201; Tue, 3 Feb 1998 17:34:42 -0700 Date: Tue, 3 Feb 1998 17:34:42 -0700 Message-Id: <199802040034.RAA03201@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Charles Henrich Cc: nate@mt.sri.com, freebsd-current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' Newsgroups: lists.freebsd.current In-Reply-To: <199802032356.SAA11555@crh.cl.msu.edu> References: <6b8aec$gb5$1@msunews.cl.msu.edu> <199802032356.SAA11555@crh.cl.msu.edu> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > >> Is paging more stable? > > >Unfortunately, I'm away on business, but I back-patched this to my 2.2.5 > >system which ran a heavy build overnight without any problems, but I > >wasn't able to test it much. Hopefully when I get back this weekend > >I'll be able to beat it up more. > > And I was just about to do that myself ! Can I get your patches to > try out on my server which keeps experiencing swapdeath? The patch to current applies easily to -stable. (I used CVS to patch stable.) Also, I don't have access to that patch as I'm in CA and my computer is in my spare bedroom in MT. Nate From owner-freebsd-current Tue Feb 3 16:40:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06979 for current-outgoing; Tue, 3 Feb 1998 16:40:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06938 for ; Tue, 3 Feb 1998 16:40:54 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA26229; Tue, 3 Feb 1998 16:34:17 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd026227; Tue Feb 3 16:34:16 1998 Message-ID: <34D7B6B0.31DFF4F5@whistle.com> Date: Tue, 03 Feb 1998 16:30:41 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: mckusick@mckusick.com, current@FreeBSD.ORG Subject: sb being written to r/o disks. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" hmmmm it's amazing what new debugging info brings to light! I noticed this with the mount from the soft-updates integration. notice the two extra fields in 'mount'. # mount /dev/wd0e on / (local, read-only, writes: sync 4 async 0) /dev/wd0h on /data (local, softdep, writes: sync 2 async 0) /dev/wd0g on /var (local, writes: sync 2 async 0) procfs on /proc (local, writes: sync 0 async 0) something is doing syncronous writes to a r/o FS.. who? that's easy.. # mount -u -ordonly / Breakpoint at _mount: pushl %ebp db> b bwrite db> c Breakpoint at _bwrite: pushl %ebp db> tr _bwrite(f245ccf4,0) at _bwrite _ffs_sbupdate(f045f200,1) at _ffs_sbupdate+0xb0 _ffs_mount(f045fc00,efbfd268,efbfd1cc,f3666eb8,f364e740) at _ffs_mount+0x1e5 _mount(f364e740,f3666f94,0,efbfd268,1201) at _mount+0x416 _syscall(27,27,1201,efbfd268,efbfd238) at _syscall+0x187 _Xsyscall() at _Xsyscall+0x35 --- syscall 0x15, eip = 0x6a95, esp = 0xefbfd188, ebp = 0xefbfd238 --- db> apparently _ffs_sbupdate() doesn't know to check if the fs is readonly.. julian From owner-freebsd-current Tue Feb 3 16:43:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07895 for current-outgoing; Tue, 3 Feb 1998 16:43:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [205.217.47.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07887 for ; Tue, 3 Feb 1998 16:43:39 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.8.5/8.8.5) with ESMTP id QAA09193; Tue, 3 Feb 1998 16:44:05 -0800 (PST) Message-Id: <199802040044.QAA09193@flamingo.McKusick.COM> To: Julian Elischer Subject: Re: sb being written to r/o disks. cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 03 Feb 1998 16:30:41 PST." <34D7B6B0.31DFF4F5@whistle.com> Date: Tue, 03 Feb 1998 16:44:05 -0800 From: Kirk McKusick Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Sender: julian@whistle.com Date: Tue, 03 Feb 1998 16:30:41 -0800 From: Julian Elischer Organization: Whistle Communications To: mckusick@mckusick.com, current@freebsd.org Subject: sb being written to r/o disks. hmmmm it's amazing what new debugging info brings to light! I noticed this with the mount from the soft-updates integration. notice the two extra fields in 'mount'. # mount /dev/wd0e on / (local, read-only, writes: sync 4 async 0) /dev/wd0h on /data (local, softdep, writes: sync 2 async 0) /dev/wd0g on /var (local, writes: sync 2 async 0) procfs on /proc (local, writes: sync 0 async 0) something is doing syncronous writes to a r/o FS.. who? that's easy.. # mount -u -ordonly / Breakpoint at _mount: pushl %ebp db> b bwrite db> c Breakpoint at _bwrite: pushl %ebp db> tr _bwrite(f245ccf4,0) at _bwrite _ffs_sbupdate(f045f200,1) at _ffs_sbupdate+0xb0 _ffs_mount(f045fc00,efbfd268,efbfd1cc,f3666eb8,f364e740) at _ffs_mount+0x1e5 _mount(f364e740,f3666f94,0,efbfd268,1201) at _mount+0x416 _syscall(27,27,1201,efbfd268,efbfd238) at _syscall+0x187 _Xsyscall() at _Xsyscall+0x35 --- syscall 0x15, eip = 0x6a95, esp = 0xefbfd188, ebp = 0xefbfd238 --- db> apparently _ffs_sbupdate() doesn't know to check if the fs is readonly.. julian If you are doing a downgrade from r/w to r/o then the update is correct. If it is r/o to r/o then it is definitely a bug. ~Kirk From owner-freebsd-current Tue Feb 3 17:00:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10415 for current-outgoing; Tue, 3 Feb 1998 17:00:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10407 for ; Tue, 3 Feb 1998 17:00:23 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA27023 for ; Tue, 3 Feb 1998 16:58:54 -0800 (PST) Received: from UNKNOWN(), claiming to be "current1.whistle.com" via SMTP by alpo.whistle.com, id smtpd027021; Tue Feb 3 16:58:51 1998 Message-ID: <34D7BC73.63DECDAD@whistle.com> Date: Tue, 03 Feb 1998 16:55:15 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: sb being written to r/o disks. References: <199802040044.QAA09193@flamingo.McKusick.COM> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Kirk McKusick wrote: > > > /dev/wd0e on / (local, read-only, writes: sync 4 async 0) > # mount -u -ordonly / > > If you are doing a downgrade from r/w to r/o then the update is > correct. If it is r/o to r/o then it is definitely a bug. > > ~Kirk ro -> ro i.e. a bug Julian (I'll try think up a patch) From owner-freebsd-current Tue Feb 3 18:15:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20130 for current-outgoing; Tue, 3 Feb 1998 18:15:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20124 for ; Tue, 3 Feb 1998 18:15:22 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id VAA09075; Tue, 3 Feb 1998 21:14:40 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802040214.VAA09075@dyson.iquest.net> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802032356.SAA11555@crh.cl.msu.edu> from Charles Henrich at "Feb 3, 98 06:56:19 pm" To: henrich@crh.cl.msu.edu (Charles Henrich) Date: Tue, 3 Feb 1998 21:14:40 -0500 (EST) Cc: nate@mt.sri.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Charles Henrich said: > In lists.freebsd.current you write: > > >> Is paging more stable? > > >Unfortunately, I'm away on business, but I back-patched this to my 2.2.5 > >system which ran a heavy build overnight without any problems, but I > >wasn't able to test it much. Hopefully when I get back this weekend > >I'll be able to beat it up more. > > And I was just about to do that myself ! Can I get your patches to try out on > my server which keeps experiencing swapdeath? > Be very careful to make sure that pages that are freed are non-busy as opposed to busy. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Tue Feb 3 18:29:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22384 for current-outgoing; Tue, 3 Feb 1998 18:29:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from venus.GAIANET.NET (vince@venus.GAIANET.NET [207.211.200.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22373 for ; Tue, 3 Feb 1998 18:29:16 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.8.7/8.8.7) with SMTP id SAA03903; Tue, 3 Feb 1998 18:28:24 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Tue, 3 Feb 1998 18:28:23 -0800 (PST) From: Vincent Poy To: spork cc: "Scot W. Hetzel" , freebsd-current@FreeBSD.ORG Subject: Re: current.freebsd.org unable to connect In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Just wanted to comment on the problem of not being able to connect to current.freebsd.org. If you are connecting through Mae-West, there is currently an outage of all the peers in the OC-3 cards between NASA Ames and the route server for the last two days. Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Tue Feb 3 19:08:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27769 for current-outgoing; Tue, 3 Feb 1998 19:08:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from venus.GAIANET.NET (vince@venus.GAIANET.NET [207.211.200.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27764 for ; Tue, 3 Feb 1998 19:08:22 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Received: from localhost (vince@localhost) by venus.GAIANET.NET (8.8.7/8.8.7) with SMTP id SAA04018; Tue, 3 Feb 1998 18:59:58 -0800 (PST) (envelope-from vince@venus.GAIANET.NET) Date: Tue, 3 Feb 1998 18:59:56 -0800 (PST) From: Vincent Poy To: spork cc: "Scot W. Hetzel" , freebsd-current@FreeBSD.ORG Subject: Re: current.freebsd.org unable to connect In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Tue, 3 Feb 1998, Vincent Poy wrote: > Just wanted to comment on the problem of not being able to connect > to current.freebsd.org. If you are connecting through Mae-West, there is > currently an outage of all the peers in the OC-3 cards between NASA Ames > and the route server for the last two days. As a followup, for more info: http://www.yahoo.com/headlines/980203/wired/stories/mae_1.html Cheers, Vince - vince@MCESTATE.COM - vince@GAIANET.NET ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] GaiaNet Corporation - M & C Estate / / / / | / | __] ] Beverly Hills, California USA 90210 / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] From owner-freebsd-current Tue Feb 3 20:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10041 for current-outgoing; Tue, 3 Feb 1998 20:33:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from casa.plan.pixelogix.com (casagate.plan.pixelogix.com [206.129.249.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA10036; Tue, 3 Feb 1998 20:33:06 -0800 (PST) (envelope-from phils@casa.plan.pixelogix.com) Received: (from phils@localhost) by casa.plan.pixelogix.com (8.8.8/8.8.5) id UAA01493; Tue, 3 Feb 1998 20:32:21 -0800 (PST) Date: Tue, 3 Feb 1998 20:32:21 -0800 (PST) Message-Id: <199802040432.UAA01493@casa.plan.pixelogix.com> From: Phil Staub To: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: PPP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Brian: A quick (I hope) question re: ppp-980123.src.tar.gz downloaded from your page. Have you disabled the telnet connection in this version? I got a "connection refused" when I tried to telnet into it on port 3000. (Yes, I remembered to disable the pppctl socket.) It worked fine on the version from 2.2.5-STABLE. Thanks, Phil -- Phil Staub, KE7HC Senior Software Engineer phils@pixelogix.com Audio Precision, Inc. or phils@audioprecision.com Beaverton, OR 97075, (800) 231-7350 From owner-freebsd-current Tue Feb 3 21:35:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19049 for current-outgoing; Tue, 3 Feb 1998 21:35:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [207.217.224.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19042 for ; Tue, 3 Feb 1998 21:35:01 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [207.217.224.195]) by mail.westbend.net (8.8.8/8.8.7) with SMTP id WAA26686 for ; Tue, 3 Feb 1998 22:44:20 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <00b001bd3127$2470cde0$c3e0d9cf@admin.westbend.net> From: "Scot W. Hetzel" To: Subject: Re: current.freebsd.org unable to connect Date: Tue, 3 Feb 1998 22:41:21 -0600 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 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" From: spork Date: Tuesday, February 03, 1998 2:11 PM >You should make sure that your machine's reverse lookup is happening OK. >The snap server seems to tend toward the "super-paranoid". It nukes >mismatches and things that just aren't reversed... > > I just did a nslookup from "a.root-server.net", and it was able to return both the name and IP address of my computers. So I don't think that's the problem. Maybe, Vince is correct that it is a problem at MAE-West. Guess I'll have to try tomorrow. Thanks Scot From owner-freebsd-current Tue Feb 3 23:17:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA03174 for current-outgoing; Tue, 3 Feb 1998 23:17:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA03169 for ; Tue, 3 Feb 1998 23:17:12 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id AAA01024; Wed, 4 Feb 1998 00:17:08 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd001013; Wed Feb 4 00:17:01 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id AAA04564; Wed, 4 Feb 1998 00:16:59 -0700 (MST) From: Terry Lambert Message-Id: <199802040716.AAA04564@usr08.primenet.com> Subject: Re: sb being written to r/o disks. To: julian@whistle.com (Julian Elischer) Date: Wed, 4 Feb 1998 07:16:59 +0000 (GMT) Cc: mckusick@mckusick.com, current@FreeBSD.ORG In-Reply-To: <34D7B6B0.31DFF4F5@whistle.com> from "Julian Elischer" at Feb 3, 98 04:30:41 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > something is doing syncronous writes to a r/o FS.. > who? that's easy.. > > # mount -u -ordonly / > Breakpoint at _mount: pushl %ebp > db> b bwrite > db> c > Breakpoint at _bwrite: pushl %ebp > db> tr > _bwrite(f245ccf4,0) at _bwrite > _ffs_sbupdate(f045f200,1) at _ffs_sbupdate+0xb0 > _ffs_mount(f045fc00,efbfd268,efbfd1cc,f3666eb8,f364e740) at > _ffs_mount+0x1e5 > _mount(f364e740,f3666f94,0,efbfd268,1201) at _mount+0x416 > _syscall(27,27,1201,efbfd268,efbfd238) at _syscall+0x187 > _Xsyscall() at _Xsyscall+0x35 > --- syscall 0x15, eip = 0x6a95, esp = 0xefbfd188, ebp = 0xefbfd238 --- > db> > > apparently _ffs_sbupdate() doesn't know to check if the fs is readonly.. This is kind of well known; this is because R/O FS's get their "last mounted on" information updated. This is probably a bad thing. Probably the "last mounted on" information for a R/O FS should be set by newfs. It really means "please mount me here". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Wed Feb 4 00:35:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12912 for current-outgoing; Wed, 4 Feb 1998 00:35:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12906 for ; Wed, 4 Feb 1998 00:35:19 -0800 (PST) (envelope-from plm@muon.xs4all.nl) Received: from asterix.xs4all.nl (root@asterix.xs4all.nl [194.109.6.11]) by smtp1.xs4all.nl (8.8.8/8.8.8) with ESMTP id JAA05333 for ; Wed, 4 Feb 1998 09:35:16 +0100 (MET) Received: from muon.xs4all.nl (uucp@localhost) by asterix.xs4all.nl (8.8.6/8.8.6) with UUCP id JAA27650 for freebsd-current@freebsd.org; Wed, 4 Feb 1998 09:23:13 +0100 (MET) Received: (from plm@localhost) by muon.xs4all.nl (8.8.8/8.7.3) id JAA21003; Wed, 4 Feb 1998 09:22:53 +0100 (MET) To: freebsd-current@FreeBSD.ORG Subject: make world of -current error From: Peter Mutsaers Date: 04 Feb 1998 09:22:53 +0100 Message-ID: <87vhuvrd7m.fsf@muon.xs4all.nl> Lines: 37 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hello, Running make world ends with: ===> lkm/joy rm -f joy.h opt_devfs.h joy.8.gz joy.8.cat.gz joy_mod joy_mod.o joy.o @ machine rm -f .depend /varårch/fbsd/src/lkm/joy/GRTAGS /varårch/fbsd/src/lkm/joy/GTAGS ===> lkm/kernfs rm -f vnode_if.h vnode_if.c kernfs_mod kernfs_mod.o kernfs_vfsops.o kernfs_vnop\ s.o @ machine rm -f .depend /varårch/fbsd/src/lkm/kernfs/GRTAGS /varårch/fbsd/src/lkm/kernfs/GTAGS ===> lkm/linux rm -f vnode_if.h vnode_if.c linux_genassym.o linux_genassym linux_assym.h opt_\ compat.h linux.8.gz linux.8.cat.gz linux_mod linux_mod.o linux_locore.o linux.o linux_file.o linux_ioctl.o linux_misc.o linux_signal.o linux_ipc.o linux_socket.o linux_stats.o linux_dummy.o linux_sysent.o linux_sysvec.o linux_util.o imgact_linux.o @ machine rm: machine: is a directory *** Error code 1 Stop. *** Error code 1 I did first install /usr/share/mk but still this happens. Should I do something else (it has been 2 months ago since I did make world) or am I not the only one? -- /\_/\ ( o.o ) Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know ) ^ ( plm@xs4all.nl | the Netherlands | what I'm doing. From owner-freebsd-current Wed Feb 4 02:08:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA23807 for current-outgoing; Wed, 4 Feb 1998 02:08:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA23788 for ; Wed, 4 Feb 1998 02:08:21 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id LAA17925 for ; Wed, 4 Feb 1998 11:11:01 +0100 (CET) Date: Wed, 4 Feb 1998 11:11:01 +0100 (CET) From: Andrzej Bialecki To: freebsd-current@FreeBSD.ORG Subject: Custom init(8) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hi! I'd like to write my own custom init. To be frank, I'm not quite aware of what is absolutely necessary for it to do, and what is not. Basically, I want it to mount local disks and start a few shells on vty's. Thus far I managed to get "panic: init died" from my first (and probably too naive) tests... Can you give me some advice (except 'man init')? Perhaps some pointers to a code examples... Thanks. Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- From owner-freebsd-current Wed Feb 4 04:06:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08229 for current-outgoing; Wed, 4 Feb 1998 04:06:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08210 for ; Wed, 4 Feb 1998 04:06:18 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id EAA00926; Wed, 4 Feb 1998 04:05:26 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802041205.EAA00926@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' In-reply-to: Your message of "Tue, 03 Feb 1998 08:20:17 EST." <199802031320.IAA01433@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Feb 1998 04:05:26 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Just finished building xemacs20 on my pentium on a nfs partition previously the system would lock up solid. I didn't have X running this time nor the previous times which the system used to crashed while building xemacs. For sure I owed you a beer ! Tnks! Amancio From owner-freebsd-current Wed Feb 4 04:37:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12402 for current-outgoing; Wed, 4 Feb 1998 04:37:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12393 for ; Wed, 4 Feb 1998 04:37:37 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id HAA01225; Wed, 4 Feb 1998 07:37:28 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802041237.HAA01225@dyson.iquest.net> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802041205.EAA00926@rah.star-gate.com> from Amancio Hasty at "Feb 4, 98 04:05:26 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Wed, 4 Feb 1998 07:37:28 -0500 (EST) Cc: toor@dyson.iquest.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Amancio Hasty said: > > Just finished building xemacs20 on my pentium on a nfs partition previously > the system would lock up solid. I didn't have X running this time nor the > previous times which the system used to crashed while building xemacs. > > For sure I owed you a beer ! > Great feedback. I think that there is still a bug lurking, but the worst is likely over. There is still a problem that can manifest itself on heavily (memory) loaded systems. It appears to have something to do with vnode rundown or with object collapsing. However, I don't think larger systems (>= 64MB) should often have problems. I am working on the still-existing problem aggressively. I can easily reproduce the problem on small (8MB) systems, with PPro processors, using one of my FreeBSD regression tests. One of the problems that occurred (and it was procedural on my part), was that I quit testing small memory configs with my regression tests. I am doing that again... Sorry!!! There have indeed been bona-fide problems with the swap pager along with other pieces, and the system should be much more stable (as it is for Amancio) for most people now. For those who are a little less intrepid, I suggest waiting 2 more days (until some more minor fixes go in.) Two more things are going to happen to the VM code over the next 2 days. 1) Improve the allocation of VM pages for internal kernel usage. There are too many ad-hoc page allocators, and I already have some cleaner, more consistant, easier to debug/control code ready. 2) Fix an object rundown problem, that appears to be manifested by heavily memory loaded systems. The issue appears to be due to improper memory object reuse after being freed, and can be easily reproduced by a regression test that has atypical (and stressful) program VM behavior. After this, I hope to keep the low-level VM code stable for a while, so we all can work more effectively on some higher level (feature) issues that have had to have been deferred. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Wed Feb 4 05:28:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16995 for current-outgoing; Wed, 4 Feb 1998 05:28:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16983 for ; Wed, 4 Feb 1998 05:28:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id FAA01278; Wed, 4 Feb 1998 05:27:30 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802041327.FAA01278@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "John S. Dyson" cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' In-reply-to: Your message of "Wed, 04 Feb 1998 07:37:28 EST." <199802041237.HAA01225@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 04 Feb 1998 05:27:30 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hi, I got two boxes over here: rah which is PPro with 98MB with fast wide scsi cioloco which is a P133 with 32MB and a fast IDE disk drive Most of the time I hang around on rah till Bettina kicks me out and takes over rah :( Cheers, Amancio From owner-freebsd-current Wed Feb 4 06:26:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23830 for current-outgoing; Wed, 4 Feb 1998 06:26:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23825 for ; Wed, 4 Feb 1998 06:26:01 -0800 (PST) (envelope-from henrich@crh.cl.msu.edu) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.7/8.8.7) id JAA00482; Wed, 4 Feb 1998 09:25:54 -0500 (EST) (envelope-from henrich) Message-ID: <19980204092551.01398@crh.cl.msu.edu> Date: Wed, 4 Feb 1998 09:25:52 -0500 From: Charles Henrich To: Nate Williams Cc: freebsd-current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' References: <6b8aec$gb5$1@msunews.cl.msu.edu> <199802032356.SAA11555@crh.cl.msu.edu> <199802040034.RAA03201@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199802040034.RAA03201@mt.sri.com>; from Nate Williams on Tue, Feb 03, 1998 at 05:34:42PM -0700 X-Operating-System: FreeBSD 2.2.5-RELEASE X-PGP-Fingerprint: 1024/F7 FD C7 3A F5 6A 23 BF 76 C4 B8 C9 6E 41 A4 4F Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On the subject of Re: Any feedback on my recent kernel 'fixes', Nate Williams stated: > > >> Is paging more stable? > > > > >Unfortunately, I'm away on business, but I back-patched this to my 2.2.5 > > >system which ran a heavy build overnight without any problems, but I > > >wasn't able to test it much. Hopefully when I get back this weekend I'll > > >be able to beat it up more. > > > > > And I was just about to do that myself ! Can I get your patches to try > > out on my server which keeps experiencing swapdeath? > > The patch to current applies easily to -stable. (I used CVS to patch > stable.) Also, I don't have access to that patch as I'm in CA and my > computer is in my spare bedroom in MT. I just applied the latest -current patch to my 2.2.5 machine, and have been beating on it for about 30 minutes here, not a massive test, but its working nontheless under heavy paging. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-current Wed Feb 4 07:02:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28603 for current-outgoing; Wed, 4 Feb 1998 07:02:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kodakr.kodak.com (kodakr.kodak.com [192.232.119.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA28596 for ; Wed, 4 Feb 1998 07:02:22 -0800 (PST) (envelope-from rlyman@kodakr.kodak.com) Received: from doolittle.ycc.Kodak.COM by kodakr.kodak.com with SMTP id AA25763 (5.67b/IDA-1.5 for ); Wed, 4 Feb 1998 10:01:45 -0500 Received: from ycc.kodak.com (monkey.ycc.Kodak.COM [129.126.74.13]) by doolittle.ycc.Kodak.COM (8.7.3/8.7.3) with SMTP id JAA18109 for ; Wed, 4 Feb 1998 09:56:42 -0500 (EST) Received: from ep-psg-kestrel by ycc.kodak.com (SMI-8.6/SMI-SVR4) id JAA01614; Wed, 4 Feb 1998 09:56:39 -0500 Received: by localhost with Microsoft MAPI; Wed, 4 Feb 1998 09:56:48 -0500 Message-Id: <01BD3153.3542F8B0.rlyman@kodak.com> From: Ralph Lyman To: "'freebsd-current@FreeBSD.ORG'" Date: Wed, 4 Feb 1998 09:56:46 -0500 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4128 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" subscribe freebsd-current rlyman@frontiernet.net From owner-freebsd-current Wed Feb 4 07:02:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28623 for current-outgoing; Wed, 4 Feb 1998 07:02:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kodakr.kodak.com (kodakr.kodak.com [192.232.119.69]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA28597 for ; Wed, 4 Feb 1998 07:02:23 -0800 (PST) (envelope-from rlyman@kodakr.kodak.com) Received: from doolittle.ycc.Kodak.COM by kodakr.kodak.com with SMTP id AB25786 (5.67b/IDA-1.5 for ); Wed, 4 Feb 1998 10:01:54 -0500 Received: from ycc.kodak.com (monkey.ycc.Kodak.COM [129.126.74.13]) by doolittle.ycc.Kodak.COM (8.7.3/8.7.3) with SMTP id JAA18116 for ; Wed, 4 Feb 1998 09:56:51 -0500 (EST) Received: from ep-psg-kestrel by ycc.kodak.com (SMI-8.6/SMI-SVR4) id JAA01621; Wed, 4 Feb 1998 09:56:48 -0500 Received: by localhost with Microsoft MAPI; Wed, 4 Feb 1998 09:56:57 -0500 Message-Id: <01BD3153.3AA9E020.rlyman@kodak.com> From: Ralph Lyman To: "'freebsd-current@FreeBSD.ORG'" Date: Wed, 4 Feb 1998 09:56:57 -0500 X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4128 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" subscribe freebsd-current From owner-freebsd-current Wed Feb 4 08:32:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11848 for current-outgoing; Wed, 4 Feb 1998 08:32:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11839 for ; Wed, 4 Feb 1998 08:32:34 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA02776; Wed, 4 Feb 1998 08:32:23 -0800 (PST) (envelope-from jdp) Message-Id: <199802041632.IAA02776@austin.polstra.com> To: sasdrq@unx.sas.com Subject: Re: Failure in debug kernel In-Reply-To: <199802031258.AA03314@gamecock.unx.sas.com> References: <199802031258.AA03314@gamecock.unx.sas.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 04 Feb 1998 08:32:23 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" In article <199802031258.AA03314@gamecock.unx.sas.com>, David Quattlebaum wrote: > I tried to build a debug kernel yesterday and when I booted it, > it printed an error and rebooted faster than I could read the > screen. This went on until we brought up kernel.old. > > steps I took to build the kernel (from 3.0-980128-SNAP): > > o cp GENERIC DEBUG > o added "OPTIONS DDB" to DEBUG > o config -g DEBUG > o make depend && make && make install For this last step, try instead: make depend && make cp kernel kernel.unstripped strip -d kernel make install I don't know whether this is really the problem or not. It looks like you have plenty of RAM. But still, an unstripped debug kernel has a _lot_ of symbols, and they all get loaded into RAM at boot time. It is often a source of problems similar to the one you reported. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Wed Feb 4 08:50:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15043 for current-outgoing; Wed, 4 Feb 1998 08:50:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15029 for ; Wed, 4 Feb 1998 08:50:09 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA02912; Wed, 4 Feb 1998 08:49:33 -0800 (PST) (envelope-from jdp) Message-Id: <199802041649.IAA02912@austin.polstra.com> To: abial@nask.pl Subject: Re: Custom init(8) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Wed, 04 Feb 1998 08:49:33 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" In article , Andrzej Bialecki wrote: > I'd like to write my own custom init. To be frank, I'm not quite aware of > what is absolutely necessary for it to do, and what is not. [...] > Can you give me some advice (except 'man init')? Perhaps some pointers to > a code examples... /usr/src/sbin/init/init.c ;-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Wed Feb 4 09:02:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA16948 for current-outgoing; Wed, 4 Feb 1998 09:02:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA16939 for ; Wed, 4 Feb 1998 09:02:48 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id SAA19868; Wed, 4 Feb 1998 18:04:30 +0100 (CET) Date: Wed, 4 Feb 1998 18:04:29 +0100 (CET) From: Andrzej Bialecki To: John Polstra cc: abial@nask.pl, current@FreeBSD.ORG Subject: Re: Custom init(8) In-Reply-To: <199802041649.IAA02912@austin.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Wed, 4 Feb 1998, John Polstra wrote: > In article , > Andrzej Bialecki wrote: > > > I'd like to write my own custom init. To be frank, I'm not quite aware of > > what is absolutely necessary for it to do, and what is not. > [...] > > Can you give me some advice (except 'man init')? Perhaps some pointers to > > a code examples... > > /usr/src/sbin/init/init.c ;-) Okay. I got what I deserved for asking too simple questions... :-/ For all of you who want only to remind me of existence of /usr/src/sbin/init.c: please talk to /dev/null ... Sorry, but this really doesn't help me to know how _the simplest_ possible init(8) could look like... Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- From owner-freebsd-current Wed Feb 4 09:17:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20638 for current-outgoing; Wed, 4 Feb 1998 09:17:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from foxdev.parker.net (foxdev.parker.net [206.14.52.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20622 for ; Wed, 4 Feb 1998 09:17:44 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by foxdev.parker.net (8.8.5/8.8.5) id KAA28165; Wed, 4 Feb 1998 10:21:45 GMT Date: Wed, 4 Feb 1998 10:21:45 GMT From: Jim Shankland Message-Id: <199802041021.KAA28165@foxdev.parker.net> To: abial@nask.pl, current@FreeBSD.ORG Subject: Re: Custom init(8) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > For all of you who want only to remind me of existence of > /usr/src/sbin/init.c: please talk to /dev/null ... > > Sorry, but this really doesn't help me to know how _the simplest_ possible > init(8) could look like... It really depends on what you want to do. The simplest possible init is: main() { while (1) ; } You have two choices: either start with /usr/src/sbin/init.c, and rip out the stuff you don't want; or start with the above template, and add the stuff you *do* want. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-current Wed Feb 4 10:14:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02746 for current-outgoing; Wed, 4 Feb 1998 10:14:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02732 for ; Wed, 4 Feb 1998 10:14:46 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA18760; Wed, 4 Feb 1998 18:14:41 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA20763; Wed, 4 Feb 1998 19:14:41 +0100 (MET) Message-ID: <19980204191440.01035@follo.net> Date: Wed, 4 Feb 1998 19:14:40 +0100 From: Eivind Eklund To: Andrzej Bialecki Cc: current@FreeBSD.ORG Subject: Re: Custom init(8) References: <199802041649.IAA02912@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from Andrzej Bialecki on Wed, Feb 04, 1998 at 06:04:29PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Wed, Feb 04, 1998 at 06:04:29PM +0100, Andrzej Bialecki wrote: > Sorry, but this really doesn't help me to know how _the simplest_ possible > init(8) could look like... You'll have to reap any zombie process in the system and not exit, and that's about it. man waitpid for details on repeaing children. Of course, you might want to start a shell or do something else useful... BTW: sysinstall (from the install floppy) is another example of an application that run as init. Eivind. From owner-freebsd-current Wed Feb 4 11:34:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20747 for current-outgoing; Wed, 4 Feb 1998 11:34:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20717 for ; Wed, 4 Feb 1998 11:34:22 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <1844-26371>; Wed, 4 Feb 1998 20:34:03 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.8/8.8.8) with ESMTP id UAA13680; Wed, 4 Feb 1998 20:18:14 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id UAA27971; Wed, 4 Feb 1998 20:17:40 +0100 (MET) Message-Id: <199802041917.UAA27971@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: <199802031320.IAA01433@dyson.iquest.net> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Wed, 4 Feb 98 20:17:38 +0100 To: "John S. Dyson" Subject: Re: Any feedback on my recent kernel 'fixes' cc: current@FreeBSD.ORG Reply-To: ben@stuyts.nl References: <199802031320.IAA01433@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Tue, 3 Feb 1998, "John S. Dyson" wrote: > Is paging more stable? > > Thanks for any feedback (either way.) John, I've cvsupped this morning, rebuilt the kernel, then made world. No problems since then. (But the uptime since then is only 9 hours.) Usually my make world ups the load average to 5 or 6, so that is a pretty good test. Parallel make, updating doc, ports, readmes, etc, all at the same time. Is there a specific torture test you want me to try? Best regards, Ben From owner-freebsd-current Wed Feb 4 13:43:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17724 for current-outgoing; Wed, 4 Feb 1998 13:43:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17633 for ; Wed, 4 Feb 1998 13:42:49 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id WAA20950; Wed, 4 Feb 1998 22:44:34 +0100 (CET) Date: Wed, 4 Feb 1998 22:44:33 +0100 (CET) From: Andrzej Bialecki To: Eivind Eklund cc: Andrzej Bialecki , current@FreeBSD.ORG Subject: Re: Custom init(8) In-Reply-To: <19980204191440.01035@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Wed, 4 Feb 1998, Eivind Eklund wrote: > On Wed, Feb 04, 1998 at 06:04:29PM +0100, Andrzej Bialecki wrote: > > Sorry, but this really doesn't help me to know how _the simplest_ possible > > init(8) could look like... > > You'll have to reap any zombie process in the system and not exit, and > that's about it. Thanks. This is useful information. Andrzej Bialecki ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- From owner-freebsd-current Wed Feb 4 14:33:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27704 for current-outgoing; Wed, 4 Feb 1998 14:33:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27696 for ; Wed, 4 Feb 1998 14:33:49 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id RAA01464; Wed, 4 Feb 1998 17:33:44 -0500 (EST) (envelope-from toor) Message-Id: <199802042233.RAA01464@dyson.iquest.net> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802041917.UAA27971@daneel.stuyts.nl> from Ben Stuyts at "Feb 4, 98 08:17:38 pm" To: ben@stuyts.nl Date: Wed, 4 Feb 1998 17:33:44 -0500 (EST) Cc: current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Ben Stuyts said: > On Tue, 3 Feb 1998, "John S. Dyson" wrote: > > > Is paging more stable? > > > > Thanks for any feedback (either way.) > > John, > > I've cvsupped this morning, rebuilt the kernel, then made world. No problems > since then. (But the uptime since then is only 9 hours.) > > Usually my make world ups the load average to 5 or 6, so that is a pretty > good test. Parallel make, updating doc, ports, readmes, etc, all at the same > time. > > Is there a specific torture test you want me to try? > The best test that I want everyone to use, is a real world loaded test. I can only run synthetic tests, or tests of my own typical real world loads. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Wed Feb 4 14:48:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01011 for current-outgoing; Wed, 4 Feb 1998 14:48:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (dacole@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00977 for ; Wed, 4 Feb 1998 14:48:22 -0800 (PST) (envelope-from dacole@netcom.ca) Received: from localhost (dacole@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id RAA22591 for ; Wed, 4 Feb 1998 17:48:18 -0500 (EST) X-Authentication-Warning: tor-adm1.nbc.netcom.ca: dacole owned process doing -bs Date: Wed, 4 Feb 1998 17:48:18 -0500 (EST) From: Dave Cole X-Sender: dacole@tor-adm1 To: current@FreeBSD.ORG Subject: ncr 875 activity LED Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I have noticed that my pII running 3.0-971225-SNAP doesn't light up its ASUS SC875 ultra wide SCSI host interface's led during activity. It lights up fine during boot and while running Win95 but it is totally dim while FreeBSD is running. I thought it might just be me but I recently heard of a friend who is running 2.2.5-Stable that also noticed his LED not doing anything. ------------------------------------------------------------- Dave Cole (DC1110) | dacole@netcom.ca Systems Administrator | dacole@vex.net | office/~dacole/ Netcom Canada | www.vex.net/~dacole/ 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725 From owner-freebsd-current Wed Feb 4 16:10:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA14677 for current-outgoing; Wed, 4 Feb 1998 16:10:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gringo.cdrom.com (root@ppp-015.tky.exa.co.jp [210.129.93.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA14672 for ; Wed, 4 Feb 1998 16:10:14 -0800 (PST) (envelope-from jkh@gringo.cdrom.com) Received: from gringo.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by gringo.cdrom.com (8.8.8/8.8.5) with ESMTP id PAA00225; Wed, 4 Feb 1998 15:36:27 -0800 (PST) To: Andrzej Bialecki cc: John Polstra , current@FreeBSD.ORG Subject: Re: Custom init(8) In-reply-to: Your message of "Wed, 04 Feb 1998 18:04:29 +0100." Date: Wed, 04 Feb 1998 15:36:27 -0800 Message-ID: <221.886635387@gringo.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > Sorry, but this really doesn't help me to know how _the simplest_ possible > init(8) could look like... I think only you can answer that question - I don't know of anyone who's even tried to do what you're doing. So, let me turn it around: "Hey Andrzej, can you tell us what the simplest init(8) might look like?" ;-) Jordan From owner-freebsd-current Wed Feb 4 16:14:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16105 for current-outgoing; Wed, 4 Feb 1998 16:14:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16092 for ; Wed, 4 Feb 1998 16:14:42 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.8.8/frmug-2.2/nospam) with UUCP id BAA04549 for freebsd-current@FreeBSD.ORG; Thu, 5 Feb 1998 01:14:30 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: (from roberto@localhost) by keltia.freenix.fr (8.8.8/keltia-2.13/nospam) id BAA28024; Thu, 5 Feb 1998 01:03:32 +0100 (CET) (envelope-from roberto) Message-ID: <19980205010331.42008@keltia.freenix.fr> Date: Thu, 5 Feb 1998 01:03:31 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: make world of -current error Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <87vhuvrd7m.fsf@muon.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <87vhuvrd7m.fsf@muon.xs4all.nl>; from Peter Mutsaers on Wed, Feb 04, 1998 at 09:22:53AM +0100 X-Operating-System: FreeBSD 3.0-CURRENT ctm#4019 AMD-K6 MMX @ 225 MHz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" According to Peter Mutsaers: > linux_util.o imgact_linux.o @ machine I getting something similar. I'm using OBJDIR=yes in make.conf and the current bsd.kmod.mk adds a "-I/usr/obj/src/src/lkm//obj/@" (note the '@' at the end) for LKMs. I'm using tcsh with ls as an alias as 'ls-F' so it may be that the script is misinterpreting the '@' printed by tcsh when it is displaying a symlink... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #54: Mon Jan 26 20:29:17 CET 1998 From owner-freebsd-current Wed Feb 4 17:00:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24974 for current-outgoing; Wed, 4 Feb 1998 17:00:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA24963 for ; Wed, 4 Feb 1998 17:00:26 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0y0FFD-000425-00; Wed, 4 Feb 1998 16:32:43 -0800 Date: Wed, 4 Feb 1998 16:32:40 -0800 (PST) From: Tom To: "Jordan K. Hubbard" cc: Andrzej Bialecki , John Polstra , current@FreeBSD.ORG Subject: Re: Custom init(8) In-Reply-To: <221.886635387@gringo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Wed, 4 Feb 1998, Jordan K. Hubbard wrote: > > Sorry, but this really doesn't help me to know how _the simplest_ possible > > init(8) could look like... > > I think only you can answer that question - I don't know of anyone > who's even tried to do what you're doing. So, let me turn it around: > "Hey Andrzej, can you tell us what the simplest init(8) might look > like?" ;-) Wait a second, doesn't sysinstall run as init? You must have started with a skeleton init first, and then added the install stuff to it. That probably makes you the number #1 expert on alternate inits! :) > Jordan Tom From owner-freebsd-current Wed Feb 4 17:03:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25967 for current-outgoing; Wed, 4 Feb 1998 17:03:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25953 for ; Wed, 4 Feb 1998 17:03:32 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id RAA24020; Wed, 4 Feb 1998 17:02:15 -0800 (PST) To: Tom cc: Andrzej Bialecki , John Polstra , current@FreeBSD.ORG Subject: Re: Custom init(8) In-reply-to: Your message of "Wed, 04 Feb 1998 16:32:40 PST." Date: Wed, 04 Feb 1998 17:02:15 -0800 Message-ID: <24017.886640535@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Nope. The startup code looks for init and, if it can't find it, runs /stand/sysinstall instead. ;) Since sysinstall is running more or less stand-alone in that scenario, it also doesn't have to do all the work that init does. Jordan > > On Wed, 4 Feb 1998, Jordan K. Hubbard wrote: > > > > Sorry, but this really doesn't help me to know how _the simplest_ possibl e > > > init(8) could look like... > > > > I think only you can answer that question - I don't know of anyone > > who's even tried to do what you're doing. So, let me turn it around: > > "Hey Andrzej, can you tell us what the simplest init(8) might look > > like?" ;-) > > Wait a second, doesn't sysinstall run as init? You must have started > with a skeleton init first, and then added the install stuff to it. That > probably makes you the number #1 expert on alternate inits! :) > > > Jordan > > Tom > From owner-freebsd-current Wed Feb 4 18:53:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13227 for current-outgoing; Wed, 4 Feb 1998 18:53:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from master.inter-linc.net ([12.10.101.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13214 for ; Wed, 4 Feb 1998 18:53:02 -0800 (PST) (envelope-from cdillon@inter-linc.net) Received: from inter-linc.net (207.160.214.4) by master.inter-linc.net (Worldmail 1.3.167); 4 Feb 1998 20:51:32 -0600 Message-ID: <34D8D5CB.F01E4374@inter-linc.net> Date: Wed, 04 Feb 1998 20:55:39 +0000 From: Chris Dillon X-Mailer: Mozilla 4.04 [en] (WinNT; I) MIME-Version: 1.0 To: Dave Cole CC: current@FreeBSD.ORG Subject: Re: ncr 875 activity LED References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Dave Cole wrote: > I have noticed that my pII running 3.0-971225-SNAP doesn't light up > its ASUS SC875 ultra wide SCSI host interface's led during activity. > It lights up fine during boot and while running Win95 but it is > totally dim while FreeBSD is running. > > I thought it might just be me but I recently heard of a friend who is > running 2.2.5-Stable that also noticed his LED not doing anything. > Just so you know, I am running -stable with a NCR 53C875 based card and the light on it works just fine (after I got the polarity right on the LED, that is. :-) I heard that other people had had this problem with earlier versions of the driver, but that was fixed some time ago as far as I know. From owner-freebsd-current Wed Feb 4 20:04:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21033 for current-outgoing; Wed, 4 Feb 1998 20:04:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.inficad.com (root@mail.inficad.com [207.19.74.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21025 for ; Wed, 4 Feb 1998 20:04:24 -0800 (PST) (envelope-from straka@inficad.com) Received: from straka.motorvation.com (ip38.ts1.phx.inficad.com [208.198.101.38]) by mail.inficad.com (8.8.8/8.8.5) with SMTP id UAA23520; Wed, 4 Feb 1998 20:58:44 -0700 (MST) Message-ID: <34D93A4B.41C67EA6@inficad.com> Date: Wed, 04 Feb 1998 21:04:27 -0700 From: "Richard S. Straka" X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-971208-SNAP i386) MIME-Version: 1.0 To: Dave Cole CC: current@FreeBSD.ORG Subject: Re: ncr 875 activity LED References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Dave Cole wrote: > > I have noticed that my pII running 3.0-971225-SNAP doesn't light up > its ASUS SC875 ultra wide SCSI host interface's led during activity. > It lights up fine during boot and while running Win95 but it is > totally dim while FreeBSD is running. > > I thought it might just be me but I recently heard of a friend who is > running 2.2.5-Stable that also noticed his LED not doing anything. > > ------------------------------------------------------------- > Dave Cole (DC1110) | dacole@netcom.ca > Systems Administrator | dacole@vex.net > | office/~dacole/ > Netcom Canada | www.vex.net/~dacole/ > 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 > Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725 Try adding options SCSI_NCR_SYMBIOS_COMPAT to your kernel configuration file. Building a kernel with this option made the activity light work on my Symbios 875 card. regards, Richard Straka From owner-freebsd-current Wed Feb 4 20:54:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26839 for current-outgoing; Wed, 4 Feb 1998 20:54:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26781; Wed, 4 Feb 1998 20:54:08 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id XAA07798; Wed, 4 Feb 1998 23:59:10 -0500 (EST) (envelope-from mark) Message-ID: <19980204235910.49629@vmunix.com> Date: Wed, 4 Feb 1998 23:59:10 -0500 From: Mark Mayo To: dyson@FreeBSD.ORG Cc: ben@stuyts.nl, current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' References: <199802041917.UAA27971@daneel.stuyts.nl> <199802042233.RAA01464@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199802042233.RAA01464@dyson.iquest.net>; from John S. Dyson on Wed, Feb 04, 1998 at 05:33:44PM -0500 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Wed, Feb 04, 1998 at 05:33:44PM -0500, John S. Dyson wrote: > Ben Stuyts said: > > On Tue, 3 Feb 1998, "John S. Dyson" wrote: > > > > > Is paging more stable? > > > > > > Thanks for any feedback (either way.) > > > > John, > > > > I've cvsupped this morning, rebuilt the kernel, then made world. No problems > > since then. (But the uptime since then is only 9 hours.) > > > > Usually my make world ups the load average to 5 or 6, so that is a pretty > > good test. Parallel make, updating doc, ports, readmes, etc, all at the same > > time. > > > > Is there a specific torture test you want me to try? > > > The best test that I want everyone to use, is a real world loaded test. I > can only run synthetic tests, or tests of my own typical real world loads. Well, I just cvsup'ed and have been pounding my box with "real world" workstation type use.. I have 32MB of RAM, and I ran several copies of Netscape, a 'make world -j4', some gigantic GIMP filters, the distributed.net DES challenge thingy, the Cafeine Bencmark on the latest jdk1.1.5, a bunch of xterms over PPP, and doing some typing in the Linux Wordperfect 7.0. I kept switching back and forth between virtual windows (with the KDE desktop thing) and surfing on different netscapes, etc, etc... I even got the load up over 15 for over 5 minutes! 8-) It's quite challenging to keep a workstation that busy! After all was said and done I had over 122MB taken up in the swap file. :-) I may have reached my 128MB limit, since at one point GIMP refused to load up any more pictures (I have about 50-60 open).. I have my swap file spread across 2 SCSI (narrow) disks and they were grinding away like crazy. Life was painful, but the system was still remarkably usable and everything seemed to run just peachy! The ppp NAT stuff worked at full speed too, since I was able to surf the net from my girlfriend's PC in the bedroom with no noticable slow down... Great job. The VM system certainly seemed rock solid during my test! -Mark If I have time tomorrow I'll temporarily bring my system disk with -CURRENT on it into my lab and let our NFS server loose on it to see how NFS is performing.. I may not have time to do this though :-( -Mark > > -- > John | Never try to teach a pig to sing, > dyson@freebsd.org | it just makes you look stupid, > jdyson@nc.com | and it irritates the pig. -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-current Wed Feb 4 23:19:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29200 for current-outgoing; Wed, 4 Feb 1998 23:19:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29192 for ; Wed, 4 Feb 1998 23:19:04 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <9302-16809>; Thu, 5 Feb 1998 08:18:51 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.8/8.8.8) with ESMTP id IAA01088; Thu, 5 Feb 1998 08:15:54 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id IAA28346; Thu, 5 Feb 1998 08:15:19 +0100 (MET) Message-Id: <199802050715.IAA28346@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: <199802041917.UAA27971@daneel.stuyts.nl> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Thu, 5 Feb 98 08:15:16 +0100 To: "John S. Dyson" Subject: Re: Any feedback on my recent kernel 'fixes' cc: current@FreeBSD.ORG Reply-To: ben@stuyts.nl References: <199802031320.IAA01433@dyson.iquest.net> <199802041917.UAA27971@daneel.stuyts.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" To follow up on my own report.... On Wed, 4 Feb 98, Ben Stuyts wrote: > On Tue, 3 Feb 1998, "John S. Dyson" wrote: > > > Is paging more stable? > > > > Thanks for any feedback (either way.) > > John, > > I've cvsupped this morning, rebuilt the kernel, then made world. No problems > since then. (But the uptime since then is only 9 hours.) > > Usually my make world ups the load average to 5 or 6, so that is a pretty > good test. Parallel make, updating doc, ports, readmes, etc, all at the same > time. Last night the system locked up again. It was doing a make world, running X, rc5des, and that's about it. There were no msgs in xconsole. I had top running in an xterm, and it just showed a bunch of cc's, make's, etc running. Best regards, Ben From owner-freebsd-current Wed Feb 4 23:44:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA05579 for current-outgoing; Wed, 4 Feb 1998 23:44:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA05574 for ; Wed, 4 Feb 1998 23:44:18 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA02078; Thu, 5 Feb 1998 02:43:57 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802050743.CAA02078@dyson.iquest.net> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802050715.IAA28346@daneel.stuyts.nl> from Ben Stuyts at "Feb 5, 98 08:15:16 am" To: ben@stuyts.nl Date: Thu, 5 Feb 1998 02:43:57 -0500 (EST) Cc: toor@dyson.iquest.net, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Ben Stuyts said: > To follow up on my own report.... > .... > > Last night the system locked up again. It was doing a make world, running X, > rc5des, and that's about it. There were no msgs in xconsole. I had top running > in an xterm, and it just showed a bunch of cc's, make's, etc running. > Try again. I just committed some code that resolves the last, currently repeatable bug (not that there aren't more.) -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Thu Feb 5 00:12:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09209 for current-outgoing; Thu, 5 Feb 1998 00:12:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09204 for ; Thu, 5 Feb 1998 00:12:28 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.5/8.8.5) id CAA16013; Thu, 5 Feb 1998 02:11:12 -0600 (CST) From: Kevin Day Message-Id: <199802050811.CAA16013@home.dragondata.com> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802031320.IAA01433@dyson.iquest.net> from "John S. Dyson" at "Feb 3, 98 08:20:17 am" To: toor@dyson.iquest.net (John S. Dyson) Date: Thu, 5 Feb 1998 02:11:12 -0600 (CST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > Is paging more stable? > > Thanks for any feedback (either way.) > -- > John | Never try to teach a pig to sing, > dyson@freebsd.org | it just makes you look stupid, > jdyson@nc.com | and it irritates the pig. > Things seem a lot better here... I've been rebuilding things here about every 2 days. Still having trouble with identd though. Posted below is the only problem we've had... (note, the nfs server 'home' mentioned below was running just fine, and other clients reported nothing odd during this period. Ditto with the NIS server) It looks like something caused it to go through a long and painful death. :) Also, I didn't touch it. I though that they system should have stopped at the page fault notice, but it kept on going.... The system has 128MB of ram, and averages around 48MB free. More than 200MB of swap, so the 'suggest more swap space' message seems a bit confusing. This kernel was from early on Feb 1st. Feb 1 16:08:27 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" not responding Feb 1 16:08:36 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" OK Feb 1 16:33:29 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" not responding Feb 1 16:33:33 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" OK Feb 1 16:34:22 shell /kernel: swap_pager: suggest more swap space: 157 MB Feb 1 16:42:49 shell /kernel: Feb 1 16:42:49 shell /kernel: Feb 1 16:42:49 shell /kernel: Fatal trap 12: page fault while in kernel mode Feb 1 16:42:49 shell /kernel: mp_lock = 00000003; cpuid = 0; lapic.id = 00000000 Feb 1 16:42:49 shell /kernel: fault virtual address = 0x60 Feb 1 16:42:49 shell /kernel: fault code = supervisor read, page not present Feb 1 16:42:49 shell /kernel: instruction pointer = 0x8:0xf01aad9e Feb 1 16:42:49 shell /kernel: stack pointer = 0x10:0xff804e08 Feb 1 16:42:49 shell /kernel: frame pointer = 0x10:0xff804e0c Feb 1 16:42:49 shell /kernel: code segment = base 0x0, limit 0xfffff, type 0x1b Feb 1 16:42:49 shell /kernel: = DPL 0, pres 1, def32 1, gran 1 Feb 1 16:42:49 shell /kernel: processor eflags = interrupt enabled, resume, IOPL = 0 Feb 1 16:42:49 shell /kernel: current process = Idle Feb 1 16:42:49 shell /kernel: interrupt mask = net tty <- SMP: XXX Feb 1 16:43:09 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" not responding Feb 1 16:43:15 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" OK Feb 1 16:41:15 shell /kernel: nfs server home:/home: not responding Feb 1 16:41:18 shell /kernel: nfs server home:/home: not responding Feb 1 16:41:26 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" OK Feb 1 16:42:59 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" not responding Feb 1 16:43:53 shell ypbind[128]: NIS server [204.137.237.2] for domain "dragondata.com" not responding Feb 1 16:45:42 shell last message repeated 2 times Feb 1 16:52:00 shell last message repeated 7 times Feb 1 16:52:18 shell /kernel: nfs server home:/home: not responding Feb 1 16:52:21 shell /kernel: vm_fault: pager input (probably hardware) error, PID 6319 failure Feb 1 16:48:05 shell /kernel: pid 4027 (eggdrop), uid 1039: exited on signal 11 (core dumped) Feb 1 17:00:01 shell /kernel: pid 5375 (eggdrop), uid 1039: exited on signal 10 (core dumped) Feb 1 17:00:53 shell /kernel: pid 10158 (irc-2.8.2-EPIC3.), uid 1016: exited on signal 6 (core dumped) Feb 1 17:01:48 shell /kernel: pid 10829 (irc-2.8.2-EPIC3.), uid 1018: exited on signal 4 (core dumped) Feb 1 17:01:49 shell inetd[167]: /usr/local/sbin/identd[14498]: exit status 0x9 Feb 1 17:05:45 shell identd[23155]: getbuf: bad address (00000000 not in f0100000-0xFFC00000) - ofiles Feb 1 17:05:46 shell last message repeated 19 times Feb 1 17:05:47 shell /kernel: nfs server home:/home: not responding Feb 1 17:05:49 shell /kernel: nfs server home:/home: is alive again Feb 1 17:05:44 shell /kernel: pid 26326 (irc-2.8.2-EPIC3.), uid 1087: exited on signal 4 (core dumped) Feb 1 17:05:46 shell identd[28841]: getbuf: bad address (00000000 not in f0100000-0xFFC00000) - ofiles Feb 1 17:05:49 shell last message repeated 19 times Feb 1 17:05:53 shell /kernel: pid 1480 (eggdrop), uid 1081: exited on signal 11 (core dumped) Feb 1 17:05:55 shell /kernel: pid 7319 (irc-2.8.2-EPIC3.), uid 1023: exited on signal 6 (core dumped) Feb 1 17:06:16 shell identd[13193]: k_getuid: ofiles malloc failed Feb 1 17:06:10 shell identd[3512]: k_getuid: ofiles malloc failed Feb 1 17:06:04 shell /kernel: pid 5296 (sh), uid 1049: exited on signal 11 (core dumped) Feb 1 17:06:05 shell /kernel: pid 5264 (sh), uid 1011: exited on signal 11 (core dumped) Feb 1 17:06:19 shell identd[12884]: k_getuid: ofiles malloc failed Feb 1 17:06:49 shell identd[23314]: getbuf: bad address (00000014 not in f0100000-0xFFC00000) - ofile Feb 1 17:06:49 shell last message repeated 19 times Feb 1 17:07:09 shell syslogd: exiting on signal 15 The NFS link was obviously still working, as certain logs across that link were still being updated up until 17:07. Kevin From owner-freebsd-current Thu Feb 5 00:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA12138 for current-outgoing; Thu, 5 Feb 1998 00:41:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA12132 for ; Thu, 5 Feb 1998 00:41:03 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id BAA22174; Thu, 5 Feb 1998 01:41:02 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd022168; Thu Feb 5 01:41:01 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id BAA13172; Thu, 5 Feb 1998 01:41:00 -0700 (MST) From: Terry Lambert Message-Id: <199802050841.BAA13172@usr08.primenet.com> Subject: Re: Custom init(8) To: abial@nask.pl (Andrzej Bialecki) Date: Thu, 5 Feb 1998 08:41:00 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Andrzej Bialecki" at Feb 4, 98 11:11:01 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" ------------------------------------------------------------------------ NOTE: The following would probably be a useful addition to the handbook or someplace else. *BUT* I typed this thing at near full-speed, off the top of my head, and without reference to man pages or code, so there may be factual errors arising from changes since the last time I looked at the code. Use the following information with caution and with man pages in hand. It is also bound to contain a lot of typos of the type seen caused by dyslexics typing at full speed. 8-). ------------------------------------------------------------------------ THE POOR MAN'S GUID TO HACKING INIT ON UNIX SYSTEMS > I'd like to write my own custom init. To be frank, I'm not quite aware of > what is absolutely necessary for it to do, and what is not. I think you are maybe barking up the wrong tree (see way below 8-)). The init's process is hand-crafted by the kernel as the first user process on the system, and is forked and exec'ed from the kernel by /sys/kern/init_main.c after a user space stack is hand built for the exec. Effectively, it is the first process on the system from which all other processes are descendents. An init will typically: 1) Be statically linked. 2) Not use a lot of libc, other than system calls. 3) Control "mode". Single user mode is defined by init running a user shell, generally /bin/sh, also expected to be statically linked. Multiuser mode is defined by init running a user shell, generally /bin/sh, to process commands in a /etc/rc file. 4) If running a shell, init fork()'s, and the shell is run in the child (init is alsways PID 1). In the case of single user mode, init will set the console canonical processing mode and exec the shell with "-" as the argument, after opening the console and making the child the process group leader and controlling process for the tty. In the case of multiuser mode, init will will fork(), exec the /etc/rc file after setting the console canonical processing modes, and will wait for the child to exit (ie: the rc file to complete) before continuing. It is the job of the rc file to do all the work of bringing thesystem to multiuser mode. This includes starting daemons in the correct order, clearing log files and lock files and tmp directories, mounting require file systems (the most probable explanation for your failure is that you linked your init program shared, the default, and it could not find /usr/libexe/ld.so or /usr/lib/libc.so.* because /usr was not yet mounted), and similar tasks. 5) When init is done fork()ing, and potentially waitng for the child process, it generally reads a configuration file to tell it the programs it should respawn (re-fork and exec should they exit). In SVR4, this is the /etc/inittab, the same file that told it which rc files to start (SVR4's init is smarter than SD's, and knows how to manage multiple run levels, not just "single user" and "multiuser"). In BSD, this file is /etc/ttys. 6) Init starts the processes in the file it read. 7) Init establishes a sigchld handler, a sighup handler, and any other handlers it choolses. Generally a sighup handler is used to tell init to reread its configuration file, above, so it can know that the file has been changed. 8) Init goes into a loop, where it calls sigpause(2) to wait for a signal. Since SIGCLD is a persistent condition, rather than an event, a good init will set a flag in the handler instead of trying to reap children there (a volatile one if you are using an ANSI compiler and don't want it to overly ambitiously optimize the flag variable away). This is needed because you can only know that "one or more SIGCLD's have been recieved". Signals are not events. A good SVR4 "port monitor" (basically an init for a single class of daemons) will use this same technique, as will a good state automaton implementing logins for many X terminals via a single "xdm" type program. 9) The main loop wakes up on the signal. If the SIGHUP flag is set, it checks the configuration file (usually by timestamp via "stat") to see if it has changed -- or just assumes it has, if the programmer is lazy -- and "does the right thing". If the SIGCHLD flag is set, it calls a system call in the wait(2) family; generally, wait4(). It uses one of the interfaces which can be called in non-blocking mode (WNOHANG) so that it can call the function iteratively, since all it knows is that "one or more child processes have exited", and can not know the exact number (signals are persistent conditions, not events; I harp on this because too many programmers try to write code instead of setting flags in signal handlers). 10) When all signals have been processed, and all processes no longer in the config file killed, and all new processes now in the config file started, then init goes back to #8. It does this for as long as the system is up. 11) Depending on implementation, the init may or may not run a shutdown script. Typically, if it does, then a user space shutdown command will, instead of calling a system call, send init a SIGTERM. This means catching SIGTERM (see #7, above). 12) The init may use a shutdown script to make an /etc/nologin file, which will be printed to the user by the login (or getty) program after they type their name and after/before (respectively) the login program has been exec'ed by getty. In BSD, the shutdown program does this. It is not a system call, and expects init to shutdown the system safely from SIGTERM. You can choose to talk to your init program however you like, with or without running the standard shutdown program. The BSD shutdown will set nologin kill SIGTERM all processes, then kill -9 them after waiting for them to dies. Then it exec's the "halt" or "reboot" programs. If you do this yourself, you should look at their source code to see the system calls involved. 13) The SVR4 init signals the initd, which then shuts things down. Effectively, "shutting down" is just another "run level". The SVR4 initd can do this gracefully because they implement tty revocation and process group propagation of SIGHUP as a result of the controlling tty being revoked from the process greoup leader. BSD doesn't do this, so its shutdown process has to be vastly more complicated (BSD misinterprets POSIX here, IMO). > Basically, I want it to mount local disks and start a few shells on > vty's. Most likely you really want to modify the program you run in /etc/ttys, or if you want getty to configure the terminals for you, then you need to modify /etc/gettytab to set the "lo" program. You can change the login prompt to something other than "login:" in /etc/gettytab as well. If you do not want to do this, you will need to manage setting up the tty's yourself (for example, if you wanted to automatically start an accounting program on the accountant desk, or a video rental POS program at the video counter, etc.). If you can live with a little delay, it's best to get getty to do this for you, you can change the login prompt to "hit return to start" or something similar, and still use getty. This will be generally acceptable, unless what you want to run takes a long time to start. This will leave the mount and other code in the /etc/rc file intact. If you want to stop network services, etc., you can njust not configure them. Otherwise, if yyou want to delete programs for a smaller footprint, you can just rewrite the /etc/rc file to contain just the mount commands and other commands you want. > Thus far I managed to get "panic: init died" from my first (and probably > too naive) tests... See above; this is probably because you liked the thing against a shared libc. 8-). > Can you give me some advice (except 'man init')? Perhaps some pointers to > a code examples... The above should be enough to let a reasonably industrious person do the job in a relatively short period of time. As I pointed out, though, I think you may be barking up the tree of the wrong program. 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Thu Feb 5 01:38:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA19977 for current-outgoing; Thu, 5 Feb 1998 01:38:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA19966; Thu, 5 Feb 1998 01:38:16 -0800 (PST) (envelope-from abial@korin.warman.org.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id KAA27228; Thu, 5 Feb 1998 10:40:22 +0100 (CET) Date: Thu, 5 Feb 1998 10:40:21 +0100 (CET) From: Andrzej Bialecki To: Terry Lambert cc: freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-Reply-To: <199802050841.BAA13172@usr08.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hi! Thanks for your replies - now I'm more aware of do's and dont's. Besides, now I know where the sources for init(8) are... :-)) I must rethink the problem. Perhaps I'll start reaping out chunks of normal init... A bit of background, if you're interested: I'm working on the next version of PicoBSD, and after some shuffling with the layout and adding new features I found that I can no longer fit into 8MB RAM... I.e. it fits, but I can't start enough processes to make a dialup connection. There was one really nasty surprise which I experienced: the way the gzipped binaries are executed. It wastes a LOT of RAM. And since all of the programs on my floppy are just one crunched binary (which is gzipped for saving space on the floppy), when it gets executed it initially takes almost thrice as much memory than its file size. And of course it can't be paged out (where to?), which results in crash. I had some ideas how to fix it, but the implementation of this is far beyond my knowledge: to modify imgact_gzip NOT to load the gzipped binary, but just to mmap it, and then unpack it. When I asked John Dyson he said that it would require a lot of work to change it... Pity. Also, IMHO it would be a good option to the kernel and/or ld.so to tell them not to load .text at all (it could apply to .text section of binaries as well as shared libs), just to mmap it, if the backing filesystem is of MFS type. So, I'm still looking for various ways of memory saving, and the way that init uses to (finally) start a user shell is unnecesarily complicated in my case. Because what I want in basic setup is just to start some interactive shells on different ttys. That said, I think I must go and read /usr/src/sbin/init/init.c... :-)) Andrzej Bialecki PS. Terry, thanks for your explanation - IMO, this is parallel to what 'man init' says, but gives, I'd say, "stereoscopic view" of the things... And no, I linked my init statically, but I forgot that it must never exit :-) ---------------------+--------------------------------------------------------- abial@warman.org.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. ---------------------+--------------------------------------------------------- From owner-freebsd-current Thu Feb 5 01:54:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA21619 for current-outgoing; Thu, 5 Feb 1998 01:54:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA21614 for ; Thu, 5 Feb 1998 01:54:37 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id BAA00404; Thu, 5 Feb 1998 01:53:48 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802050953.BAA00404@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: "John S. Dyson" cc: ben@stuyts.nl, current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' In-reply-to: Your message of "Thu, 05 Feb 1998 02:43:57 EST." <199802050743.CAA02078@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Feb 1998 01:53:47 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" No Joy with tonites commits: nfs-client P133 32MB ---> nfs-server PPro 98MB test scenario run X compiling xemacs over nfs partition start surfing with netscape The nfs transactions seems to come to a hold a few seconds after netscape started -- the system sort of got stuck in nfs wait -- the compilation process paused yet I was able to move the cursor around . A few minutes later the system die . Cheers, Amancio From owner-freebsd-current Thu Feb 5 08:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA08684 for current-outgoing; Thu, 5 Feb 1998 08:08:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA08660 for ; Thu, 5 Feb 1998 08:08:15 -0800 (PST) (envelope-from bsdcur@shadows.aeon.net) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.8/8.8.3) id SAA23230 for current@freebsd.org; Thu, 5 Feb 1998 18:08:02 +0200 (EET) From: mika ruohotie Message-Id: <199802051608.SAA23230@shadows.aeon.net> Subject: *hmph* To: current@FreeBSD.ORG Date: Thu, 5 Feb 1998 18:08:02 +0200 (EET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" probably not to the right list, but anyway... it appears that i was dropped off from two bsd lists a while ago, probably that crash someone mentioned about. only now (after finding time to read the email back-log i have) did i find that the other list i dropped off from was cvs. for me (and anyone else) running current, that is very, very, very bad thing to happen. specially since the time i noticed this was two weeks later. now, i feel quite pissed off about the fact there appears to be no backups or anything, since i wasnt put back into the lists. and, whoever didnt have backups, could make me feel much better if the lost cvs-emails would be emailed me now. (apologies to everyone, i feel rather violent at the moment, mostly coz of other things) mickey From owner-freebsd-current Thu Feb 5 08:18:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10706 for current-outgoing; Thu, 5 Feb 1998 08:18:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alexis.videotron.ca (ppp213.245.mmtl.videotron.net [207.96.245.213]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10601 for ; Thu, 5 Feb 1998 08:17:57 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost [127.0.0.1]) by alexis.videotron.ca (8.8.8/8.8.8) with ESMTP id LAA00260 for ; Thu, 5 Feb 1998 11:13:40 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34D9E532.8CF91685@videotron.ca> Date: Thu, 05 Feb 1998 11:13:38 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Current dying horribly when using lp0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hi! I don't know if I'm the only one having this problem. I have 2 computer running Current linked together with a laplink cable using interface lp0. Everytime I try to transfert any relevent amount of data between the two of them the server side freeze and then reboot promptly after. It does that with ftp, cvsup and nfs. It doesn't seems to be load, X or memory related. I'm able to reproduce it on a system unloaded not running X. If anyone could give me a pointer where to start looking it would be very appreciated. Regards, Stephane E. Potvin sepotvin@videotron.ca From owner-freebsd-current Thu Feb 5 08:20:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11206 for current-outgoing; Thu, 5 Feb 1998 08:20:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11195 for ; Thu, 5 Feb 1998 08:20:16 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id IAA09900; Thu, 5 Feb 1998 08:20:08 -0800 (PST) (envelope-from jdp) Message-Id: <199802051620.IAA09900@austin.polstra.com> To: abial@nask.pl Subject: Re: Custom init(8) (and some ideas) In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Thu, 05 Feb 1998 08:20:08 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" In article , Andrzej Bialecki wrote: > Also, IMHO it would be a good option to the kernel and/or ld.so to tell > them not to load .text at all (it could apply to .text section of binaries > as well as shared libs), just to mmap it, if the backing filesystem is of > MFS type. Both the kernel and ld.so do that (use mmap), no matter what type of filesystem the executable or shared library is on. Actually, they mmap not only text, but also data and bss. Copy-on-write prevents that from causing problems. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Thu Feb 5 08:21:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11501 for current-outgoing; Thu, 5 Feb 1998 08:21:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11486 for ; Thu, 5 Feb 1998 08:21:10 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA01064; Thu, 5 Feb 1998 11:20:50 -0500 (EST) (envelope-from toor) Message-Id: <199802051620.LAA01064@dyson.iquest.net> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802050953.BAA00404@rah.star-gate.com> from Amancio Hasty at "Feb 5, 98 01:53:47 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 5 Feb 1998 11:20:50 -0500 (EST) Cc: ben@stuyts.nl, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Amancio Hasty said: > > The nfs transactions seems to come to a hold a few seconds after > netscape started -- the system sort of got stuck in nfs wait -- > the compilation process paused yet I was able to move the cursor > around . A few minutes later the system die . > That is unfortunate. I don't think that ANY of the changes should have *any* effect on NFS. I think that the changes are sometimes simply moving the way the NFS bugs are being manifest. Oh well, more bugs to work on. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Thu Feb 5 08:43:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15588 for current-outgoing; Thu, 5 Feb 1998 08:43:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15571 for ; Thu, 5 Feb 1998 08:43:02 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id LAA00255; Thu, 5 Feb 1998 11:42:53 -0500 (EST) (envelope-from toor) Message-Id: <199802051642.LAA00255@dyson.iquest.net> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802050953.BAA00404@rah.star-gate.com> from Amancio Hasty at "Feb 5, 98 01:53:47 am" To: hasty@rah.star-gate.com (Amancio Hasty) Date: Thu, 5 Feb 1998 11:42:53 -0500 (EST) Cc: ben@stuyts.nl, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I just fixed an erroneous NFS commit (looks like a missing code line.) I didn't do it this time!!! :-). Try again!!! Amancio Hasty said: > No Joy with tonites commits: > > nfs-client P133 32MB ---> > nfs-server PPro 98MB > > test scenario > run X > compiling xemacs over nfs partition > start surfing with netscape > > The nfs transactions seems to come to a hold a few seconds after > netscape started -- the system sort of got stuck in nfs wait -- > the compilation process paused yet I was able to move the cursor > around . A few minutes later the system die . > -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Thu Feb 5 09:21:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20546 for current-outgoing; Thu, 5 Feb 1998 09:21:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20539 for ; Thu, 5 Feb 1998 09:21:27 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.8/8.8.5) id JAA23194; Thu, 5 Feb 1998 09:23:26 -0800 (PST) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199802051608.SAA23230@shadows.aeon.net> Date: Thu, 05 Feb 1998 09:12:17 -0800 (PST) Organization: Applied Physics Laboratory From: Steve Kargl To: mika ruohotie Subject: RE: *hmph* Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On 05-Feb-98 mika ruohotie wrote: >probably not to the right list, but anyway... > >it appears that i was dropped off from two bsd lists a while ago, >probably that crash someone mentioned about. > Several people had accidentally been dropped from mailing lists, so don't take it personally. >only now (after finding time to read the email back-log i have) >did i find that the other list i dropped off from was cvs. for me >(and anyone else) running current, that is very, very, very bad >thing to happen. specially since the time i noticed this was two >weeks later. > >now, i feel quite pissed off about the fact there appears to be no >backups or anything, since i wasnt put back into the lists. > FreeBSD is a VOLUNTEER effort. FreeBSD.org is hosted on machines by Walnut Creek Cdrom for FREE. If you wish to make a significant monetary contribution to ensure that major disk failures and their subsequent replacement goes smoothly, I'm sure Walnut Creek Cdrom will not complain. >and, whoever didnt have backups, could make me feel much better if >the lost cvs-emails would be emailed me now. http://www.freebsd.org/cgi/cvsweb.cgi Oh, did I mention that FreeBSD is a volunteer effort. Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html From owner-freebsd-current Thu Feb 5 09:44:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24083 for current-outgoing; Thu, 5 Feb 1998 09:44:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24078 for ; Thu, 5 Feb 1998 09:44:28 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.6/8.8.6) id LAA22529; Thu, 5 Feb 1998 11:44:26 -0600 (CST) Message-ID: <19980205114426.00932@emsphone.com> Date: Thu, 5 Feb 1998 11:44:26 -0600 From: Dan Nelson To: sepotvin@videotron.ca, current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <34D9E532.8CF91685@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <34D9E532.8CF91685@videotron.ca>; from "Stephane E. Potvin" on Thu Feb 5 11:13:38 GMT 1998 X-OS: FreeBSD 2.2-970701-RELENG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" In the last episode (Feb 05), Stephane E. Potvin said: > Hi! > > I don't know if I'm the only one having this problem. I have 2 > computer running Current linked together with a laplink cable using > interface lp0. Everytime I try to transfert any relevent amount of data > between the two of them the server side freeze and then reboot promptly > after. It does that with ftp, cvsup and nfs. It doesn't seems to be > load, X or memory related. I'm able to reproduce it on a system unloaded > not running X. > > If anyone could give me a pointer where to start looking it would be > very appreciated. I just got a spare laptop from work (486/75) and installed FreeBSD over lp0. It only rebooted once on me. I must have transferred 500MB of data in total (at a measly 70K/s and 90% interrupt load on both machines :) , but it worked fine. -Dan Nelson dnelson@emsphone.com From owner-freebsd-current Thu Feb 5 10:34:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00998 for current-outgoing; Thu, 5 Feb 1998 10:34:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan@dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00978 for ; Thu, 5 Feb 1998 10:34:36 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.8.6/8.8.6) id MAA23038; Thu, 5 Feb 1998 12:34:35 -0600 (CST) Message-ID: <19980205123435.48215@emsphone.com> Date: Thu, 5 Feb 1998 12:34:35 -0600 From: Dan Nelson To: mika ruohotie , current@FreeBSD.ORG Subject: Re: *hmph* References: <199802051608.SAA23230@shadows.aeon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802051608.SAA23230@shadows.aeon.net>; from "mika ruohotie" on Thu Feb 5 18:08:02 GMT 1998 X-OS: FreeBSD 2.2-970701-RELENG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" In the last episode (Feb 05), mika ruohotie said: > probably not to the right list, but anyway... > > it appears that i was dropped off from two bsd lists a while ago, > probably that crash someone mentioned about. > > only now (after finding time to read the email back-log i have) > did i find that the other list i dropped off from was cvs. for me > (and anyone else) running current, that is very, very, very bad > thing to happen. specially since the time i noticed this was two > weeks later. > > now, i feel quite pissed off about the fact there appears to be no > backups or anything, since i wasnt put back into the lists. > > and, whoever didnt have backups, could make me feel much better if > the lost cvs-emails would be emailed me now. ftp://ftp.freebsd.org/pub/FreeBSD/mailing-lists/archive Organized by mailinglist name, split into sections by date. -Dan Nelson dnelson@emsphone.com From owner-freebsd-current Thu Feb 5 10:45:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02931 for current-outgoing; Thu, 5 Feb 1998 10:45:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02925 for ; Thu, 5 Feb 1998 10:44:58 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id SAA29026; Thu, 5 Feb 1998 18:44:55 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id TAA03343; Thu, 5 Feb 1998 19:44:55 +0100 (MET) Message-ID: <19980205194454.64968@follo.net> Date: Thu, 5 Feb 1998 19:44:54 +0100 From: Eivind Eklund To: Mark Mayo Cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' References: <199802041917.UAA27971@daneel.stuyts.nl> <199802042233.RAA01464@dyson.iquest.net> <19980204235910.49629@vmunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19980204235910.49629@vmunix.com>; from Mark Mayo on Wed, Feb 04, 1998 at 11:59:10PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Wed, Feb 04, 1998 at 11:59:10PM -0500, Mark Mayo wrote: > Well, I just cvsup'ed and have been pounding my box with "real world" > workstation type use.. I have 32MB of RAM, and I ran several > copies of Netscape, Hey - which Netscape? I've got 64M and 141M swap, and I'm getting 'out of swap space' _often_ with just a single Netscape 4.04 and a couple of Netscape-windows. I've got a couple of related things that might be of significance - I have bktr in the kernel, run 1600x1200x16-bit resolution, and I'm running XFree. Eivind, who just thought he was way too low on swap... From owner-freebsd-current Thu Feb 5 10:56:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA05913 for current-outgoing; Thu, 5 Feb 1998 10:56:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alexis.videotron.ca (ppp189.117.mmtl.videotron.net [207.253.117.189]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA05902 for ; Thu, 5 Feb 1998 10:56:42 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost [127.0.0.1]) by alexis.videotron.ca (8.8.8/8.8.8) with ESMTP id NAA00250 for ; Thu, 5 Feb 1998 13:52:27 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DA0A69.D60EE489@videotron.ca> Date: Thu, 05 Feb 1998 13:52:26 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Current@FreeBSD.ORG Subject: Current dying horribly when using lp0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Maybe it will help shed some light on why both my computers keep rebooting... Last time it crashed, instead of simply rebooting it did a trap 12. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x7993b183 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0113fc8 stack pointer = 0x10:0xf01f89d0 frame pointer = 0x10:0xf01f89dc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 218 (ftpd) interrupt mask = net tty bio cam trap number = 12 panic: page fault I don't really know what conclusion can be reached from that (if any can) but some light would surely be appreciated. Regards -- Stephane E. Potvin sepotvin@videotron.ca From owner-freebsd-current Thu Feb 5 11:18:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10836 for current-outgoing; Thu, 5 Feb 1998 11:18:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10811 for ; Thu, 5 Feb 1998 11:18:27 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id OAA00727 for current@freebsd.org; Thu, 5 Feb 1998 14:18:23 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802051918.OAA00727@dyson.iquest.net> Subject: Comment about -current bug reports To: current@FreeBSD.ORG Date: Thu, 5 Feb 1998 14:18:23 -0500 (EST) 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Please, whenever reporting a bug about -current, specify the date (and even time) of your last update to your source tree. When someone says that there is a problem with -current, since there is no time associated with the name "-current", I cannot tell if the problem is an old one and has been fixed or hasn't been fixed yet. So, if a bug report simply says "I am having this or that problem with -current", it might be ignored because of a lack of needed and critical info. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Thu Feb 5 11:36:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13964 for current-outgoing; Thu, 5 Feb 1998 11:36:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alexis.videotron.ca (ppp189.117.mmtl.videotron.net [207.253.117.189]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13959 for ; Thu, 5 Feb 1998 11:36:15 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost [127.0.0.1]) by alexis.videotron.ca (8.8.8/8.8.8) with ESMTP id OAA00313 for ; Thu, 5 Feb 1998 14:32:01 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DA13B0.E4FE52A2@videotron.ca> Date: Thu, 05 Feb 1998 14:32:01 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Current@FreeBSD.ORG Subject: Problems with lp0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hmm, as it seems I was one of those to whom the last note of John applied, here is the requested info: First machine (ALEXIS) is FreeBSD 3.0-CURRENT Feb 5 13:31:11 EST 1998 Second machine (AZIMOV) is FreeBSD 3.0-CURRENT Feb 3 19:11:21 EST 1998 The one freezing is ALEXIS. Alexis is a P5 166Mhz, 32M ram, 128M swap Azimov is an IBM TP760XD, P5 166Mhz MMX, 32M ram, 64M swap Except for the lp0 problem between the two computer, they seems to be fairly stable. I beated both of them pretty hard and didn't get any problem with it (except for the little exercice the swap got :) If any more information is needed please don't hesitate to ask me (dmesg output, config file, ....) Now I'm to the point of splitting everything I must transfer between the two in chunks of 256k... Regards -- Stephane E. Potvin sepotvin@videotron.ca From owner-freebsd-current Thu Feb 5 12:06:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17896 for current-outgoing; Thu, 5 Feb 1998 12:06:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17891 for ; Thu, 5 Feb 1998 12:06:08 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id UAA02432; Thu, 5 Feb 1998 20:06:03 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id VAA03582; Thu, 5 Feb 1998 21:06:02 +0100 (MET) Message-ID: <19980205210602.39210@follo.net> Date: Thu, 5 Feb 1998 21:06:02 +0100 From: Eivind Eklund To: Eivind Eklund Cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' References: <199802041917.UAA27971@daneel.stuyts.nl> <199802042233.RAA01464@dyson.iquest.net> <19980204235910.49629@vmunix.com> <19980205194454.64968@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19980205194454.64968@follo.net>; from Eivind Eklund on Thu, Feb 05, 1998 at 07:44:54PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Thu, Feb 05, 1998 at 07:44:54PM +0100, Eivind Eklund wrote: > On Wed, Feb 04, 1998 at 11:59:10PM -0500, Mark Mayo wrote: > > Well, I just cvsup'ed and have been pounding my box with "real world" > > workstation type use.. I have 32MB of RAM, and I ran several > > copies of Netscape, > > Hey - which Netscape? I've got 64M and 141M swap, and I'm getting > 'out of swap space' _often_ with just a single Netscape 4.04 and a > couple of Netscape-windows. > > I've got a couple of related things that might be of significance - I > have bktr in the kernel, run 1600x1200x16-bit resolution, and I'm > running XFree. > > Eivind, who just thought he was way too low on swap... And in case anybody wonders - this has been going on for months, and is still present in a -current kernel of 15h ago. I don't think Johns changes has anything to do with it. Eivind. From owner-freebsd-current Thu Feb 5 12:15:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19654 for current-outgoing; Thu, 5 Feb 1998 12:15:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19647 for ; Thu, 5 Feb 1998 12:15:34 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id PAA01016; Thu, 5 Feb 1998 15:15:26 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802052015.PAA01016@dyson.iquest.net> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <19980205210602.39210@follo.net> from Eivind Eklund at "Feb 5, 98 09:06:02 pm" To: eivind@yes.no (Eivind Eklund) Date: Thu, 5 Feb 1998 15:15:26 -0500 (EST) Cc: eivind@yes.no, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Eivind Eklund said: > On Thu, Feb 05, 1998 at 07:44:54PM +0100, Eivind Eklund wrote: > > On Wed, Feb 04, 1998 at 11:59:10PM -0500, Mark Mayo wrote: > > > Well, I just cvsup'ed and have been pounding my box with "real world" > > > workstation type use.. I have 32MB of RAM, and I ran several > > > copies of Netscape, > > > > Hey - which Netscape? I've got 64M and 141M swap, and I'm getting > > 'out of swap space' _often_ with just a single Netscape 4.04 and a > > couple of Netscape-windows. > > > > I've got a couple of related things that might be of significance - I > > have bktr in the kernel, run 1600x1200x16-bit resolution, and I'm > > running XFree. > > > > Eivind, who just thought he was way too low on swap... > > And in case anybody wonders - this has been going on for months, and > is still present in a -current kernel of 15h ago. > > I don't think Johns changes has anything to do with it. > When you think that the system is running low on swap, send me a copy of all of the VM info that you can: 1) for i in /proc/*/map do echo $i:: cat $i done >mapinfo 2) vmstat -s 3) vmstat -m 4) pstat -s 5) ps -xla 6) sysctl kern 7) sysctl vm 8) sysctl vfs Kernel config file, dmesg, etc. This should be a reasonably large part of the info that I can digest. (I don't think that there is any private info in these items, but check it just in case.) I'll try to look at it. You don't have to wait until you actually run out of swap to send me the info. Just make sure that you have used a large part of your swap space. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Thu Feb 5 13:03:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25953 for current-outgoing; Thu, 5 Feb 1998 13:03:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tor-adm1.nbc.netcom.ca (dacole@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25948 for ; Thu, 5 Feb 1998 13:03:53 -0800 (PST) (envelope-from dacole@netcom.ca) Received: from localhost (dacole@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id QAA17997 for ; Thu, 5 Feb 1998 16:03:49 -0500 (EST) X-Authentication-Warning: tor-adm1.nbc.netcom.ca: dacole owned process doing -bs Date: Thu, 5 Feb 1998 16:03:49 -0500 (EST) From: Dave Cole X-Sender: dacole@tor-adm1 cc: current@FreeBSD.ORG Subject: Re: ncr 875 activity LED In-Reply-To: <34D93A4B.41C67EA6@inficad.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Wed, 4 Feb 1998, Richard S. Straka wrote: -Dave Cole wrote: -> -> I have noticed that my pII running 3.0-971225-SNAP doesn't light up -> its ASUS SC875 ultra wide SCSI host interface's led during activity. -> It lights up fine during boot and while running Win95 but it is -> totally dim while FreeBSD is running. -> -> I thought it might just be me but I recently heard of a friend who is -> running 2.2.5-Stable that also noticed his LED not doing anything. - -Try adding - -options SCSI_NCR_SYMBIOS_COMPAT - -to your kernel configuration file. Works like a charm! Thanks! (of course, I'm assuming this was the fix, even though I also cvsup'd to 971223,12h00 and installed that at the same time as the new kernel. ------------------------------------------------------------- Dave Cole (DC1110) | dacole@netcom.ca Systems Administrator | dacole@vex.net | office/~dacole/ Netcom Canada | www.vex.net/~dacole/ 905 King Street West, Toronto, M6K 3G9 | phone - 416.341.5801 Toronto, Ontario, Canada, Earth, Sol | fax - 416.341.5725 From owner-freebsd-current Thu Feb 5 13:15:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27264 for current-outgoing; Thu, 5 Feb 1998 13:15:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27247 for ; Thu, 5 Feb 1998 13:15:04 -0800 (PST) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.8.8/8.6.9) with ESMTP id WAA00541; Thu, 5 Feb 1998 22:15:39 +0100 (CET) Message-Id: <199802052115.WAA00541@peedub.muc.de> X-Mailer: exmh version 2.0.1 12/23/97 To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' Reply-To: Gary Jennejohn In-reply-to: Your message of "Wed, 04 Feb 1998 04:05:26 PST." <199802041205.EAA00926@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Feb 1998 22:15:39 +0100 From: Gary Jennejohn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Amancio Hasty writes: > >Just finished building xemacs20 on my pentium on a nfs partition previously >the system would lock up solid. I didn't have X running this time nor the >previous times which the system used to crashed while building xemacs. > >For sure I owed you a beer ! > can you run the new xemacs on the pentium as non-root without it complaining that memory is exhausted ? I've been seeing this problem for a few days on my P5. xemacs only works if I suid it to root. I do not see this problem on my PPro at work under -current. Otherwise things are just peachy-keen now. Thanks, John ! Oh yeah: FreeBSD 3.0-CURRENT #0: Thu Feb 5 21:17:02 CET 1998 & CTM 3239 (has John's commits from yesterday in it). --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com From owner-freebsd-current Thu Feb 5 13:23:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29066 for current-outgoing; Thu, 5 Feb 1998 13:23:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29057 for ; Thu, 5 Feb 1998 13:23:44 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id QAA01386; Thu, 5 Feb 1998 16:23:21 -0500 (EST) (envelope-from toor) Message-Id: <199802052123.QAA01386@dyson.iquest.net> Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <199802052115.WAA00541@peedub.muc.de> from Gary Jennejohn at "Feb 5, 98 10:15:39 pm" To: garyj@muc.de Date: Thu, 5 Feb 1998 16:23:21 -0500 (EST) Cc: hasty@rah.star-gate.com, current@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Gary Jennejohn said: > Amancio Hasty writes: > > > >Just finished building xemacs20 on my pentium on a nfs partition previously > >the system would lock up solid. I didn't have X running this time nor the > >previous times which the system used to crashed while building xemacs. > > > >For sure I owed you a beer ! > > > > can you run the new xemacs on the pentium as non-root without it > complaining that memory is exhausted ? I've been seeing this problem > for a few days on my P5. xemacs only works if I suid it to root. > > I do not see this problem on my PPro at work under -current. > What are your ulimits? I wonder if something odd happened with your login.conf or other way of modifying your ulimits? -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Thu Feb 5 13:41:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02466 for current-outgoing; Thu, 5 Feb 1998 13:41:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02458; Thu, 5 Feb 1998 13:41:03 -0800 (PST) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199802052141.NAA02458@hub.freebsd.org> Subject: Re: *hmph* In-Reply-To: <199802051608.SAA23230@shadows.aeon.net> from mika ruohotie at "Feb 5, 98 06:08:02 pm" To: bsdcur@shadows.aeon.net (mika ruohotie) Date: Thu, 5 Feb 1998 13:41:03 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" mika ruohotie wrote: > probably not to the right list, but anyway... > > it appears that i was dropped off from two bsd lists a while ago, > probably that crash someone mentioned about. > > only now (after finding time to read the email back-log i have) > did i find that the other list i dropped off from was cvs. for me > (and anyone else) running current, that is very, very, very bad > thing to happen. specially since the time i noticed this was two > weeks later. > > now, i feel quite pissed off about the fact there appears to be no > backups or anything, since i wasnt put back into the lists. > > and, whoever didnt have backups, could make me feel much better if > the lost cvs-emails would be emailed me now. i am sorry that your address was lost from the some of the FreeBSD mailing lists. in self defense, i must say that i sent mail twice to FreeBSD announce asking people to check their subscriptions. you can ftp all the mailing lists from ftp://ftp.freebsd.org/pub/freebsd/mailing-lists/archive/...... (modulo upper/lower case, etc......) please check your subscriptions. jmb From owner-freebsd-current Thu Feb 5 14:40:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14012 for current-outgoing; Thu, 5 Feb 1998 14:40:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA13758 for ; Thu, 5 Feb 1998 14:38:54 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg by adelphi.physics.adelaide.edu.au (5.65/AndrewR-930902) id AA24470; Fri, 6 Feb 1998 09:08:34 +1030 Received: by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA22995; Fri, 6 Feb 1998 09:09:44 +1030 Date: Fri, 6 Feb 1998 09:09:43 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Eivind Eklund Cc: Mark Mayo , current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: <19980205194454.64968@follo.net> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Thu, 5 Feb 1998, Eivind Eklund wrote: > On Wed, Feb 04, 1998 at 11:59:10PM -0500, Mark Mayo wrote: > > Well, I just cvsup'ed and have been pounding my box with "real world" > > workstation type use.. I have 32MB of RAM, and I ran several > > copies of Netscape, > > Hey - which Netscape? I've got 64M and 141M swap, and I'm getting > 'out of swap space' _often_ with just a single Netscape 4.04 and a > couple of Netscape-windows. Netscape 4.04 seems to handle memory caching of webpages _woefully_. Whenever I run NS4 with a memory cache size set above 0, it invariably dies after an hour of browsing or less, complaining about being out of memory (despite the fact that free swap space remains on the machine). This problem was noticed by others some time late last year, and since then I had been running with memory (and disk) caches set to 0kb (and pointing my browser to an apache web-cache I installed locally) but when I recently gave it some of its' own memory cache again I'm seeing the same thing. I'd be interested to hear of any other fixes to this problem which dont impact so much on performance (perhaps it's just the way I've got apache set up, but I dont get all that stunning performance from the cache :) Kris From owner-freebsd-current Thu Feb 5 15:44:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24790 for current-outgoing; Thu, 5 Feb 1998 15:44:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24703 for ; Thu, 5 Feb 1998 15:43:30 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id CAA28422 for freebsd-current@freebsd.org; Fri, 6 Feb 1998 02:36:49 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id CAA01853 for ; Fri, 6 Feb 1998 02:43:02 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802052343.CAA01853@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-current@FreeBSD.ORG Subject: DIAGNOSTIC kernels broken Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Feb 1998 02:43:02 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" vm/vm_zone.h depends on DIAGNOSTIC but doesn't include "opt_diagnostic.h". This (I believe) and the fact that I use 'config -n' just caused my last kernel to panic on reboot. I feel it would be better to put DIAGNOSTIC to opt_global.h. Dima From owner-freebsd-current Thu Feb 5 16:00:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28666 for current-outgoing; Thu, 5 Feb 1998 16:00:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28624 for ; Thu, 5 Feb 1998 16:00:24 -0800 (PST) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id RAA25564 for ; Thu, 5 Feb 1998 17:00:23 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp04.primenet.com, id smtpd025521; Thu Feb 5 17:00:15 1998 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id RAA27563 for current@freebsd.org; Thu, 5 Feb 1998 17:00:12 -0700 (MST) From: Terry Lambert Message-Id: <199802060000.RAA27563@usr09.primenet.com> Subject: PATCH: new option for newsyslog To: current@FreeBSD.ORG Date: Fri, 6 Feb 1998 00:00:12 +0000 (GMT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" When debugging problems that show up in the logs, it's useful to be able to zero the logs. But you don't want to lose the existing log data, you just want to start over with a clean slate. I have added a "-F" option ("Force") to newsyslog to force it to rotate the logs, even if the rotation criteria have not been met. Here are the (trivial) patches to the program itself and to the man page for the program. Please commit these... PS: still waiting for a "Bcc:" option for send-pr so I can Cc: a copy of these bug reports to send-pr... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. --------------------------------------------------------------------------- Index: newsyslog.8 =================================================================== RCS file: /cvs/freebsd/src/usr.sbin/newsyslog/newsyslog.8,v retrieving revision 1.9 diff -c -r1.9 newsyslog.8 *** newsyslog.8 1997/10/06 07:46:06 1.9 --- newsyslog.8 1998/02/05 23:30:44 *************** *** 152,157 **** --- 152,163 ---- will not be able to send a HUP signal to .Xr syslogd 8 so this option should only be used in debugging. + .It Fl F + Force + .Nm + to trim the logs, even if the trim conditions have not been met. This + option is useful for diagnosing system problems by providing you with + fresh logs that contain only the problems. .El .Sh FILES .Bl -tag -width /etc/newsyslog.confxxxx -compact Index: newsyslog.c =================================================================== RCS file: /cvs/freebsd/src/usr.sbin/newsyslog/newsyslog.c,v retrieving revision 1.15 diff -c -r1.15 newsyslog.c *** newsyslog.c 1997/11/30 18:58:18 1.15 --- newsyslog.c 1998/02/05 23:30:44 *************** *** 89,94 **** --- 89,95 ---- int verbose = 0; /* Print out what's going on */ int needroot = 1; /* Root privs are necessary */ int noaction = 0; /* Don't do anything, just show it */ + int force = 0; /* Force the tim no matter what*/ char *conf = CONF; /* Configuration file to use */ time_t timenow; pid_t syslog_pid; /* read in from /etc/syslog.pid */ *************** *** 159,165 **** printf("size (Kb): %d [%d] ", size, ent->size); if (verbose && (ent->hours > 0)) printf(" age (hr): %d [%d] ", modtime, ent->hours); ! if (((ent->size > 0) && (size >= ent->size)) || ((ent->hours > 0) && ((modtime >= ent->hours) || (modtime < 0)))) { if (verbose) --- 160,167 ---- printf("size (Kb): %d [%d] ", size, ent->size); if (verbose && (ent->hours > 0)) printf(" age (hr): %d [%d] ", modtime, ent->hours); ! if (force || ! ((ent->size > 0) && (size >= ent->size)) || ((ent->hours > 0) && ((modtime >= ent->hours) || (modtime < 0)))) { if (verbose) *************** *** 201,207 **** } optind = 1; /* Start options parsing */ ! while ((c=getopt(argc,argv,"nrvf:t:")) != -1) switch (c) { case 'n': noaction++; /* This implies needroot as off */ --- 203,209 ---- } optind = 1; /* Start options parsing */ ! while ((c=getopt(argc,argv,"nrvFf:t:")) != -1) switch (c) { case 'n': noaction++; /* This implies needroot as off */ *************** *** 215,220 **** --- 217,225 ---- case 'f': conf = optarg; break; + case 'F': + force = 1; + break; default: usage(); } --------------------------------------------------------------------------- From owner-freebsd-current Thu Feb 5 16:07:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA01263 for current-outgoing; Thu, 5 Feb 1998 16:07:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA01257 for ; Thu, 5 Feb 1998 16:07:15 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id AAA08665; Fri, 6 Feb 1998 00:07:13 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id BAA00479; Fri, 6 Feb 1998 01:07:12 +0100 (MET) Message-ID: <19980206010712.58740@follo.net> Date: Fri, 6 Feb 1998 01:07:12 +0100 From: Eivind Eklund To: Dmitrij Tejblum Cc: freebsd-current@FreeBSD.ORG Subject: Re: DIAGNOSTIC kernels broken References: <199802052343.CAA01853@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199802052343.CAA01853@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Fri, Feb 06, 1998 at 02:43:02AM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Fri, Feb 06, 1998 at 02:43:02AM +0300, Dmitrij Tejblum wrote: > vm/vm_zone.h depends on DIAGNOSTIC but doesn't include "opt_diagnostic.h". > This (I believe) and the fact that I use 'config -n' just caused my last > kernel to panic on reboot. Something is weird with your setup, I believe. vm_zone.c includes opt_diagnostic.h as of revision 1.16, which was part of the "Turn DIAGNOSTIC into a new-style option" commit. You don't have a sticky tag on sys/vm or something? > I feel it would be better to put DIAGNOSTIC to opt_global.h. Possibly. I dislike the present state, too, and have been tempted by that simple solution (as it is less likely to bit-rot than the present one). Eivind. From owner-freebsd-current Thu Feb 5 18:22:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA24917 for current-outgoing; Thu, 5 Feb 1998 18:22:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24739; Thu, 5 Feb 1998 18:22:20 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.7) with ESMTP id TAA07385; Thu, 5 Feb 1998 19:04:31 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199802051904.TAA07385@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Phil Staub cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: PPP In-reply-to: Your message of "Tue, 03 Feb 1998 20:32:21 PST." <199802040432.UAA01493@casa.plan.pixelogix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Feb 1998 19:04:30 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > Brian: > > A quick (I hope) question re: ppp-980123.src.tar.gz downloaded from > your page. > > Have you disabled the telnet connection in this version? I got a > "connection refused" when I tried to telnet into it on port > 3000. (Yes, I remembered to disable the pppctl socket.) It worked fine > on the version from 2.2.5-STABLE. You have to use `set socket' these days. There's none by default for security reasons. > Thanks, > Phil > -- > Phil Staub, KE7HC Senior Software Engineer > phils@pixelogix.com Audio Precision, Inc. > or phils@audioprecision.com Beaverton, OR 97075, (800) 231-7350 -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-current Thu Feb 5 18:28:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26822 for current-outgoing; Thu, 5 Feb 1998 18:28:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26757 for ; Thu, 5 Feb 1998 18:27:58 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id AAA12892; Fri, 6 Feb 1998 00:27:52 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199802060227.AAA12892@gaia.coppe.ufrj.br> Subject: Re: PATCH: new option for newsyslog In-Reply-To: <199802060000.RAA27563@usr09.primenet.com> from Terry Lambert at "Feb 6, 98 00:00:12 am" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 6 Feb 1998 00:27:52 -0200 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" #define quoting(Terry Lambert) // When debugging problems that show up in the logs, it's useful to // be able to zero the logs. Yes, but does rotating ALL the logs really helps ? For example, I don't want to rotate the maillog if the problem is not concerned to mail system. Maybe you could define another file, but then you could also define another set of ranges for this newsyslog file, so small that almost always the log would rotate. If it does not rotate, then it's probably not worth doing so. For example, a file with more than 1K should be rotated. A file with less than 1K is not big enough to make trouble reading it. If it's not enough, just make newsyslog support rotate size or rotate time values as zero. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-current Thu Feb 5 20:28:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA21893 for current-outgoing; Thu, 5 Feb 1998 20:28:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA21884 for ; Thu, 5 Feb 1998 20:28:41 -0800 (PST) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id XAA15170; Thu, 5 Feb 1998 23:33:32 -0500 (EST) (envelope-from mark) Message-ID: <19980205233332.61812@vmunix.com> Date: Thu, 5 Feb 1998 23:33:32 -0500 From: Mark Mayo To: Eivind Eklund Cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' References: <199802041917.UAA27971@daneel.stuyts.nl> <199802042233.RAA01464@dyson.iquest.net> <19980204235910.49629@vmunix.com> <19980205194454.64968@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <19980205194454.64968@follo.net>; from Eivind Eklund on Thu, Feb 05, 1998 at 07:44:54PM +0100 X-Operating-System: FreeBSD 2.2.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Thu, Feb 05, 1998 at 07:44:54PM +0100, Eivind Eklund wrote: > On Wed, Feb 04, 1998 at 11:59:10PM -0500, Mark Mayo wrote: > > Well, I just cvsup'ed and have been pounding my box with "real world" > > workstation type use.. I have 32MB of RAM, and I ran several > > copies of Netscape, > > Hey - which Netscape? I've got 64M and 141M swap, and I'm getting > 'out of swap space' _often_ with just a single Netscape 4.04 and a > couple of Netscape-windows. I use the stand-alone Navigator version (4.04). I don't get out of swap space messages. The only thing I can think of is that all of my limits are set to infinity. > > I've got a couple of related things that might be of significance - I > have bktr in the kernel, run 1600x1200x16-bit resolution, and I'm > running XFree. FWIW I run XFree 3.3.1 at 1152x900x16, using the Millenium video card. > > Eivind, who just thought he was way too low on swap... What does pstat -s or vmstat or top show when netscape claims to be out of swap space? -Mark P.S. For anybody else out there who wants to torture test an X workstation like I did, my only advice is to get really used to how far you need to move your mouse relative to screen position. Under huge swapping/disk activity successfully using a mouse is the largest challenge. I recomend learning how to use all your WM's hot keys for popping between apps! 8-) -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-current Thu Feb 5 20:57:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26371 for current-outgoing; Thu, 5 Feb 1998 20:57:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from casa.plan.pixelogix.com (casagate.plan.pixelogix.com [206.129.249.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA26309; Thu, 5 Feb 1998 20:57:22 -0800 (PST) (envelope-from phils@casa.plan.pixelogix.com) Received: (from phils@localhost) by casa.plan.pixelogix.com (8.8.8/8.8.5) id UAA04398; Thu, 5 Feb 1998 20:56:44 -0800 (PST) Date: Thu, 5 Feb 1998 20:56:44 -0800 (PST) Message-Id: <199802060456.UAA04398@casa.plan.pixelogix.com> From: Phil Staub To: brian@Awfulhak.org CC: current@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: <199802051904.TAA07385@awfulhak.org> (message from Brian Somers on Thu, 05 Feb 1998 19:04:30 +0000) Subject: Re: PPP References: <199802051904.TAA07385@awfulhak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > > A quick (I hope) question re: ppp-980123.src.tar.gz downloaded from > > your page. > > > > Have you disabled the telnet connection in this version? I got a > > "connection refused" when I tried to telnet into it on port > > 3000. (Yes, I remembered to disable the pppctl socket.) It worked fine > > on the version from 2.2.5-STABLE. > > You have to use `set socket' these days. There's none by default for > security reasons. > I suspected as much. I *was* able to get pppctl to work via the socket. However, the references to telnet are still in the man page (although I do seem to recall seeing references to the possibility that telnet may go away at some point.) (Not a complaint, mind you, just thought it deserved to be mentioned.) BTW, thanks for your efforts to update and improve PPP. They are appreciated! -- Phil Staub, KE7HC Senior Software Engineer phils@pixelogix.com Audio Precision, Inc. or phils@audioprecision.com Beaverton, OR 97075, (800) 231-7350 From owner-freebsd-current Thu Feb 5 21:21:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA29471 for current-outgoing; Thu, 5 Feb 1998 21:21:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA29453 for ; Thu, 5 Feb 1998 21:21:06 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA03850; Thu, 5 Feb 1998 20:26:13 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802060426.UAA03850@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-current@FreeBSD.ORG cc: Julian Elischer Subject: Remote gdb ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Feb 1998 20:26:13 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Does anyone know what can cause "Reply contains invalid hex digit 116" ? Tnks, Amancio (kgdb) set remotebaud 38400 (kgdb) target remote /dev/cuaa0 Remote debugging using /dev/cuaa0 Debugger (msg=0xf01f33eb "manual escape to debugger") at ../../i386/i386/db_interface.c:319 319 } (kgdb) frame #0 Debugger (msg=0xf01f33eb "manual escape to debugger") at ../../i386/i386/db_interface.c:319 319 } (kgdb) cont Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. Debugger (msg=0xf0117874 "panic") at ../../i386/i386/db_interface.c:317 317 in_Debugger = 0; (kgdb) frame #0 Debugger (Ignoring packet error, continuing... msg=Reply contains invalid hex digit 116 ) at ../../i386/i386/db_interface.c:317 317 in_Debugger = 0; (kgdb) {root} stty -f /dev/cuaa0 speed 38400 baud; lflags: -icanon -isig -iexten -echo iflags: -icrnl -ixon -ixany -imaxbel -brkint oflags: -opost -onlcr -oxtabs cflags: cs8 -parenb clocal min time 0 20 From owner-freebsd-current Thu Feb 5 21:30:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01512 for current-outgoing; Thu, 5 Feb 1998 21:30:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01506 for ; Thu, 5 Feb 1998 21:30:22 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id PAA07058; Fri, 6 Feb 1998 15:59:00 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id PAA19954; Fri, 6 Feb 1998 15:59:00 +1030 (CST) (envelope-from grog) Message-ID: <19980206155859.02035@freebie.lemis.com> Date: Fri, 6 Feb 1998 15:58:59 +1030 From: Greg Lehey To: Amancio Hasty , freebsd-current@FreeBSD.ORG Cc: Julian Elischer Subject: Re: Remote gdb ? References: <199802060426.UAA03850@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802060426.UAA03850@rah.star-gate.com>; from Amancio Hasty on Thu, Feb 05, 1998 at 08:26:13PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Thu, 5 February 1998 at 20:26:13 -0800, Amancio Hasty wrote: > > Does anyone know what can cause "Reply contains invalid hex digit 116" ? At a guess, it's an overrun. I haven't been able to get remote gdb to work reliably above 9600 bps. In fact, I haven't been able to get it to work reliably at all, but at least at 9600 bps I don't have any transmission errors :-) Of course, I don't believe it's a hex digit at all. I'd guess it's decimal (0x74 hex, or 't'). Is it repeatable? From what you show below, it appears to be intermittent. Greg > > Tnks, > Amancio > > (kgdb) set remotebaud 38400 > (kgdb) target remote /dev/cuaa0 > Remote debugging using /dev/cuaa0 > Debugger (msg=0xf01f33eb "manual escape to debugger") > at ../../i386/i386/db_interface.c:319 > 319 } > (kgdb) frame > #0 Debugger (msg=0xf01f33eb "manual escape to debugger") > at ../../i386/i386/db_interface.c:319 > 319 } > (kgdb) cont > Continuing. > > Program received signal SIGTRAP, Trace/breakpoint trap. > Debugger (msg=0xf0117874 "panic") at ../../i386/i386/db_interface.c:317 > 317 in_Debugger = 0; > (kgdb) frame > #0 Debugger (Ignoring packet error, continuing... > msg=Reply contains invalid hex digit 116 > ) at ../../i386/i386/db_interface.c:317 > 317 in_Debugger = 0; > (kgdb) > {root} stty -f /dev/cuaa0 > speed 38400 baud; > lflags: -icanon -isig -iexten -echo > iflags: -icrnl -ixon -ixany -imaxbel -brkint > oflags: -opost -onlcr -oxtabs > cflags: cs8 -parenb clocal > min time > 0 20 From owner-freebsd-current Thu Feb 5 21:39:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02863 for current-outgoing; Thu, 5 Feb 1998 21:39:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02839 for ; Thu, 5 Feb 1998 21:39:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id VAA04226; Thu, 5 Feb 1998 21:39:00 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802060539.VAA04226@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Greg Lehey cc: freebsd-current@FreeBSD.ORG, Julian Elischer Subject: Re: Remote gdb ? In-reply-to: Your message of "Fri, 06 Feb 1998 15:58:59 +1030." <19980206155859.02035@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Feb 1998 21:39:00 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Oh, it happens every time after the kernel has been running. The first that the debugger breaks it seems to work okay after it doesn't work. Tnks, Amancio From owner-freebsd-current Thu Feb 5 22:13:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08680 for current-outgoing; Thu, 5 Feb 1998 22:13:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08675 for ; Thu, 5 Feb 1998 22:13:02 -0800 (PST) (envelope-from tlambert@usr06.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id XAA03505; Thu, 5 Feb 1998 23:12:55 -0700 (MST) Received: from usr06.primenet.com(206.165.6.206) via SMTP by smtp04.primenet.com, id smtpd003460; Thu Feb 5 23:12:46 1998 Received: (from tlambert@localhost) by usr06.primenet.com (8.8.5/8.8.5) id XAA04400; Thu, 5 Feb 1998 23:12:44 -0700 (MST) From: Terry Lambert Message-Id: <199802060612.XAA04400@usr06.primenet.com> Subject: Re: PATCH: new option for newsyslog To: jonny@coppe.ufrj.br (Joao Carlos Mendes Luis) Date: Fri, 6 Feb 1998 06:12:43 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <199802060227.AAA12892@gaia.coppe.ufrj.br> from "Joao Carlos Mendes Luis" at Feb 6, 98 00:27:52 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > #define quoting(Terry Lambert) > // When debugging problems that show up in the logs, it's useful to > // be able to zero the logs. > > Yes, but does rotating ALL the logs really helps ? > > For example, I don't want to rotate the maillog if the problem is not > concerned to mail system. That's what I thought, until I found out that the reason smtpd was getting read timeouts was because the ppp link went down, and not as a result of a bug in smtpd. It's also what I thought when sendmail wasn't processing its outbound mail, until I examined the kernel and firewall logs and saw that an inbound TCP packet reject was either dumping the system or dumping the process before it could finish processing. > Maybe you could define another file, but then you could also define > another set of ranges for this newsyslog file, so small that almost > always the log would rotate. If it does not rotate, then it's probably > not worth doing so. When a consultant dials into site he's supporting, he would rather fix the problem than diddle lock files. Remember that the data is not lost, only forcibly rotated so that you can examine only the data during the period of time when the costomer is demonstrating the problem to you. > For example, a file with more than 1K should be rotated. A file > with less than 1K is not big enough to make trouble reading it. The kernel log is frequently 1k, and it contains things like "WARNING: / was not cleanly unmounted" (ie: your system silently rebooted) or "kernel: panic: pahe fault in kernel mode". What's worth reading is relative. What is definitely *not* worth reading is all of the log information that occurred before the attempt at demonstration. The only way to mark that point in time easily is to zero the log files. I could just as easily do: cd /var/log zap=`find . -name "*[^0-9]"` for i in $zap do cat /dev/null > $i done But then, of course, I'd lose information which may not be pertinent to the current problem, but which I wouldn't want to lose. > If it's not enough, just make newsyslog support rotate size or > rotate time values as zero. Ugh. Then I have to know what's in the existing newsyslog.conf so I can make a modified version of it. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Feb 6 01:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA08309 for current-outgoing; Fri, 6 Feb 1998 01:40:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (root@dnttm.wave.ras.ru [194.85.104.197]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA08241 for ; Fri, 6 Feb 1998 01:40:00 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.8.5/8.8.5/IP-3) with UUCP id MAA01034; Fri, 6 Feb 1998 12:37:15 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.8.8/8.8.7) with ESMTP id MAA01329; Fri, 6 Feb 1998 12:43:20 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199802060943.MAA01329@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: Eivind Eklund cc: freebsd-current@FreeBSD.ORG Subject: Re: DIAGNOSTIC kernels broken In-reply-to: Your message of "Fri, 06 Feb 1998 01:07:12 +0100." <19980206010712.58740@follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Feb 1998 12:43:20 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Eivind Eklund wrote: > On Fri, Feb 06, 1998 at 02:43:02AM +0300, Dmitrij Tejblum wrote: > > vm/vm_zone.h depends on DIAGNOSTIC but doesn't include "opt_diagnostic.h". ^^ > > Something is weird with your setup, I believe. vm_zone.c includes ^^ > opt_diagnostic.h as of revision 1.16, which was part of the "Turn DIAGNOSTIC > into a new-style option" commit. I talk about vm_zone.h, not vm_zone.c. vm_zone.h contains several inline functions, which depends on DIAGNOSTIC. These functions is part of vm_zone external interface, and used in such files as kern_fork.c, and kern_exit.c, and others, which doesn't include opt_diagnostic.h. Dima From owner-freebsd-current Fri Feb 6 01:48:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09465 for current-outgoing; Fri, 6 Feb 1998 01:48:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09459 for ; Fri, 6 Feb 1998 01:48:22 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id JAA21781; Fri, 6 Feb 1998 09:48:19 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id KAA08355; Fri, 6 Feb 1998 10:48:18 +0100 (MET) Message-ID: <19980206104818.51201@follo.net> Date: Fri, 6 Feb 1998 10:48:18 +0100 From: Eivind Eklund To: Dmitrij Tejblum Cc: Eivind Eklund , freebsd-current@FreeBSD.ORG Subject: Re: DIAGNOSTIC kernels broken References: <19980206010712.58740@follo.net> <199802060943.MAA01329@tejblum.dnttm.rssi.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199802060943.MAA01329@tejblum.dnttm.rssi.ru>; from Dmitrij Tejblum on Fri, Feb 06, 1998 at 12:43:20PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Fri, Feb 06, 1998 at 12:43:20PM +0300, Dmitrij Tejblum wrote: > Eivind Eklund wrote: > > On Fri, Feb 06, 1998 at 02:43:02AM +0300, Dmitrij Tejblum wrote: > > > vm/vm_zone.h depends on DIAGNOSTIC but doesn't include "opt_diagnostic.h". > ^^ > > > > Something is weird with your setup, I believe. vm_zone.c includes > ^^ > > opt_diagnostic.h as of revision 1.16, which was part of the "Turn DIAGNOSTIC > > into a new-style option" commit. > > I talk about vm_zone.h, not vm_zone.c. vm_zone.h contains several inline > functions, which depends on DIAGNOSTIC. These functions is part of vm_zone > external interface, and used in such files as kern_fork.c, and kern_exit.c, > and others, which doesn't include opt_diagnostic.h. Guilty as charged. They don't matter for an SMP kernel, which is why I didn't notice :-( I'm backing this change out and putting DIAGNOSTIC in opt_global.h. Maintaining it separately is more likely to go wrong than not. Eivind. From owner-freebsd-current Fri Feb 6 04:10:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26078 for current-outgoing; Fri, 6 Feb 1998 04:10:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26071 for ; Fri, 6 Feb 1998 04:10:04 -0800 (PST) (envelope-from kato@migmatite.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.8/3.6Wbeta7) with ESMTP id VAA03294 for ; Fri, 6 Feb 1998 21:09:59 +0900 (JST) To: current@FreeBSD.ORG Subject: unionfs clobbers a file From: KATO Takenori X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980206210958N.kato@gneiss.eps.nagoya-u.ac.jp> Date: Fri, 06 Feb 1998 21:09:58 +0900 X-Dispatcher: imput version 971024 Lines: 24 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Current major problem of unionfs is: Writing a file via unionfs sometimes clobbers the file. When new file is created and modified on unionfs, a part of the file is filled by zero. The size of zero-filled part is always multiple of 4096 bytes. Easy way to reproduce the problem is: # mount -t union /foo /usr/obj # cd /usr/src # make world When you got signal 11 or other error, please see /usr/obj/usr/src/tmp/usr/bin/make and /usr/obj/usr/src/usr.bin/make/.depend. One of them contains zero- filled field. Do you have any idea to solve it? ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- From owner-freebsd-current Fri Feb 6 05:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10543 for current-outgoing; Fri, 6 Feb 1998 05:37:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shadows.aeon.net (shadows.aeon.net [194.100.41.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10484 for ; Fri, 6 Feb 1998 05:37:14 -0800 (PST) (envelope-from bsdcur@shadows.aeon.net) Received: (from bsdcur@localhost) by shadows.aeon.net (8.8.8/8.8.3) id PAA07757; Fri, 6 Feb 1998 15:36:55 +0200 (EET) From: mika ruohotie Message-Id: <199802061336.PAA07757@shadows.aeon.net> Subject: Re: *hmph* In-Reply-To: from Steve Kargl at "Feb 5, 98 09:12:17 am" To: sgk@troutmask.apl.washington.edu (Steve Kargl) Date: Fri, 6 Feb 1998 15:36:55 +0200 (EET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > >it appears that i was dropped off from two bsd lists a while ago, > >probably that crash someone mentioned about. > Several people had accidentally been dropped from mailing lists, > so don't take it personally. i didnt. > FreeBSD is a VOLUNTEER effort. FreeBSD.org is hosted on machines > by Walnut Creek Cdrom for FREE. If you wish to make a significant > monetary contribution to ensure that major disk failures and their > subsequent replacement goes smoothly, I'm sure Walnut Creek Cdrom > will not complain. i'm sure i will do it the first day i can afford to do it. > http://www.freebsd.org/cgi/cvsweb.cgi ops, i did not know such a thing exists... basicly, what i wanted, was that someone would tell me that there is some method for me to read those missed cvs-all messages. my mistake was to post the question while in a bad mood, so i worded it in a most wrong way. > Oh, did I mention that FreeBSD is a volunteer effort. i apologized, and will do again. will it make it look any "better" for me if i mention that i'm in the middle of a major project merging our netbsd servers into freebsd? =) (why? coz i know frisbee better, and coz of the x86 platforms, and coz of cvsup and /usr/ports and 10001 other things) > Steve mickey From owner-freebsd-current Fri Feb 6 06:45:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21129 for current-outgoing; Fri, 6 Feb 1998 06:45:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from versa.eng.comsat.com (root@versa.eng.comsat.com [134.133.169.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21109; Fri, 6 Feb 1998 06:45:45 -0800 (PST) (envelope-from marc@versa.eng.comsat.com) Received: (from marc@localhost) by versa.eng.comsat.com (8.8.5/8.7.3) id JAA07866; Fri, 6 Feb 1998 09:44:35 -0500 (EST) Date: Fri, 6 Feb 1998 09:44:35 -0500 (EST) From: Marc Giannoni Message-Id: <199802061444.JAA07866@versa.eng.comsat.com> To: brian@Awfulhak.org, phils@casagate.plan.pixelogix.com Subject: Re: PPP Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Pardon: Uhh...i i'm having the same problem myself. i cant seem to get 'allow users' to do anything in 'ppp.conf'. I really feel clueless, i miss using port 3000 to hang up the phone! is there a sample 'ppp.conf' around with this in it? marc From owner-freebsd-current Fri Feb 6 10:06:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22078 for current-outgoing; Fri, 6 Feb 1998 10:06:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA22073 for ; Fri, 6 Feb 1998 10:06:44 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id KAA10114; Fri, 6 Feb 1998 10:06:31 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802061806.KAA10114@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: Greg Lehey cc: freebsd-current@FreeBSD.ORG, Julian Elischer Subject: Re: Remote gdb ? In-reply-to: Your message of "Fri, 06 Feb 1998 15:58:59 +1030." <19980206155859.02035@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Feb 1998 10:06:31 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Nope, gdb remote is broken on -current. Cheers, Amancio > On Thu, 5 February 1998 at 20:26:13 -0800, Amancio Hasty wrote: > > > > Does anyone know what can cause "Reply contains invalid hex digit 116" ? > > At a guess, it's an overrun. I haven't been able to get remote gdb to > work reliably above 9600 bps. In fact, I haven't been able to get it > to work reliably at all, but at least at 9600 bps I don't have any > transmission errors :-) > > Of course, I don't believe it's a hex digit at all. I'd guess it's > decimal (0x74 hex, or 't'). Is it repeatable? From what you show > below, it appears to be intermittent. > > Greg > > > > > Tnks, > > Amancio > > > > (kgdb) set remotebaud 38400 > > (kgdb) target remote /dev/cuaa0 > > Remote debugging using /dev/cuaa0 > > Debugger (msg=0xf01f33eb "manual escape to debugger") > > at ../../i386/i386/db_interface.c:319 > > 319 } > > (kgdb) frame > > #0 Debugger (msg=0xf01f33eb "manual escape to debugger") > > at ../../i386/i386/db_interface.c:319 > > 319 } > > (kgdb) cont > > Continuing. > > > > Program received signal SIGTRAP, Trace/breakpoint trap. > > Debugger (msg=0xf0117874 "panic") at ../../i386/i386/db_interface.c:317 > > 317 in_Debugger = 0; > > (kgdb) frame > > #0 Debugger (Ignoring packet error, continuing... > > msg=Reply contains invalid hex digit 116 > > ) at ../../i386/i386/db_interface.c:317 > > 317 in_Debugger = 0; > > (kgdb) > > {root} stty -f /dev/cuaa0 > > speed 38400 baud; > > lflags: -icanon -isig -iexten -echo > > iflags: -icrnl -ixon -ixany -imaxbel -brkint > > oflags: -opost -onlcr -oxtabs > > cflags: cs8 -parenb clocal > > min time > > 0 20 From owner-freebsd-current Fri Feb 6 11:26:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07877 for current-outgoing; Fri, 6 Feb 1998 11:26:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07871 for ; Fri, 6 Feb 1998 11:26:20 -0800 (PST) (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id MAA05503; Fri, 6 Feb 1998 12:26:19 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd005468; Fri Feb 6 12:26:10 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id MAA15103; Fri, 6 Feb 1998 12:26:08 -0700 (MST) From: Terry Lambert Message-Id: <199802061926.MAA15103@usr01.primenet.com> Subject: Re: unionfs clobbers a file To: kato@migmatite.eps.nagoya-u.ac.jp (KATO Takenori) Date: Fri, 6 Feb 1998 19:26:08 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <19980206210958N.kato@gneiss.eps.nagoya-u.ac.jp> from "KATO Takenori" at Feb 6, 98 09:09:58 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > Current major problem of unionfs is: > Writing a file via unionfs sometimes clobbers the file. > > When new file is created and modified on unionfs, a part of the file > is filled by zero. The size of zero-filled part is always multiple of > 4096 bytes. Easy way to reproduce the problem is: > > # mount -t union /foo /usr/obj > # cd /usr/src > # make world > > When you got signal 11 or other error, please see > /usr/obj/usr/src/tmp/usr/bin/make and > /usr/obj/usr/src/usr.bin/make/.depend. One of them contains zero- > filled field. > > Do you have any idea to solve it? 4096 bytes is a page. Pages are hung off the vnode, when the vnode pager is using the file for backing store. Because of the way vnodes stack, and the lack of a general mechanism for obtaining the backing vnode for a given vnode at the top of a stack, combined with the lack of general support for VOP_GETPAGES and VOP_PUTPAGES in all local media FS implementations, and the vnpager havking a lack of knowledge of whether a given FS is implemented on local media, aliases are created. If I have a vnode that is the local media vnode, and it has pages in place, and I create an overlay vnode, and it has aliases for those pages, then I can get into a situation where the overlay vnode and the local media vnode have the same pages referenced as existing, but only one has copies of the disk pages. When this happens, and you reference the page from the wrong vnode, you get a zero filled page instead, just as you would when extending a file or accessing a page in a sparse file. The easy fix is to modify the vnode pager to not know about where the pages are located on the vnode. This will have two consequences: 1) You *must* support VOP_GETPAGES/VOP_PUTPAGES in local media filesystems for them to continue to work. If you do this, then the "bypass" mechanism of the stacking vnode architecture will "do the right thing" for FS's that do not have these functions in their vnops structure, and the aliases will go away. 2) Most stacking FS's will start to work, except where they've been modified, like the commits that have been threatened to the umapfs. The easy fix is *WRONG*. The unionfs will, in fact, still not work (I think it won't; you can probably kludge it) because of VOP_LOCK and VOP_ADVLOCK. There are deadlocks and recursion panics. The harder fix is to add a VOP_FINALVP to all local media filesystems. Adding a VOP_FINALVP will allow an upper layer to get the backing vnode for a VM object, not matter how buried by other stacks it becomes. This fix will have three consequences: 1) The vnode pager *must* be modified to call VOP_FINALVP to get the backing object on which it is going to operate, instead of using page aliases from random vnode in the stack. If you do this, then the "bypass" mechanism of the stacking vnode architecture will "do the right thing" for FS's that do not have this function in their vnops structure, and the aliases will go away. 2) The advisory locking will need to be hung off a pointer in the generic vnode, instead of off a pointer in the FS specific inode. All advisory locks should be asserted in upper level code instead of in FS code, and should be veto based. The upper level code will use the VOP_FINALVP to get the backing node(s) for the lock range. The locks will then be associated with the data they are locking. 3) Most stacking FS's will start to work, except where they've been modified, like the commits that have been threatened to the umapfs. The unionfs, as a multiplexer, *will* work for VOP_ADVLOCK, since it implements the bypass and no longer has to assert sub-locks on per FS objects. An FS which agregates multiple vp's into a single vp will still need to maintain alias coherency. This is a much smaller problem; the upper level code will assert the VOP_ADVLOCK against the alias vp, and the VOP_ADVLOCK, instead of being a null "non-veto" of the assert, will have to do the assert into the lower layers. This will generally be a non-problem. There are currently no FS's which do this, at this time, and the places where it *is* done are handled as drivers (the vnconfig and ccd code), which is probably the correct way to do it anyway. The unionfs may still fail because of VOP_LOCK, depending on how it is implemented this week. If it's still using the lockmgr code, it will definitely fail, because that code projects a three dimensional geodesic into a two dimensional space. I can explain how to fix this, if you are interested. Generally, allowing the lock to recurse could make it run, but would leave a race condition in the case where the projected image of the lock relationship could have come from the shadow of more than one possible geodesic (make a triangle out of straws and hold it upt to a projection screen until you only see a line and you will approximate the problem). I have, at various times, posted the code to implement the second fix to the -current mailing list; the code should be in the archives (the VOP_ADVLOCK/veto code will be listed under "NFS Client locking"). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Feb 6 12:11:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16596 for current-outgoing; Fri, 6 Feb 1998 12:11:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16559 for ; Fri, 6 Feb 1998 12:11:23 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id PAA00937; Fri, 6 Feb 1998 15:10:58 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199802062010.PAA00937@dyson.iquest.net> Subject: Re: unionfs clobbers a file In-Reply-To: <199802061926.MAA15103@usr01.primenet.com> from Terry Lambert at "Feb 6, 98 07:26:08 pm" To: tlambert@primenet.com (Terry Lambert) Date: Fri, 6 Feb 1998 15:10:58 -0500 (EST) Cc: kato@migmatite.eps.nagoya-u.ac.jp, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Terry Lambert said: > > Pages are hung off the vnode, when the vnode pager is using the file > for backing store. > Pages are hung off of a VM object, which might optionally be aliased by multiple vnodes. > > The harder fix is to add a VOP_FINALVP to all local media filesystems. > Adding a VOP_FINALVP will allow an upper layer to get the backing > vnode for a VM object, not matter how buried by other stacks it becomes. > This fix will have three consequences: > I kind of like that. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Fri Feb 6 14:07:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10452 for current-outgoing; Fri, 6 Feb 1998 14:07:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10280; Fri, 6 Feb 1998 14:05:56 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.org (8.8.7/8.8.7) with ESMTP id VAA25715; Fri, 6 Feb 1998 21:25:48 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199802062125.VAA25715@awfulhak.org> X-Mailer: exmh version 2.0.1 12/23/97 To: Marc Giannoni cc: brian@Awfulhak.org, phils@casagate.plan.pixelogix.com, current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: PPP In-reply-to: Your message of "Fri, 06 Feb 1998 09:44:35 EST." <199802061444.JAA07866@versa.eng.comsat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Feb 1998 21:25:47 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > Pardon: > > Uhh...i > i'm having the same problem myself. i cant seem to get 'allow users' to do > anything in 'ppp.conf'. I really feel clueless, i miss using port 3000 > to hang up the phone! is there a sample 'ppp.conf' around with this in it? > marc There are examples in /etc/ppp/ppp.conf.sample. Just ``allow users *'' and ``set server 3000 ""'' in the default section and it'll be the same as in the old days. -- Brian , , Don't _EVER_ lose your sense of humour.... From owner-freebsd-current Fri Feb 6 14:46:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15468 for current-outgoing; Fri, 6 Feb 1998 14:46:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA15462 for ; Fri, 6 Feb 1998 14:46:04 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 4107 invoked from network); 6 Feb 1998 22:46:01 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 6 Feb 1998 22:46:01 -0000 Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.8.8/8.8.8) with ESMTP id OAA03856 for ; Fri, 6 Feb 1998 14:46:02 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199802062246.OAA03856@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-current@FreeBSD.ORG Subject: cvs bug (and fix) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Feb 1998 14:46:02 -0800 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" This one's been driving me batshit for the last couple of days. I'm surprised no one else has encountered it yet. Line 6016 in /usr/src/contrib/cvs/src/rcs.c needs to be changed from if (n == EOF) to if (n == EOF || num == NULL) Otherwise you get spurious assert's in findnode() a little later on. Can someone change, approve, and check this in? TIA --scooter -- Scott Michel | In life, there are sheep and there are UCLA Computer Science | wolves. PhD Graduate Student | I don't bleat. From owner-freebsd-current Fri Feb 6 15:17:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19938 for current-outgoing; Fri, 6 Feb 1998 15:17:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bigbrother ([206.29.49.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA19828 for ; Fri, 6 Feb 1998 15:16:47 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by bigbrother (8.6.12/8.6.9) id TAA04617 for ; Fri, 6 Feb 1998 19:10:39 -0500 Received: from fault.rstcorp.com(206.29.49.18) by bigbrother.rstcorp.com via smap (V2.0) id xma004613; Fri, 6 Feb 98 19:10:03 -0500 Received: (from vshah@localhost) by rstcorp.com (8.8.1/8.8.1) id SAA02102; Fri, 6 Feb 1998 18:15:21 -0500 (EST) Date: Fri, 6 Feb 1998 18:15:21 -0500 (EST) Message-Id: <199802062315.SAA02102@rstcorp.com> From: "Viren R. Shah" To: freebsd-current@FreeBSD.ORG Subject: 3.0-980206-SNAP install panics on a Dell PowerEdge 2200/266 X-Mailer: VM 6.40 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hi, I tried to install 3.0-980206 on a Dell PowerEdge 2200/266 and it would install. It panic'ed right after the probe messages as follows: ... rootfs is 1440 Kbyte compiled in MFS vm_page_free: pindex(0),busy(0),PG_BUSY(0),hold(0) panic: vm_page_free: freeing free page Note that this machine is currently (happily) getting the 3.0-971225 SNAP installed on it. Any ideas? [I'm installing FreeBSD on this machine jsut to test SMP capabilities on it, and it is not a permanent install.] Viren -- Viren R. Shah, viren @ rstcorp . com, http://www.rstcorp.com/~vshah/ If you understand what you're doing, you are not learning anything From owner-freebsd-current Fri Feb 6 15:32:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22125 for current-outgoing; Fri, 6 Feb 1998 15:32:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22120 for ; Fri, 6 Feb 1998 15:32:53 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id KAA09814; Sat, 7 Feb 1998 10:02:47 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA27585; Sat, 7 Feb 1998 10:02:47 +1030 (CST) (envelope-from grog) Message-ID: <19980207100247.60298@freebie.lemis.com> Date: Sat, 7 Feb 1998 10:02:47 +1030 From: Greg Lehey To: Amancio Hasty Cc: freebsd-current@FreeBSD.ORG, Julian Elischer Subject: Re: Remote gdb ? References: <19980206155859.02035@freebie.lemis.com> <199802061806.KAA10114@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802061806.KAA10114@rah.star-gate.com>; from Amancio Hasty on Fri, Feb 06, 1998 at 10:06:31AM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Fri, 6 February 1998 at 10:06:31 -0800, Amancio Hasty wrote: >> On Thu, 5 February 1998 at 20:26:13 -0800, Amancio Hasty wrote: >>> >>> Does anyone know what can cause "Reply contains invalid hex digit 116" ? >> >> At a guess, it's an overrun. I haven't been able to get remote gdb to >> work reliably above 9600 bps. In fact, I haven't been able to get it >> to work reliably at all, but at least at 9600 bps I don't have any >> transmission errors :-) >> >> Of course, I don't believe it's a hex digit at all. I'd guess it's >> decimal (0x74 hex, or 't'). Is it repeatable? From what you show >> below, it appears to be intermittent. > > Nope, gdb remote is broken on -current. Where do you get that idea from? It has numerous problems, but it definitely works. I've been using it for the last several weeks. Greg From owner-freebsd-current Fri Feb 6 16:28:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28615 for current-outgoing; Fri, 6 Feb 1998 16:28:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.178]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28610 for ; Fri, 6 Feb 1998 16:28:20 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id QAA29431; Fri, 6 Feb 1998 16:28:04 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199802070028.QAA29431@rah.star-gate.com> To: Greg Lehey cc: Amancio Hasty , freebsd-current@FreeBSD.ORG, Julian Elischer , hasty@rah.star-gate.com Subject: Re: Remote gdb ? In-reply-to: Your message of "Sat, 07 Feb 1998 10:02:47 +1030." <19980207100247.60298@freebie.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29427.886811284.1@rah> Date: Fri, 06 Feb 1998 16:28:04 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Have you tried -current as of about 4 days ago or so? Cheers, Amancio From owner-freebsd-current Fri Feb 6 17:02:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05073 for current-outgoing; Fri, 6 Feb 1998 17:02:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05007 for ; Fri, 6 Feb 1998 17:02:42 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id LAA09948; Sat, 7 Feb 1998 11:32:38 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA27989; Sat, 7 Feb 1998 11:32:37 +1030 (CST) (envelope-from grog) Message-ID: <19980207113237.32138@freebie.lemis.com> Date: Sat, 7 Feb 1998 11:32:37 +1030 From: Greg Lehey To: Amancio Hasty Cc: freebsd-current@FreeBSD.ORG, Julian Elischer Subject: Re: Remote gdb ? References: <19980207100247.60298@freebie.lemis.com> <199802070028.QAA29431@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <199802070028.QAA29431@rah.star-gate.com>; from Amancio Hasty on Fri, Feb 06, 1998 at 04:28:04PM -0800 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Fri, 6 February 1998 at 16:28:04 -0800, Amancio Hasty wrote: > Have you tried -current as of about 4 days ago or so? -rwxr-xr-x 1 root wheel 1644553 Jan 31 18:00 /kernel Has it broken since then? Greg From owner-freebsd-current Fri Feb 6 18:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14335 for current-outgoing; Fri, 6 Feb 1998 18:08:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gneiss.eps.nagoya-u.ac.jp (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14327 for ; Fri, 6 Feb 1998 18:08:07 -0800 (PST) (envelope-from kato@migmatite.eps.nagoya-u.ac.jp) Received: from localhost (localhost [127.0.0.1]) by gneiss.eps.nagoya-u.ac.jp (8.8.8/3.6Wbeta7) with ESMTP id LAA11333; Sat, 7 Feb 1998 11:07:57 +0900 (JST) To: tlambert@primenet.com Cc: current@FreeBSD.ORG Subject: Re: unionfs clobbers a file From: KATO Takenori In-Reply-To: Your message of "Fri, 6 Feb 1998 19:26:08 +0000 (GMT)" <199802061926.MAA15103@usr01.primenet.com> References: <199802061926.MAA15103@usr01.primenet.com> X-Mailer: Mew version 1.92.4 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19980207110757B.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 07 Feb 1998 11:07:57 +0900 X-Dispatcher: imput version 971024 Lines: 18 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Terry Lambert wrote: > The unionfs may still fail because of VOP_LOCK, depending on how > it is implemented this week. If it's still using the lockmgr code, > it will definitely fail, because that code projects a three dimensional > geodesic into a two dimensional space. I can explain how to fix > this, if you are interested. Please explain it. I think lock/unlock system in unionfs is somethink like ropewalking and current implemetation is a result of compromise. ---- KATO Takenori Dept. Earth Planet. Sci., Nagoya Univ., Nagoya, 464-01, Japan PGP public key: finger kato@eclogite.eps.nagoya-u.ac.jp ------------------- Powered by FreeBSD(98) ------------------- From owner-freebsd-current Fri Feb 6 18:55:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21932 for current-outgoing; Fri, 6 Feb 1998 18:55:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gloria.cord.edu (gloria.cord.edu [138.129.254.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21926; Fri, 6 Feb 1998 18:55:34 -0800 (PST) (envelope-from twschulz@gloria.cord.edu) Received: from localhost (twschulz@localhost) by gloria.cord.edu (8.8.5/8.6.5) with SMTP id UAA22734; Fri, 6 Feb 1998 20:55:26 -0600 (CST) Date: Fri, 6 Feb 1998 20:55:26 -0600 (CST) From: Trenton Schulz To: freebsd-questions@FreeBSD.ORG cc: freebsd-current@FreeBSD.ORG Subject: Fat32 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" I was wondering whether FAT32 was implemented in -current. If that is so, I would gladly be a tester for it or something. Thanks, Trenton Schulz twschulz@cord.edu From owner-freebsd-current Fri Feb 6 19:29:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26353 for current-outgoing; Fri, 6 Feb 1998 19:29:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26344 for ; Fri, 6 Feb 1998 19:29:04 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id BAA08161; Sat, 7 Feb 1998 01:28:50 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199802070328.BAA08161@gaia.coppe.ufrj.br> Subject: Re: PATCH: new option for newsyslog In-Reply-To: <199802060612.XAA04400@usr06.primenet.com> from Terry Lambert at "Feb 6, 98 06:12:43 am" To: tlambert@primenet.com (Terry Lambert) Date: Sat, 7 Feb 1998 01:28:50 -0200 (EDT) Cc: jonny@coppe.ufrj.br, tlambert@primenet.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" #define quoting(Terry Lambert) // When a consultant dials into site he's supporting, he would rather // fix the problem than diddle lock files. Remember that the data // is not lost, only forcibly rotated so that you can examine only // the data during the period of time when the costomer is demonstrating // the problem to you. Ok. You don't know where the problem is yet, and want to search everywhere for it, in the least time possible, having no other description of the problem except the customer's comment. Then I agree with your option. It'll create a "log window" in which you can search every log file for problems. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-current Fri Feb 6 19:34:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27226 for current-outgoing; Fri, 6 Feb 1998 19:34:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27208; Fri, 6 Feb 1998 19:34:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id TAA03469; Fri, 6 Feb 1998 19:32:59 -0800 (PST) Message-Id: <199802070332.TAA03469@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Andrzej Bialecki cc: Terry Lambert , freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-reply-to: Your message of "Thu, 05 Feb 1998 10:40:21 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Feb 1998 19:32:58 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > A bit of background, if you're interested: I'm working on the next version > of PicoBSD, and after some shuffling with the layout and adding new > features I found that I can no longer fit into 8MB RAM... I.e. it fits, > but I can't start enough processes to make a dialup connection. What does the process listing look like? (use ddb and the 'ps' command rather than try to squeeze 'ps' into the crunch image). > There was one really nasty surprise which I experienced: the way the > gzipped binaries are executed. It wastes a LOT of RAM. How else would you do it? You can't easily page off an LZW-compressed image (for obvious reasons), so you have to put the uncompressed thing *somewhere*. Have you shrunk the kernel as much as possible? > I had some ideas how to fix it, but the implementation of this is far > beyond my knowledge: to modify imgact_gzip NOT to load the gzipped binary, > but just to mmap it, and then unpack it. When I asked John Dyson he said > that it would require a lot of work to change it... Pity. I'm not sure I follow you there. The imgact_gzip code doesn't load the gzipped binary at all; it mmap's it one page at a time, uncompressing it as it goes. > Also, IMHO it would be a good option to the kernel and/or ld.so to tell > them not to load .text at all (it could apply to .text section of binaries > as well as shared libs), just to mmap it, if the backing filesystem is of > MFS type. For non-gzip binaries, execution starts by mmapping the entire text section, and jumping to it. Nothing is "loaded" in any case. What you're suggesting really is "execute-in-place", which is quite a tough thing to implement. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com From owner-freebsd-current Fri Feb 6 19:47:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29410 for current-outgoing; Fri, 6 Feb 1998 19:47:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (root@lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29400 for ; Fri, 6 Feb 1998 19:47:35 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (markham.southpeak.com [192.58.185.8]) by lamb.sas.com (8.8.7/8.8.7) with SMTP id WAA04616 for ; Fri, 6 Feb 1998 22:47:21 -0500 (EST) Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA14688; Fri, 6 Feb 1998 22:47:20 -0500 From: "John W. DeBoskey" Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA14637; Fri, 6 Feb 1998 22:47:20 -0500 Message-Id: <199802070347.AA14637@iluvatar.unx.sas.com> Subject: Re: Remote gdb ? To: freebsd-current@FreeBSD.ORG Date: Fri, 6 Feb 1998 22:47:20 -0500 (EST) X-Mailer: ELM [version 2.4 PL23] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Hi, I've been using remote gdb as of the 0204 snap to debug some NFS issues.. YMMV, John > Nope, gdb remote is broken on -current. > Have you tried -current as of about 4 days ago or so? > > Cheers, > Amancio -- jwd@unx.sas.com (w) John W. De Boskey (919) 677-8000 x6915 From owner-freebsd-current Fri Feb 6 19:50:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00287 for current-outgoing; Fri, 6 Feb 1998 19:50:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA00260; Fri, 6 Feb 1998 19:50:29 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id WAA00681; Fri, 6 Feb 1998 22:50:01 -0500 (EST) (envelope-from toor) Message-Id: <199802070350.WAA00681@dyson.iquest.net> Subject: Re: Custom init(8) (and some ideas) In-Reply-To: <199802070332.TAA03469@dingo.cdrom.com> from Mike Smith at "Feb 6, 98 07:32:58 pm" To: mike@smith.net.au (Mike Smith) Date: Fri, 6 Feb 1998 22:50:01 -0500 (EST) Cc: abial@nask.pl, tlambert@primenet.com, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Mike Smith said: > > > I had some ideas how to fix it, but the implementation of this is far > > beyond my knowledge: to modify imgact_gzip NOT to load the gzipped binary, > > but just to mmap it, and then unpack it. When I asked John Dyson he said > > that it would require a lot of work to change it... Pity. > > I'm not sure I follow you there. The imgact_gzip code doesn't load > the gzipped binary at all; it mmap's it one page at a time, > uncompressing it as it goes. > I think that I might have misinformed here. Gzipped binaries need swap backing store for each page in the image even for .text section, when physical memory space needs to be freed for another page. Non-gzipped binaries can depend on paging off of the a.out itself. Also, non-gzipped binaries don't have to page out the .text for the initial freeing of the .text space. Gzipped binaries need to page out the .text pages when they are individually freed due to pageout daemon activity. Also, gzipped binaries are not demand-loaded, but are loaded at startup. This guarantees that the entire image will have to be supported by either memory or swap space. During normal program execution (normal a.out, ELF, etc), the entire image doesn't have to be initially loaded, and you can get by with the size of the image being larger than the size of physical memory + swap space (of course, that is a special case need, but it is possible to do.) In the case of a gzipped binary, that isn't true. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. From owner-freebsd-current Fri Feb 6 20:29:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA04825 for current-outgoing; Fri, 6 Feb 1998 20:29:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA04820 for ; Fri, 6 Feb 1998 20:29:42 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id VAA02934; Fri, 6 Feb 1998 21:29:37 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd002911; Fri Feb 6 21:29:36 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA25084; Fri, 6 Feb 1998 21:29:33 -0700 (MST) From: Terry Lambert Message-Id: <199802070429.VAA25084@usr05.primenet.com> Subject: Re: unionfs clobbers a file To: kato@migmatite.eps.nagoya-u.ac.jp (KATO Takenori) Date: Sat, 7 Feb 1998 04:29:33 +0000 (GMT) Cc: tlambert@primenet.com, current@FreeBSD.ORG In-Reply-To: <19980207110757B.kato@gneiss.eps.nagoya-u.ac.jp> from "KATO Takenori" at Feb 7, 98 11:07:57 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > > The unionfs may still fail because of VOP_LOCK, depending on how > > it is implemented this week. If it's still using the lockmgr code, > > it will definitely fail, because that code projects a three dimensional > > geodesic into a two dimensional space. I can explain how to fix > > this, if you are interested. > > Please explain it. > > I think lock/unlock system in unionfs is somethink like ropewalking > and current implemetation is a result of compromise. OK, this delves into the "What if I already had an implementation that used VOP_FINALVP to avoid alias problems" case. To understand it, you first need to know why advisory locks have to be veto-based to work for an agregating FS (one that presents the buffers of two vnodes as a an agregate that looks like one set of buffers on one vnode). This is a simpler analogy to the VOP_LOCK in unionfs case because it demonstrates the dimensionality and reversibility problem without needing me to draw a two color perspective drawing in ASCII art. 8-). This is because, for the purposes of VOP_LOCK, any FS which implements a multiplexer will agregate the vnode locks under some circumstances; the union FS is one such FS. The mount point traversal code in a translucent FS mounted into the same directory as exports its root is another case. When you agregate two objects (be they block lists or be they directory block lists) under a single vnode pointer, you end up with a case where the operation must be idempotent but can not be atomic (this means that you must either do everything or nothing, and that you can't, by definition, do everything at once). Say I have a new FS type, called "AGFS". It's purpose is to replace CCD, and do transparent file concatenation. When one FS runs out of room writing the file, the next write starts a new file in the next FS. Now, after I've written this file, I have something that looks like: vp[1] (AGFS, size 100 blocks) / \ (FFS, size 80 blocks) vp[2] vp[3] (FFS, size 20 blocks) I come back later to open this file. So far, so good. Now I want to set an advisory lock on 20 blocks: 70 through 90. This advisory lock needs to span two underlying objects (regardless of whether I implement the VOP_ADVLOCK chain off the vp or the ip in the underlying implementation, this is true). So I assert a lock on vp[1]. The AGFS asserts the lock on both vp[2] and vp[3] in the underlying FS's. Now we have problems: IF !VOP_ADVLOCK(vp[2]) FAIL /* this is OK; we can fail back*/ IF !VOP_ADVLOCK(vp[3]) FAIL /* this is bad; recovery is indeterminate*/ Why can't we recover from the second failure? The reason we can't recover is that the first operation has succeeded, and as a result, we have coelesced the lock list for that vp. This may have resulted in promotions or demotions. of the lock state. When can this happen in real life? It can happen when we start with something like this: [ SSS ][ XXX ] [ 111 ][ 222 ] (process 1 holds a shared lock and process 2 holds an exclusive lock), and we want to assert a new lock: [ XXXXX][XX ] [ 11111][11 ] After the first statement, we have: ** [ SXXXXX][ XXX ] [ 111111][ 222 ] (* lock promoted from S to X, previous state lost) The second statement fails, because the last part of the lock would conflict with the lock from process 2. Now let's look at the VOP_LOCK case for a directory traversal, and specifically look at the race condition for the parent unlock when traversing to the child (this is a well known race, which is handled by generation numbers in the flat stack case). When the traversal crosses the agregation boundry, the race is greatly expanded. This is less of a problem if one of the FS's is mounted read-only... but only if you don't permit white-outs. In the non-read-only case, we must hold the parent (upper level) lock twice: there are two parent spaces: one for the stack relationship, and one for the underlying parent/child relationship. You can illustrate the same problem with a translucent fs, where you have /a/b/c and you remount c in /a/b/d. The d/c traversal means that the lookup prior needs to do a b->b transition. You could probably kludge all of these border cases using a recursion flag, and specific equality testing, if you had to. Or you could delay the coelesce, buying you an additional dimension, and then make the call down to the second one, and decide to abort the coelesce instead, when the second call fails. A delayed coelesce only buys you a single dimensionality, however; if you did something like: vp (union) / \ vp vp (union) / \ vp vp Then the problem just comes back; only now you can't solve it. The fix is to make both the VOP_LOCK and VOP_ADVLOCK use veto interfaces; then you can ask the layer if the lock can proceed, and if it can, then you run it to completion. The one limitation here is that you can only have a single FINALVP that needs a proxy mechanism, unless the proxy coelesce is also reversible (an NFS client FS employs a proxy mechanism where it must actually remotely assert the lock to determine if the lock can be asserted. This is a flay in the NFS protocol, as is the inability to proxy VOP_IOCTL requests). In reality, if you are not referencing the backing object for the vnode (the in-core inode, nfsnode, or whatever), then you can apply a single lock to the backing vnodes alone. You are still left with the fact that if you assert one NFS lock, it will be remotely coelesced, and then if you assert another NFS lock, and the assertion fails, you can't back the first out. One way out of this bind is to maintain a lock list locally, and manufacture PID's for the lock requests so that a coelesce does not take place on the remote server. This means you must keep an interference graph locally to match them up. The NFS rpc.lockd needs to have similar code. In any case, if I can only have a single dimensionality from a delayed coelesce, I'd rather spend it on a remote FS, and make multiple stacks work. Right now, you don't even have one extra dimensionality. To drag myself back on the specific subject, though, a union FS has a loss of dimensionality, and you end up with something that looks like: vp1' / \ vp2' vp1 / \ vp2 vp3 Where vp1' shadows vp1 and vp2' shadows vp2 in the flat space managed by the lockmgr() code (visualize vp1' floating over vp1, and if there is both a vp2' and a vp2, they float over each other and result in a conflict because you don't know which one you are supposed to be going to when you traverse down from vp1'/vp1). The vp1'/vp1 shadowing is not a problem (you can special case "self"). The vp2'/vp2 shadowing does not always occur in practice (mostly it's vp4' off of vp1', so you don't have a space conflict), but when it does, then you lock recursively and get a "locking against myself" error. This shadowing is the same shadowing that's currently causing your panic's in the buffer alias case. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Feb 6 20:34:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA05613 for current-outgoing; Fri, 6 Feb 1998 20:34:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA05577; Fri, 6 Feb 1998 20:34:24 -0800 (PST) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id VAA03766; Fri, 6 Feb 1998 21:34:18 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp02.primenet.com, id smtpd003742; Fri Feb 6 21:34:14 1998 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA25379; Fri, 6 Feb 1998 21:34:09 -0700 (MST) From: Terry Lambert Message-Id: <199802070434.VAA25379@usr05.primenet.com> Subject: Re: Custom init(8) (and some ideas) To: dyson@FreeBSD.ORG Date: Sat, 7 Feb 1998 04:34:09 +0000 (GMT) Cc: mike@smith.net.au, abial@nask.pl, tlambert@primenet.com, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG In-Reply-To: <199802070350.WAA00681@dyson.iquest.net> from "John S. Dyson" at Feb 6, 98 10:50:01 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > I think that I might have misinformed here. Gzipped binaries need swap > backing store for each page in the image even for .text section, when > physical memory space needs to be freed for another page. Non-gzipped > binaries can depend on paging off of the a.out itself. Also, non-gzipped > binaries don't have to page out the .text for the initial freeing of the > .text space. Gzipped binaries need to page out the .text pages when they > are individually freed due to pageout daemon activity. Also, gzipped > binaries are not demand-loaded, but are loaded at startup. This guarantees > that the entire image will have to be supported by either memory or swap > space. During normal program execution (normal a.out, ELF, etc), the > entire image doesn't have to be initially loaded, and you can get > by with the size of the image being larger than the size of physical > memory + swap space (of course, that is a special case need, but it is > possible to do.) In the case of a gzipped binary, that isn't true. What is the compression table flush boundry? You *could* use the gzip'ped file as a swap store, *if* you created pages out of the file on the flush boundry, since you could re-decompress the needed pages by restarting from that point. This would require (basically) a gzip-pager. You would also need to make an map (probably an RLE 0/1 bitmap) to know how many full and partial pages each decompressed to, and handle the section boundries (since they would probably not decompress to even page boundries). Heh. Feels like "SoftRAM". 8-) 8-). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-current Fri Feb 6 20:54:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08503 for current-outgoing; Fri, 6 Feb 1998 20:54:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08450; Fri, 6 Feb 1998 20:54:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id UAA03722; Fri, 6 Feb 1998 20:54:00 -0800 (PST) Message-Id: <199802070454.UAA03722@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: dyson@FreeBSD.ORG, mike@smith.net.au, abial@nask.pl, freebsd-current@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: Custom init(8) (and some ideas) In-reply-to: Your message of "Sat, 07 Feb 1998 04:34:09 GMT." <199802070434.VAA25379@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Feb 1998 20:53:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > What is the compression table flush boundry? You *could* use the > gzip'ped file as a swap store, *if* you created pages out of the > file on the flush boundry, since you could re-decompress the needed > pages by restarting from that point. It's not quite that simple. From /usr/src/lib/libz/algorithm.doc: ---8<--- Literals or match lengths are compressed with one Huffman tree, and match distances are compressed with another tree. The trees are stored in a compact form at the start of each block. The blocks can have any size (except that the compressed data for one block must fit in available memory). A block is terminated when deflate() determines that it would be useful to start another block with fresh trees. (This is somewhat similar to the behavior of LZW-based _compress_.) ---8<--- You would have to scan the entire image to locate the compression blocks, which would be a chore. > This would require (basically) a gzip-pager. You would also need > to make an map (probably an RLE 0/1 bitmap) to know how many full > and partial pages each decompressed to, and handle the section > boundries (since they would probably not decompress to even page > boundries). A table of region lengths would be more compact, but perhaps slower to traverse. This would be another one of those fun-but-distracting projects for a relatively new kernel hacker. 8) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com From owner-freebsd-current Sat Feb 7 04:14:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29044 for current-outgoing; Sat, 7 Feb 1998 04:14:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alushta.NL.net (alushta.NL.net [193.78.240.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29039 for ; Sat, 7 Feb 1998 04:14:15 -0800 (PST) (envelope-from benst@terminus.stuyts.nl) Received: from stuyts by alushta.NL.net with UUCP id <1702-25826>; Sat, 7 Feb 1998 13:14:01 +0100 Received: from daneel.stuyts.nl (daneel.stuyts.nl [193.78.231.7]) by terminus.stuyts.nl (8.8.8/8.8.8) with ESMTP id NAA19096; Sat, 7 Feb 1998 13:13:04 +0100 (MET) (envelope-from benst) Received: (from benst@localhost) by daneel.stuyts.nl (8.8.5/8.8.5) id NAA29864; Sat, 7 Feb 1998 13:12:28 +0100 (MET) Message-Id: <199802071212.NAA29864@daneel.stuyts.nl> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: <199802050743.CAA02078@dyson.iquest.net> X-Nextstep-Mailer: Mail 3.3 (Enhance 1.2) Received: by NeXT.Mailer (1.118.2) From: Ben Stuyts Date: Sat, 7 Feb 98 13:12:25 +0100 To: "John S. Dyson" Subject: Re: Any feedback on my recent kernel 'fixes' cc: current@FreeBSD.ORG Reply-To: ben@stuyts.nl References: <199802050743.CAA02078@dyson.iquest.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Thu, 5 Feb 1998, "John S. Dyson" wrote: > Try again. I just committed some code that resolves the last, currently > repeatable bug (not that there aren't more.) John, I've been running a kernel of Thu Feb 5 22:43:00 MET 1998, and I've had two spontaneous reboots. Both happened when I wasn't at the machine, and I can't find anything about it in the logs. The machine was probably mostly idle. This is something new. Here is the output of /var/log/messages: Feb 6 14:10:14 terminus xntpd[87]: sendto(130.159.62.4): No route to host Feb 6 15:09:59 terminus /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Feb 6 15:09:59 terminus /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Feb 6 15:09:59 terminus /kernel: The Regents of the University of California. All rights reserved. Feb 6 15:09:59 terminus /kernel: FreeBSD 3.0-CURRENT #0: Thu Feb 5 22:43:00 MET 1998 Feb 6 15:09:59 terminus /kernel: benst@terminus.stuyts.nl:/usr/source/src/sys/compile/TERMINUS-SMP Feb 6 15:09:59 terminus /kernel: CPU: Pentium (586-class CPU) Feb 6 15:09:59 terminus /kernel: Origin = "GenuineIntel" Id = 0x543 Stepping=3 Feb 6 15:09:59 terminus /kernel: Features=0x8003bf Feb 6 15:09:59 terminus /kernel: real memory = 67108864 (65536K bytes) Feb 6 15:09:59 terminus /kernel: avail memory = 62709760 (61240K bytes) Feb 6 15:09:59 terminus /kernel: FreeBSD/SMP: Multiprocessor motherboard Feb 6 15:09:59 terminus /kernel: cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 Feb 6 15:09:59 terminus /kernel: cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 Feb 6 15:09:59 terminus /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Feb 6 15:09:59 terminus /kernel: Probing for devices on PCI bus 0: Feb 6 15:09:59 terminus /kernel: chip0: rev 0x03 on pci0.0.0 Feb 6 15:09:59 terminus /kernel: chip1: rev 0x01 on pci0.7.0 Feb 6 15:09:59 terminus /kernel: ide_pci0: rev 0x00 on pci0.7.1 Feb 6 15:09:59 terminus /kernel: de0: rev 0x11 int a irq 17 on pci0.9.0 Feb 6 15:09:59 terminus /kernel: de0: SMC 21041 [10Mb/s] pass 1.1 Feb 6 15:09:59 terminus /kernel: de0: address 00:00:c0:1f:54:e8 Feb 6 15:09:59 terminus /kernel: vga0: rev 0x02 int a irq 18 on pci0.10.0 Feb 6 15:09:59 terminus /kernel: ahc0: rev 0x00 int a irq 19 on pci0.12.0 Feb 6 15:09:59 terminus /kernel: ahc0: Using left over BIOS settings Feb 6 15:09:59 terminus /kernel: ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBsFeb 6 15:09:59 terminus /kernel: ahc0: waiting for scsi devices to settle Feb 6 15:09:59 terminus /kernel: scbus0 at ahc0 bus 0 Feb 6 15:09:59 terminus /kernel: sd0 at scbus0 target 1 lun 0 Feb 6 15:09:59 terminus /kernel: sd0: type 0 fixed SCSI 2 Feb 6 15:09:59 terminus /kernel: sd0: Direct-Access 4134MB (8467200 512 byte sectors) Feb 6 15:09:59 terminus /kernel: sd0: with 8205 cyls, 6 heads, and an average 171 sectors/track Feb 6 15:09:59 terminus /kernel: sd1 at scbus0 target 3 lun 0 Feb 6 15:10:00 terminus /kernel: sd1: type 0 fixed SCSI 2 Feb 6 15:10:00 terminus /kernel: sd1: Direct-Access 810MB (1660299 512 byte sectors) Feb 6 15:10:00 terminus /kernel: sd1: with 3653 cyls, 4 heads, and an average 113 sectors/track Feb 6 15:10:00 terminus /kernel: cd0 at scbus0 target 4 lun 0 Feb 6 15:10:00 terminus /kernel: cd0: type 5 removable SCSI 2 Feb 6 15:10:00 terminus /kernel: cd0: CD-ROM can't get the size Feb 6 15:10:00 terminus /kernel: worm0 at scbus0 target 5 lun 0 Feb 6 15:10:00 terminus /kernel: worm0: type 5 removable SCSI 2 Feb 6 15:10:00 terminus /kernel: worm0: Write-Once Feb 6 15:10:00 terminus /kernel: Probing for PnP devices: Feb 6 15:10:00 terminus /kernel: CSN 1 Vendor ID: CTL0039 [0x39008c0e] Serial 0x00020ddb Feb 6 15:10:00 terminus /kernel: Probing for devices on the ISA bus: Feb 6 15:10:00 terminus /kernel: sc0 at 0x60-0x6f irq 1 on motherboard > Feb 6 15:10:00 terminus /kernel: sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa Feb 6 15:10:00 terminus /kernel: sio0: type 16550A Feb 6 15:10:00 terminus /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Feb 6 15:10:00 terminus /kernel: sio1: type 16550A Feb 6 15:10:00 terminus /kernel: sio2 at 0x3e8-0x3ef irq 10 on isa Feb 6 15:10:00 terminus /kernel: sio2: type 16550A Feb 6 15:10:00 terminus /kernel: sio3 at 0x2e8-0x2ef irq 9 on isa Feb 6 15:10:00 terminus /kernel: sio3: type 16550A Feb 6 15:10:00 terminus /kernel: lpt0 at 0x378-0x37f irq 7 on isa Feb 6 15:10:00 terminus /kernel: lpt0: Interrupt-driven port Feb 6 15:10:00 terminus /kernel: lp0: TCP/IP capable interface Feb 6 15:10:00 terminus /kernel: psm0 at 0x60-0x64 irq 12 on motherboard Feb 6 15:10:00 terminus /kernel: psm0: model Generic PS/2 mouse, device ID 0 Feb 6 15:10:00 terminus /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Feb 6 15:10:00 terminus /kernel: fdc0: FIFO enabled, 8 bytes threshold Feb 6 15:10:00 terminus /kernel: fd0: 1.44MB 3.5in Feb 6 15:10:00 terminus /kernel: wdc0 not found at 0x1f0 Feb 6 15:10:00 terminus /kernel: npx0 on motherboard Feb 6 15:10:00 terminus /kernel: npx0: INT 16 interface Feb 6 15:10:00 terminus /kernel: sb0 at 0x220 irq 5 drq 1 on isa Feb 6 15:10:00 terminus /kernel: snd0: Feb 6 15:10:00 terminus /kernel: sbxvi0 at ? drq 5 on isa Feb 6 15:10:00 terminus /kernel: snd0: Feb 6 15:10:01 terminus /kernel: sbmidi0 at 0x330 on isa Feb 6 15:10:01 terminus /kernel: snd0: Feb 6 15:10:01 terminus /kernel: opl0 at 0x388 on isa Feb 6 15:10:01 terminus /kernel: snd0: Feb 6 15:10:01 terminus /kernel: Intel Pentium F00F detected, installing workaround Feb 6 15:10:01 terminus /kernel: APIC_IO: routing 8254 via 8259 on pin 0 Feb 6 15:10:01 terminus /kernel: SMP: AP CPU #1 Launched! Feb 6 15:10:01 terminus /kernel: WARNING: / was not properly dismounted. Feb 6 15:10:01 terminus /kernel: de0: enabling BNC port Feb 6 15:10:01 terminus xntpd[87]: xntpd version=3.4e (beta multicast); Wed Feb 4 02:27:01 MET 1998 (1) Feb 6 15:10:01 terminus xntpd[87]: tickadj = 5, tick = 10000, tvu_maxslew = 495Feb 6 15:10:01 terminus xntpd[87]: using xntpd phase-lock loop Feb 6 15:10:02 terminus amd[121]: NIS domain name is not set. NIS ignored. Feb 6 15:10:04 terminus lpd[145]: restarted Feb 6 15:10:13 terminus /kernel: sio3: 64 events for device with no tp I am cvsupping now, so I'll let you know if things improve. Best regards, Ben From owner-freebsd-current Sat Feb 7 10:58:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14034 for current-outgoing; Sat, 7 Feb 1998 10:58:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cons.org (knight.cons.org [194.233.237.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14026 for ; Sat, 7 Feb 1998 10:58:20 -0800 (PST) (envelope-from cracauer@cons.org) Received: (from cracauer@localhost) by cons.org (8.8.5/8.7.3) id TAA23111; Sat, 7 Feb 1998 19:59:52 +0100 (CET) Message-ID: <19980207195952.24691@cons.org> Date: Sat, 7 Feb 1998 19:59:52 +0100 From: Martin Cracauer To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvs commit: src/bin/sh jobs.c References: <199802071645.DAA14279@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <199802071645.DAA14279@godzilla.zeta.org.au>; from Bruce Evans on Sun, Feb 08, 1998 at 03:45:59AM +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" [moved to current@freebsd.org] I now have a collection of tests. Start with file 'DOC'. My results are in 'OBSERVATIONS'. So far all shells fail on one test or another, but we knew that already :-) It also contains diff.bde and diff.cra, these are the diffs I used for testing. Mine differs from the commited version only in resetting signals after a failed fork(). begin 644 testsuite.tar.gz M'XL(`,NLW#0``^T MNC8`V^IU.G`+`,R>*?\"M/1?_06Z=K=G6AV[9R&69;;L6]"Y/I%R2$3L1`"W MW,AQG81%%^$MIHP%VQ!HNQ!G\^\ZL3ME4<.]')P^/!H6'<\4,W2#P&WXC8\WEC^H_B M(W\2.L'JLR3T$7/UV=@-XS4T%D6AI%8DMQ3->#EG8A4U9M',YV(3)&X.F`]@+YSAF>^L-//#R-C^,P0V8 M$R;S9_``6GO$?"R5[5C#LL]/RQ(?L/)P$?.<%P M[&'OU]SW8.J$7L`BJTK-J+Z:\6=&Z?2'9["S+Y:A"XX;^SP$_#_B$&K5JOT: M[A@`BPA]LVK6$;DN_+>,CZOXL5;;,_3,X3?CW2JW]L=P^S5 MV`#X8ZBF"JP!/0&81RC)N+ISP@2+XR2<*-VC$2$[)$HXU"]VL=V)XZB:J[`. MIP>#_:?'+^MPMS!3-?@&6BE]Y("&Q:/JCL_=.("(^$#38Z_)5E(.[PSUGQMP MP0HQ]`.4_I51:BWM:B;*EJ+U#[.NC[M2$H?+@*P_U5R=$ZD2T MJRTU&B(]<_Q03XH[Q>#FOM(.\AMASWUO&,-\$LV5B1?=/^=Y5)G!LZ-'FM.$ MQ=BM*NU`V[N2%?]7L'KT&SYG874GFX'Z\?#DT?'3)S_7:-[,S"[TK!'VN>E: M455+/J39RSB2Z,@I=DDJ_%R$Z\N";Q'1O%A,AJIUTPV>,V%SK+B*N:'JCTE17-; MC)=Y2\,=!N/`F<#=!_#?HP-TV:<7-A\>?'^\UNBZKU[\^/SH]#?D((-K95*I M[4'S'CR.^`S.Q7VXUS0^+&IE'Z%6G^%P+@BWI0I+WDPRK@Z/OCIZ>XF#I M41V#Q[I$]VJM-6;GB+8W$*49N93J!62+.MQ`^OOGSSY8WJS3Z>')#Q_02_I& MZK'/!2[7N[C>A1[^G<"81^`45D!1!_196/CQ%-N]U.D64S]@4,V"E4`$=PK5 MB#E>T=+>V:?;TJD77*C`<>/(!#G*"3FG';Y2&&\83MK2U=E&B% M0-13(]QHAII)*^6Q:760E`Z/'Z.&ICP)*".84XCE8;`$;'*=,$2\&?=8'F(N MX*8]KC@D]U7K-QK1`;+`D;_?1V^_7\`IQOYQ$J!AZ7[/_`:K?3_5^+#@IP_]^QN&$P1]^+** M3VN&\>CPV>#T^>/'B)`:AV$`\;4W9?8!78?#9\=#XY^&@Z. MGY\PT7DVB0_]QK\+^+!]XLY/Y/ MGUPQO08>IM7J]7HK_I_'`1T,E/^;9I=B@=GI],Q;8#5'?MB\'IDR^%#_OZS] M$X75^6^9C6M0MP[K%\9_V^ZEY[]M%?_MEMDJX_\VX,X7C=3S81=WK\R=#H^"G\!GM$+%3[]SPZ8'!@@6#R<2-],O;/18S*4[[XV)!1H4`1 M,"$^J6"1^_^CXX-KXG'9_J]GIOYO=7'G1^]_.ZU>Z?_;@%-R.3?RY[&`2B-? M!"ID^NF#CGQ`&SWI'=@B8@_]'(.#$QOH:$O0YTT>E_&`GL.(39W7/CH?G9BS M-W/FQLQK@`PNV&>F7)J.XEX'RP9N-[$O5&:XTZS`V(\(B\,HH;#C@'!F<_3[ M><0GD3/#_@Z]YSAC`A+!@(_3$&3H<(21J0%/_/!,%*(*THN9HELIA+T*>7$E MRX,J*,L)F['9",,>HE*T$'3Z+U^55?[U:\60X0>8XTXEP08[)]B M0!L`'1XZ?JA&,_-%KMPC&%,Y@_/`XO7O$>()Y%;A!@G]&%-UI3Z@#+D:Q2:/1H`-"WZ$@IM,EJ/RJ7IO) M?=9IY$\F^)"BW?J;%A6!]3(1\ECF53NPTATS-I5NI=335S,I7B.M4JK\M6A7 MPCJL^O_U'+5=YO]MNYWO_RQ9_V79W=+_MP&9)^N"$>V+E8]VY4JQ\X6.7$E+ M?E[!%[`[SATZW[+=IK0N>R-!Z+A!6W%^JG/1>ZU,:G5IRWW?[99UO]N`U;G_X3S^.IY7+;_A[S^ MUS;MKLK_.F7\WP;\P<]8U&].,!C7%=#<[=6]FAE)&AL\)5OW_,(PCGXDKYG&) M_YMFJU?(_^C^EVV6_K\=R,K^FF;#;`Z<&!ZS$4`/S$[?[O8Q&S>__OI^LVGD M]\,V8';LOGT_PWQT?(`XU@K._;[=Z9M6AE,\W#Y'$)&MOFUFR#\^/QQLQNSU MK5:_;6>8^A!S`U[K?M]JK^!)-&L=K8,4,[2\)F:#C-;7_9:YCGH14;.SBFE= M(*;9[IO===2-F!VKWUDCVMZ$>5_27,.T+\`TB_.8O?O9@-E"4;/!/RK7A$\5 MUNH_K)NH_[!ZG?3\K]?IRO/_;L1"'HMFI:*Z/>TJG+"H'>ANV^,.'+F4*F`9:R/#O'[PRAQF7Q4P6<&(;UFD:";5F/'#P25?\E*"JL.OZ-W M_DXE'B-&_GWF!P'S8+3,JC`>\GAJZ.Y"O6:<1QP#R4RH\*$HT14@6=:11@@D MZ4_H7JU7IRJTB!GRII`N.\LN."&Y$6-ABHO\<`BIM$X@N&X1A@XW.*`B2C:@ M3KU8*J)+UIC0KQ:H:7Q,'0Y2HP_%G3+*:.T+0?+-X0;.0B<)S3J%GR/6"1^DS',^^T%:&PZ49IO%EZC/7 MS0P"_XR1F:88?(P3):5KR*YF6EBC+()F2VE,FUI&J@/5B:[049>IA:'4QNCN MB9-,IC$9+Q%0)8^IHM+O4DLU',%;%'A53%/-%LV>@]1G?H"A9>$L(9\\5!7- M7A_V)5G'*!!5LQ$QE_FO65K%).>Y8(W^;,8\YL2R9.H(%CST]+Q(#5HX4Z$S M042<`6*8#QQUG$BKH"G3`LMW^NZ&@9`!+C@)+_K&+OE?*'6@A&J>,RLU#"T[ MQ@*NTH)TJ3<@&PYQ4\/-AU(O.)FBA*XE8@PEF8.E0L@8@(L_6=.,K@IE7/"S MAZ:+%H+*HU*OE)CB2;Y"%X?CS3,JIZ[H]129Z"Z2E\SF6DG%:)+7O%)HRAQ: M:!O"'J1)NSY.)DX-SFG`7CLJ MGB".H.JT-PRMXL''@E(B][P00P!:50$,XV5J83OZH&$G*_:3I7)BI:!.ANJ( M52CZD0YV%W[H\86A)H,N^Z+.9W3Y59I"=J&9/"!GX`1TZW8IU44KQQ&:%]$U M%CQ"J_'',GVE:Z62I+)1G(&,@A0C+!@RO>.6YF8LR'CI-P"9>Q3`-&3/B>6AS_>?3D MR8:[61Q7\S@"C/CY#:NL<@@IZE\ZB/.'AS(ZJP7YRV\_[^M86X5M^ M14J<.PDLQ)%"#!EA]G6VUC>[7G6.QND4F4\XI>811PE6[HN-`NZ>B2R#IIW" M>G\IL0Y6*O%5US:RBRN8V\O-!?U,#"5::MCK9%`+-+ZKN'0F"0]2L9"P,7GK MS^$;]:-$;UG$X3^P<.'N^4MIJ>I0):2UOW[W+/?_["7;E=O8I?4?G5ZV_O=L M2]9_=K65BK\E'5N)VNBO15;S/TD]HG>5O[ZF'-_SLWX/_8;&;^WS;5 M^__R]Y^W`^_Q_TY?GBA>=.*?GLYF6X(H6%\M^RS=^O(:'LQ#<) MUS81#],W)G0BJ\YKZ0S\M>^H(]?EQI!$IQ27!2,Z*6^#2$8JRJT&*"7C_T4L MRW^BXG;ZJS:KOU$AQ Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17391 for current-outgoing; Sat, 7 Feb 1998 11:21:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17384 for ; Sat, 7 Feb 1998 11:21:27 -0800 (PST) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id LAA18068; Sat, 7 Feb 1998 11:21:24 -0800 (PST) (envelope-from jdp) Message-Id: <199802071921.LAA18068@austin.polstra.com> To: scottm@cs.ucla.edu Subject: Re: cvs bug (and fix) In-Reply-To: <199802062246.OAA03856@mordred.cs.ucla.edu> References: <199802062246.OAA03856@mordred.cs.ucla.edu> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Sat, 07 Feb 1998 11:21:24 -0800 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" In article <199802062246.OAA03856@mordred.cs.ucla.edu>, Scott Michel wrote: > This one's been driving me batshit for the last couple of days. I'm > surprised no one else has encountered it yet. > > Line 6016 in /usr/src/contrib/cvs/src/rcs.c needs to be changed from > > if (n == EOF) > > to > > if (n == EOF || num == NULL) > > Otherwise you get spurious assert's in findnode() a little later on. It looks like only an invalid RCS file could cause that to happen. (Which of course doesn't make it any less of a bug.) Is that right? > Can someone change, approve, and check this in? TIA The fix doesn't look quite right to me. A revision number was expected, but something else (not EOF) was found instead. Shouldn't it report an error? How about something like this: if (n == EOF) { /* If n == EOF and num == NULL, it means we reached EOF naturally. That's fine. */ if (num == NULL) return NULL; else error (1, 0, "%s: unexpected EOF", rcs->path); } else if (num == NULL) error (1, 0, "%s: file contains invalid revision number", rcs->path); -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-current Sat Feb 7 13:48:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08892 for current-outgoing; Sat, 7 Feb 1998 13:48:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA08834 for ; Sat, 7 Feb 1998 13:48:23 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 13590 invoked by uid 1001); 7 Feb 1998 21:48:07 +0000 (GMT) To: toor@dyson.iquest.net Cc: current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' In-Reply-To: Your message of "Wed, 4 Feb 1998 07:37:28 -0500 (EST)" References: <199802041237.HAA01225@dyson.iquest.net> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 07 Feb 1998 22:48:07 +0100 Message-ID: <13588.886888087@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" This may or may not be related to the the recent kernel changes, but I'll report them here anyways: boot.flp from 3.0-980206-SNAP (from releng22.freebsd.org) panics at the end of the boot process, with: changing root device to fd0c rootfs is 1440 KByte compiled in MFS vm_page_free: pindex(12), busy(0), PG_BUSY(0), hold(0) panic: vm_page_free: freeing free page boot.flp from 3.0-980204-SNAP works okay. It's very much reproducible - the panic occurs every time :-). The numbers in the parentheses are the same every time. I've tried it on a PPro-200 with 64 mByte memory, and an AMD 5x86-133 with 24 MByte memory. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current Sat Feb 7 13:53:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10087 for current-outgoing; Sat, 7 Feb 1998 13:53:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10080 for ; Sat, 7 Feb 1998 13:53:15 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id NAA12498 for ; Sat, 7 Feb 1998 13:53:42 -0800 (PST) To: current@FreeBSD.ORG Subject: Latest breakage in -current. Date: Sat, 07 Feb 1998 13:53:40 -0800 Message-ID: <12494.886888420@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" sIV/usr.sbin/kadmind/../../lib/libkadm -I/usr/obj/usr/src/kerberosIV/usr.sbin/k admind/../../lib/libkrb -I/usr/src/kerberosIV/usr.sbin/kadmind/../include -I/us r/src/kerberosIV/usr.sbin/kadmind/../../include -Wall -DHAVE_CONFIG_H -I/usr/ob j/usr/src/kerberosIV/usr.sbin/kadmind/../../include -DBINDIR=\"/usr/bin\" -DSBIN DIR=\"/usr/sbin\" -o kadmind kadm_server.o kadm_funcs.o admin_server.o kadm_s er_wrap.o pw_check.o -L/usr/obj/usr/src/kerberosIV/usr.sbin/kadmind/../../lib/l ibroken -lroken -L/usr/obj/usr/src/kerberosIV/usr.sbin/kadmind/../../lib/libsl - lsl -L/usr/obj/usr/src/kerberosIV/usr.sbin/kadmind/../../lib/libacl -lacl -L/us r/obj/usr/src/kerberosIV/usr.sbin/kadmind/../../lib/libkadm -lkadm -L/usr/obj/u sr/src/kerberosIV/usr.sbin/kadmind/../../lib/libkdb -lkdb -L/usr/obj/usr/src/ker berosIV/usr.sbin/kadmind/../../lib/libkrb -lkrb -ldes -lcom_err kadm_funcs.o: Undefined symbol `_strccm' referenced from text segment kadm_funcs.o: Undefined symbol `_strccm' referenced from text segment kadm_funcs.o: Undefined symbol `_strccm' referenced from text segment kadm_funcs.o: Undefined symbol `_strccm' referenced from text segment *** Error code 1 Hmmm? Jordan From owner-freebsd-current Sat Feb 7 14:04:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11736 for current-outgoing; Sat, 7 Feb 1998 14:04:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11730 for ; Sat, 7 Feb 1998 14:04:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA05821; Sat, 7 Feb 1998 14:02:41 -0800 (PST) Message-Id: <199802072202.OAA05821@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: sthaug@nethelp.no cc: toor@dyson.iquest.net, current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' In-reply-to: Your message of "Sat, 07 Feb 1998 22:48:07 +0100." <13588.886888087@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Feb 1998 14:02:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > This may or may not be related to the the recent kernel changes, but I'll > report them here anyways: > > boot.flp from 3.0-980206-SNAP (from releng22.freebsd.org) panics at the > end of the boot process, with: This SNAP's kernel is busted; don't use it. I expect that it will disappear from the server shortly. I don't know what is actually broken; a fresh -current kernel boots fine. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com From owner-freebsd-current Sat Feb 7 14:27:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15742 for current-outgoing; Sat, 7 Feb 1998 14:27:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from moe.sbbsnet.net ([199.190.101.100]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA15736 for ; Sat, 7 Feb 1998 14:27:32 -0800 (PST) (envelope-from cgorish@sbbsnet.net) Received: from [205.148.219.3] by moe.sbbsnet.net (NTMail 3.03.0014/4c.agn4) with ESMTP id ja051307 for ; Sat, 7 Feb 1998 17:26:52 -0500 Message-Id: <3.0.5.32.19980207172654.009f33e0@mail.sbbsnet.net> X-Sender: cgorish@mail.sbbsnet.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Sat, 07 Feb 1998 17:26:54 -0500 To: freebsd-current@FreeBSD.ORG From: Chuck Gorish Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" subscribe freebsd-current Chuck Gorish SBBSnetworks Florida NOC Manager http://www.sbbsnet.net From owner-freebsd-current Sat Feb 7 16:28:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29409 for current-outgoing; Sat, 7 Feb 1998 16:28:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sphinx.lovett.com (root@sphinx.lovett.com [38.155.241.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA29400 for ; Sat, 7 Feb 1998 16:28:15 -0800 (PST) (envelope-from ade@demon.net) Received: from gorgon.lovett.com [38.155.241.3] (ade) by sphinx.lovett.com with esmtp (Exim 1.82 #1) id 0y1KbU-0000Fe-00; Sat, 7 Feb 1998 18:28:12 -0600 To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Latest breakage in -current. Organization: Demon Internet Reply-To: ade@demon.net In-reply-to: Your message of "Sat, 07 Feb 1998 13:53:40 PST." <12494.886888420@time.cdrom.com> Date: Sat, 07 Feb 1998 18:28:12 -0600 From: Ade Lovett Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" "Jordan K. Hubbard" writes: > > [compiling kadmind] > >kadm_funcs.o: Undefined symbol `_strccm' referenced from text segment >kadm_funcs.o: Undefined symbol `_strccm' referenced from text segment >kadm_funcs.o: Undefined symbol `_strccm' referenced from text segment >kadm_funcs.o: Undefined symbol `_strccm' referenced from text segment >*** Error code 1 > >Hmmm? That's odd. My build machine here was running through a make world as this mail came through.. [last cvsup was around Feb-7 0200 CST] Just watched it go through building the kerberos stuff without a hitch -- I snarf my local copies of the cvs repository from cvsup.freebsd.org if that makes any difference. -aDe -- Ade Lovett, Demon Internet, Austin, Texas. From owner-freebsd-current Sat Feb 7 16:58:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA02819 for current-outgoing; Sat, 7 Feb 1998 16:58:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA02790 for ; Sat, 7 Feb 1998 16:57:56 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id LAA11396; Sun, 8 Feb 1998 11:27:43 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id LAA04072; Sun, 8 Feb 1998 11:27:42 +1030 (CST) (envelope-from grog) Message-ID: <19980208112742.23313@freebie.lemis.com> Date: Sun, 8 Feb 1998 11:27:42 +1030 From: Greg Lehey To: sepotvin@videotron.ca, Current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <34DA0A69.D60EE489@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <34DA0A69.D60EE489@videotron.ca>; from Stephane E. Potvin on Thu, Feb 05, 1998 at 01:52:26PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Thu, 5 February 1998 at 13:52:26 -0500, Stephane E. Potvin wrote: > Maybe it will help shed some light on why both my computers keep > rebooting... > Last time it crashed, instead of simply rebooting it did a trap 12. > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x7993b183 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xf0113fc8 > stack pointer = 0x10:0xf01f89d0 > frame pointer = 0x10:0xf01f89dc > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 218 (ftpd) > interrupt mask = net tty bio cam > trap number = 12 > panic: page fault > > I don't really know what conclusion can be reached from that (if any > can) but some light would surely be appreciated. Do you have a dump or a stack trace? Where is address 0xf0113fc8? Greg From owner-freebsd-current Sat Feb 7 17:17:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04671 for current-outgoing; Sat, 7 Feb 1998 17:17:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp078.100.mmtl.videotron.net [207.253.100.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04666 for ; Sat, 7 Feb 1998 17:17:49 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id UAA21323 for ; Sat, 7 Feb 1998 20:18:33 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DD07E8.B33F2501@videotron.ca> Date: Sat, 07 Feb 1998 20:18:32 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <34DA0A69.D60EE489@videotron.ca> <19980208112742.23313@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" Greg Lehey wrote: > Do you have a dump or a stack trace? Where is address 0xf0113fc8? > > Greg Unfortunately, I noticed after the panic that my dump device was not configured properly. It is now so I'm currently trying to make it panic again instead of just rebooting. Btw, the rest of the system is very stable now. I was able yesterday to keep the system at a load level of 10 using 98% of the swap file for about 30 min without any noticeable problems. Keep the good work! -- Stephane E. Potvin sepotvin@videotron.ca From owner-freebsd-current Sat Feb 7 17:20:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04864 for current-outgoing; Sat, 7 Feb 1998 17:20:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04859 for ; Sat, 7 Feb 1998 17:20:26 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.6.9) with ESMTP id RAA05411; Sat, 7 Feb 1998 17:20:51 -0800 (PST) To: ade@demon.net cc: current@FreeBSD.ORG Subject: Re: Latest breakage in -current. In-reply-to: Your message of "Sat, 07 Feb 1998 18:28:12 CST." Date: Sat, 07 Feb 1998 17:20:50 -0800 Message-ID: <5407.886900850@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > That's odd. My build machine here was running through a make world > as this mail came through.. [last cvsup was around Feb-7 0200 CST] > Just watched it go through building the kerberos stuff without > a hitch -- I snarf my local copies of the cvs repository from > cvsup.freebsd.org if that makes any difference. Perhaps this only shows up with make release? Let's see if it falls over again tonite. Jordan From owner-freebsd-current Sat Feb 7 17:31:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06488 for current-outgoing; Sat, 7 Feb 1998 17:31:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06452 for ; Sat, 7 Feb 1998 17:31:43 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id MAA11431; Sun, 8 Feb 1998 12:01:22 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id MAA04413; Sun, 8 Feb 1998 12:01:22 +1030 (CST) (envelope-from grog) Message-ID: <19980208120121.24477@freebie.lemis.com> Date: Sun, 8 Feb 1998 12:01:21 +1030 From: Greg Lehey To: sepotvin@videotron.ca, Current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <34DA0A69.D60EE489@videotron.ca> <19980208112742.23313@freebie.lemis.com> <34DD07E8.B33F2501@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <34DD07E8.B33F2501@videotron.ca>; from Stephane E. Potvin on Sat, Feb 07, 1998 at 08:18:32PM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Sat, 7 February 1998 at 20:18:32 -0500, Stephane E. Potvin wrote: > Greg Lehey wrote: > >> Do you have a dump or a stack trace? Where is address 0xf0113fc8? >> >> Greg > > Unfortunately, I noticed after the panic that my dump device was not > configured properly. It is now so I'm currently trying to make it panic > again instead of just rebooting. You can at least get an idea of where it dies with this: $ nm kernel | sort | less Then search for the address in the first column. > Btw, the rest of the system is very stable now. I was able yesterday > to keep the system at a load level of 10 using 98% of the swap file > for about 30 min without any noticeable problems. Keep the good > work! Hmm. I'd hope that you could keep the machine running like that for a lot more than 30 minutes! Greg From owner-freebsd-current Sat Feb 7 17:39:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07486 for current-outgoing; Sat, 7 Feb 1998 17:39:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA07481 for ; Sat, 7 Feb 1998 17:39:15 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 4638 invoked from network); 8 Feb 1998 01:39:12 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 8 Feb 1998 01:39:12 -0000 Received: from mordred.cs.ucla.edu (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.8.8/8.8.8) with ESMTP id RAA00299; Sat, 7 Feb 1998 17:39:12 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199802080139.RAA00299@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: John Polstra cc: scottm@CS.UCLA.EDU, current@FreeBSD.ORG Subject: Re: cvs bug (and fix) In-reply-to: Your message of "Sat, 07 Feb 1998 11:21:24 PST." <199802071921.LAA18068@austin.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Feb 1998 17:39:11 -0800 From: Scott Michel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" > In article <199802062246.OAA03856@mordred.cs.ucla.edu>, > Scott Michel wrote: > > This one's been driving me batshit for the last couple of days. I'm > > surprised no one else has encountered it yet. > > > > Line 6016 in /usr/src/contrib/cvs/src/rcs.c needs to be changed from > > > > if (n == EOF) > > > > to > > > > if (n == EOF || num == NULL) > > > > Otherwise you get spurious assert's in findnode() a little later on. > > It looks like only an invalid RCS file could cause that to happen. > (Which of course doesn't make it any less of a bug.) Is that right? For some reason, mine has an extra blank line at the end of the revision file. Other than that, it's perfectly valid. > The fix doesn't look quite right to me. A revision number was > expected, but something else (not EOF) was found instead. Shouldn't > it report an error? > > How about something like this: > > if (n == EOF) > { > /* If n == EOF and num == NULL, it means we reached EOF > naturally. That's fine. */ > if (num == NULL) > return NULL; > else > error (1, 0, "%s: unexpected EOF", rcs->path); > } > else if (num == NULL) > error (1, 0, "%s: file contains invalid revision number", rcs->path); No. I'd make this a warning. Otherwise, some naive Linux-wannabe who encounters this will generate equivalent e-mail. -scooter From owner-freebsd-current Sat Feb 7 17:42:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08078 for current-outgoing; Sat, 7 Feb 1998 17:42:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.119.24.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08073 for ; Sat, 7 Feb 1998 17:42:17 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [194.198.43.36]) by ns1.yes.no (8.8.7/8.8.7) with ESMTP id BAA21986; Sun, 8 Feb 1998 01:40:15 GMT Received: (from eivind@localhost) by bitbox.follo.net (8.8.6/8.8.6) id CAA02145; Sun, 8 Feb 1998 02:40:13 +0100 (MET) Message-ID: <19980208024013.47045@follo.net> Date: Sun, 8 Feb 1998 02:40:13 +0100 From: Eivind Eklund To: Mike Smith Cc: sthaug@nethelp.no, toor@dyson.iquest.net, current@FreeBSD.ORG Subject: Re: Any feedback on my recent kernel 'fixes' References: <13588.886888087@verdi.nethelp.no> <199802072202.OAA05821@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: <199802072202.OAA05821@dingo.cdrom.com>; from Mike Smith on Sat, Feb 07, 1998 at 02:02:40PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe current" On Sat, Feb 07, 1998 at 02:02:40PM -0800, Mike Smith wrote: > > This may or may not be related to the the recent kernel changes, but I'll > > report them here anyways: > > > > boot.flp from 3.0-980206-SNAP (from releng22.freebsd.org) panics at the > > end of the boot process, with: > > This SNAP's kernel is busted; don't use it. I expect that it will > disappear from the server shortly. > > I don't know what is actually broken; a fresh -current kernel boots > fine. I think this was some of my diagnostic changes. They worked fine on SMP-enabled kernels... :-( Eivind, who hopes he won't ever need to make that wide changes to the kernel again. From owner-freebsd-current Sat Feb 7 21:30:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA01818 for current-outgoing; Sat, 7 Feb 1998 21:30:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from azimov.videotron.ca (ppp107.118.mmtl.videotron.net [207.253.118.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA01809 for ; Sat, 7 Feb 1998 21:30:30 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from videotron.ca (localhost.videotron.ca [127.0.0.1]) by azimov.videotron.ca (8.8.8/8.8.8) with ESMTP id AAA00248 for ; Sun, 8 Feb 1998 00:31:29 -0500 (EST) (envelope-from sepotvin@videotron.ca) Message-ID: <34DD432F.A9259025@videotron.ca> Date: Sun, 08 Feb 1998 00:31:28 -0500 From: "Stephane E. Potvin" Reply-To: sepotvin@videotron.ca Organization: IBM Canada Ltd. X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Current@FreeBSD.ORG Subject: Re: Current dying horribly when using lp0 References: <34DA0A69.D60EE489@videotron.ca> <19980208112742.23313@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > Do you have a dump or a stack trace? Where is address 0xf0113fc8? > > Greg Here is the stack trace. If you need anything else let me know. #0 boot (howto=256) at ../../kern/kern_shutdown.c:285 #1 0xf0114316 in panic (fmt=0xf01b6aef "page fault") at ../../kern/kern_shutdown.c:425 #2 0xf01b7731 in trap_fatal (frame=0xf407de98) at ../../i386/i386/trap.c:842 #3 0xf01b71c4 in trap_pfault (frame=0xf407de98, usermode=0) at ../../i386/i386/trap.c:735 #4 0xf01b6e2f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 100, tf_esi = -2147483648, tf_ebp = -200810764, tf_isp = -200810816, tf_ebx = -263249408, tf_edx = 523435, tf_ecx = -200810744, tf_eax = -263316480, tf_trapno = 12, tf_err = 2, tf_eip = -267221090, tf_cs = 8, tf_eflags = 66066, tf_esp = -200810604, tf_ss = 4525259}) at ../../i386/i386/trap.c:363 #5 0xf012879e in sosend (so=0xf06e5c00, addr=0x0, uio=0xf407df44, top=0x0, control=0x0, flags=0, p=0xf4017480) at ../../kern/uipc_socket.c:444 #6 0xf011e6a8 in soo_write (fp=0xf06dbec0, uio=0xf407df44, cred=0xf06e7200) at ../../kern/sys_socket.c:78 #7 0xf011bccd in write (p=0xf4017480, uap=0xf407df94) at ../../kern/sys_generic.c:268 #8 0xf01b7963 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = 537628672, tf_esi = 4525259, tf_ebp = -272641984, tf_isp = -200810524, tf_ebx = 537627176, tf_edx = 0, tf_ecx = 0, tf_eax = 4, tf_trapno = 22, tf_err = 7, tf_eip = 537502977, tf_cs = 31, tf_eflags = 531, tf_esp = -272642052, tf_ss = 39}) at ../../i386/i386/trap.c:994 #9 0x2009a501 in ?? () #10 0x36a7 in ?? () #11 0x86bc in ?? () #12 0x20e9 in ?? () #13 0x1099 in ?? () -- Stephane E. Potvin sepotvin@videotron.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sat Feb 7 23:13:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11769 for current-outgoing; Sat, 7 Feb 1998 23:13:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gte.net (1Cust39.tnt1.lafayette.in.da.uu.net [208.254.19.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11736 for ; Sat, 7 Feb 1998 23:13:01 -0800 (PST) (envelope-from bhlewis@gte.net) Received: from localhost (localhost [127.0.0.1]) by gte.net (8.8.8/8.8.8) with ESMTP id CAA14068 for ; Sun, 8 Feb 1998 02:12:54 -0500 (EST) (envelope-from bhlewis@gte.net) Message-Id: <199802080712.CAA14068@gte.net> X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-current@FreeBSD.ORG Subject: kpilot Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Feb 1998 02:12:53 -0500 From: Benjamin Lewis Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello- Has anyone gotten kpilot1.1b to work under -current? I took a stab at it, but I wasn't able to get it to link cleanly. I figure that the various hacks I had to do to get it that far finally sabotaged me, so now I will have to defer to those more experienced in these things. Part of the README file is reproduced below, to satisfy the curious and to (hopefully) entice someone with more clues than I (most anyone) to do the hard work :) ****** KPilot is software for syncing the 3Com Palm Pilot and IBM Workpad (UNTESTED!) with a machine running some flavor of unix. The actual PC->PP communcations was originally based on pilot-link.0.8.7. By default it attempts to connnect using /dev/pilot which should be a link to the actual serial port, however this is configurable in the settings dialog. This is the second release of KPilot, The have been a few bug fixes (most notably the compile problem a lot of people were experiencing), some cosmetic changes, and signifcant rewrite and expanding of the syncing capabilities. Current features include: o Full Backup/Restore capabilities of Palm Pilot o File (prc,pdb) installation o Email syncing capabilities (via POP3 & sendmail) * o SmartSync backing up modified data even for databases KPilot doesn't recognize * o Import/Export to/from virtually any text format for Addresses. * o Import/Export to/from text files for memos * o Simple to use API to allow developers to add custom widgets to KPilot's display. * o Docs. :) (* = new in v1.1) ****** Thank you for your attention, -Ben -- Benjamin Lewis bhlewis@gte.net -or- bhlewis@purdue.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message From owner-freebsd-current Sat Feb 7 23:47:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15360 for current-outgoing; Sat, 7 Feb 1998 23:47:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15355 for ; Sat, 7 Feb 1998 23:47:41 -0800 (PST) (envelope-from tlambert@usr02.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id AAA24782; Sun, 8 Feb 1998 00:47:36 -0700 (MST) Received: from usr02.primenet.com(206.165.6.202) via SMTP by smtp03.primenet.com, id smtpd024769; Sun Feb 8 00:47:27 1998 Received: (from tlambert@localhost) by usr02.primenet.com (8.8.5/8.8.5) id AAA29050; Sun, 8 Feb 1998 00:47:26 -0700 (MST) From: Terry Lambert Message-Id: <199802080747.AAA29050@usr02.primenet.com> Subject: Re: Current dying horribly when using lp0 To: sepotvin@videotron.ca Date: Sun, 8 Feb 1998 07:47:26 +0000 (GMT) Cc: Current@FreeBSD.ORG In-Reply-To: <34DD432F.A9259025@videotron.ca> from "Stephane E. Potvin" at Feb 8, 98 00:31:28 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > #3 0xf01b71c4 in trap_pfault (frame=0xf407de98, usermode=0) > at ../../i386/i386/trap.c:735 > #4 0xf01b6e2f in trap (frame={tf_es = 16, tf_ds = 16, tf_edi = 100, > tf_esi = -2147483648, tf_ebp = -200810764, tf_isp = -200810816, > tf_ebx = -263249408, tf_edx = 523435, tf_ecx = -200810744, > tf_eax = -263316480, tf_trapno = 12, tf_err = 2, tf_eip = > -267221090, > tf_cs = 8, tf_eflags = 66066, tf_esp = -200810604, tf_ss = > 4525259}) > at ../../i386/i386/trap.c:363 > #5 0xf012879e in sosend (so=0xf06e5c00, addr=0x0, uio=0xf407df44, > top=0x0, > control=0x0, flags=0, p=0xf4017480) at ../../kern/uipc_socket.c:444 > #6 0xf011e6a8 in soo_write (fp=0xf06dbec0, uio=0xf407df44, > cred=0xf06e7200) Do this again with a radix of 16. When you find the damaged pointer in memory, then examine the region of memory before it and after it (again in hex). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe current" in the body of the message