From owner-freebsd-questions Wed Jul 17 15:58:29 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA28992 for questions-outgoing; Wed, 17 Jul 1996 15:58:29 -0700 (PDT) Received: from croute.com (ishm2.croute.com [199.97.106.1]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA28985 for ; Wed, 17 Jul 1996 15:58:26 -0700 (PDT) Received: from bldg1.croute.com by croute.com (4.1/SMI-4.1) id AA00583; Wed, 17 Jul 96 17:58:24 CDT Received: from COMPUROUTE/SpoolDir by bldg1.croute.com (Mercury 1.13); Wed, 17 Jul 96 17:58:08 +600 Received: from SpoolDir by COMPUROUTE (Mercury 1.13); Wed, 17 Jul 96 17:57:58 +600 From: "Larry Dolinar" Organization: CompuRoute, Inc. To: questions@freebsd.org Date: Wed, 17 Jul 1996 17:57:51 +600 CDT Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Subject: lpd, 3 parallel ports, and occasional lpd.core X-Confirm-Reading-To: "Larry Dolinar" X-Pmrqc: 1 Priority: normal X-Mailer: Pegasus Mail v3.22 Message-Id: <83233FF2470@bldg1.croute.com> Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk greetings, folks... Hardware: clone 486DX-33 motherboard, Intel CPU 8MB RAM (4 9-chip, 4 3-chip, 30pin SIMMs) 3 IDE controller cards: floppy, IDE, and parallel/serial ports enabled on 1st parallel only on 2nd and 3rd (as lpt1 and lpt2) NE2000 clone NIC (GVC NX-16T) Maxtor 270MB IDE drive 3.5" floppy 16bit Cirrus VGA software: 2.1.0-RELEASE, GENERIC kernel filesystems: /dev/wd0a on / (local) /dev/wd0s1e on /usr (local) procfs on /proc (local) Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0a 24062 13524 8612 61% / /dev/wd0s1e 210954 56136 137940 29% /usr procfs 4 4 0 100% /proc OK, you can stop laughing now, but all I really want it to be is a nice little BSD printserver for our inkjets. The basic problem is that the box is slow to acknowledge print requests (even compared to an old HP 725), but reasonably quick to shove the data at the printers. Once in a while the OS will dump core (lpd.core) in the spool directory for the first printer (/usr/spool/lp0) and generally stop servicing print requests (and telnet) until the resulting child processes are killed (sorry, no current ps list available for the error condition). I'd like to keep using this box in this fashion, but don't know if I need to add more memory, cut down the kernel (suspect it's likely) or something else. The dmesg output is below: Jul 16 14:26:12 chub /kernel: FreeBSD 2.1.0-RELEASE #0: Thu Nov 16 10:47:14 1995 Jul 16 14:26:12 chub /kernel: jkh@westhill.cdrom.com:/usr/src/sys/compile/GENERIC Jul 16 14:26:12 chub /kernel: CPU: i486DX (486-class CPU) Jul 16 14:26:12 chub /kernel: real memory = 8388608 (8192K bytes) Jul 16 14:26:12 chub /kernel: avail memory = 6557696 (6404K bytes) Jul 16 14:26:13 chub /kernel: Probing for devices on the ISA bus: Jul 16 14:26:13 chub /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jul 16 14:26:13 chub /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jul 16 14:26:13 chub /kernel: ed0 at 0x300-0x31f irq 12 on isa Jul 16 14:26:13 chub /kernel: ed0: address 00:00:e8:c7:f7:83, type NE2000 (16 bit) Jul 16 14:26:13 chub /kernel: ed1: disabled, not probed. Jul 16 14:26:13 chub /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Jul 16 14:26:13 chub /kernel: sio0: type 16450 Jul 16 14:26:13 chub /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Jul 16 14:26:13 chub /kernel: sio1: type 16450 Jul 16 14:26:13 chub /kernel: sio2: disabled, not probed. Jul 16 14:26:14 chub /kernel: sio3: disabled, not probed. Jul 16 14:26:14 chub /kernel: lpt0 at 0x3bc-0x3c3 irq 7 on isa Jul 16 14:26:14 chub /kernel: lpt0: Interrupt-driven port Jul 16 14:26:14 chub /kernel: lp0: TCP/IP capable interface Jul 16 14:26:14 chub /kernel: lpt1 at 0x378-0x37f on isa Jul 16 14:26:14 chub /kernel: lpt2 at 0x278-0x27f on isa Jul 16 14:26:14 chub /kernel: mse0: disabled, not probed. Jul 16 14:26:14 chub /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jul 16 14:26:14 chub /kernel: fdc0: NEC 765 Jul 16 14:26:14 chub /kernel: fd0: 1.44MB 3.5in Jul 16 14:26:14 chub /kernel: wdc0 at 0x1f0-0x1f7 irq 14 on isa Jul 16 14:26:14 chub /kernel: wdc0: unit 0 (wd0): Jul 16 14:26:15 chub /kernel: wd0: 257MB (527450 sectors), 959 cyls, 11 heads, 50 S/T, 512 B/S Jul 16 14:26:15 chub /kernel: wdc1: disabled, not probed. Jul 16 14:26:15 chub /kernel: bt0: disabled, not probed. Jul 16 14:26:15 chub /kernel: uha0: disabled, not probed. Jul 16 14:26:15 chub /kernel: ahc1: disabled, not probed. Jul 16 14:26:16 chub /kernel: ahb0: disabled, not probed. Jul 16 14:26:16 chub /kernel: aha0: disabled, not probed. Jul 16 14:26:16 chub /kernel: aic0: disabled, not probed. Jul 16 14:26:16 chub /kernel: nca0: disabled, not probed. Jul 16 14:26:16 chub /kernel: nca1: disabled, not probed. Jul 16 14:26:16 chub /kernel: sea0: disabled, not probed. Jul 16 14:26:16 chub /kernel: wt0: disabled, not probed. Jul 16 14:26:16 chub /kernel: mcd0: disabled, not probed. Jul 16 14:26:16 chub /kernel: mcd1: disabled, not probed. Jul 16 14:26:16 chub /kernel: matcdc0: disabled, not probed. Jul 16 14:26:16 chub /kernel: scd0: disabled, not probed. Jul 16 14:26:16 chub /kernel: ie0: disabled, not probed. Jul 16 14:26:16 chub /kernel: ep0: disabled, not probed. Jul 16 14:26:16 chub /kernel: ix0: disabled, not probed. Jul 16 14:26:17 chub /kernel: le0: disabled, not probed. Jul 16 14:26:17 chub /kernel: lnc0: disabled, not probed. Jul 16 14:26:17 chub /kernel: lnc1: disabled, not probed. Jul 16 14:26:17 chub /kernel: ze0: disabled, not probed. Jul 16 14:26:17 chub /kernel: zp0: disabled, not probed. Jul 16 14:26:17 chub /kernel: npx0 on motherboard Jul 16 14:26:17 chub /kernel: npx0: INT 16 interface Jul 16 14:26:22 chub lpd[94]: restarted Jul 16 14:26:29 chub /kernel: lpt0 switched to polled mode : : Jul 16 15:29:57 chub /kernel: pid 265: lpd: uid 0: exited on signal 11 : Jul 17 10:28:25 chub /kernel: pid 1211: lpd: uid 0: exited on signal 11 : Jul 17 10:42:21 chub /kernel: pid 1232: lpd: uid 0: exited on signal 11 I'd like to know what the signal 11 indicates (memory problems?). Discerning individuals will notice the I/O ports for lpt0-2 are skewed: made necessary by some hardware issue I don't yet understand. And is it a mistake to turn on polling for lpt0 in these circumstances? All comments welcomed. cheers, larry