From owner-freebsd-stable Mon Mar 25 13:24:21 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA06100 for stable-outgoing; Mon, 25 Mar 1996 13:24:21 -0800 (PST) Received: from ki.net (root@ki.net [142.77.249.8]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA05972 for ; Mon, 25 Mar 1996 13:23:51 -0800 (PST) Received: (from scrappy@localhost) by ki.net (8.7.4/8.7.4) id QAA00557; Mon, 25 Mar 1996 16:23:46 -0500 (EST) Date: Mon, 25 Mar 1996 16:23:42 -0500 (EST) From: "Marc G. Fournier" To: stable@freebsd.org Subject: Stable not very stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... Just had another system freeze up, after a shocking 5+ days uptime. That, I think, is a record so far for this kernel :( FreeBSD 2.1-STABLE #4: Sat Mar 16 17:16:06 EST 1996 Essentially, the system does a bunch of disk thrashing (I believe its thrashing while it unbatches news, but am not 100% certain that that is what it is doing), then it grinds to a complete halt. I can change VT's, but that is about it. The system consists of: FreeBSD 2.1-STABLE #4: Sat Mar 16 17:16:06 EST 1996 scrappy@ki.net:/usr/src/sys/compile/kinet CPU: i486 DX4 (486-class CPU) Origin = "GenuineIntel" Id = 0x480 Stepping=0 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14704640 (14360K bytes) Probing for devices on PCI bus 0: chip0 rev 49 on pci0:5 ncr0 rev 2 int a irq 12 on pci0:11 ncr0 waiting for scsi devices to settle (ncr0:0:0): "CONNER CFP1060S 1.05GB 243F" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1013MB (2074880 512 byte sectors) (ncr0:1:0): "QUANTUM LPS340S 020B" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 327MB (670506 512 byte sectors) (ncr0:2:0): "QUANTUM LP240S GM240S01X 4.6" type 0 fixed SCSI 2 sd2(ncr0:2:0): Direct-Access sd2(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 234MB (479350 512 byte sectors) (ncr0:3:0): "CONNER CFA540S 13B0" type 0 fixed SCSI 2 sd3(ncr0:3:0): Direct-Access sd3(ncr0:3:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 515MB (1056708 512 byte sectors) vga0 rev 0 on pci0:15 Probing for devices on the ISA bus: ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:86:44:79, type WD8013EPC (16 bit) vt0 at 0x60-0x6f irq 1 on motherboard vt0: generic, 80 col, color, 8 scr, mf2-kbd, [R3.20-b24] sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in aha0 not found at 0x330 npx0 on motherboard npx0: INT 16 interface And within 8min of booting up, is using over 20Meg of SWAP: > uptime; pstat -s 4:16PM up 8 mins, 5 users, load averages: 0.04, 0.15, 0.08 Device 1K-blocks Used Avail Capacity Type /dev/sd0b 102400 5120 97216 5% Interleaved /dev/sd1b 32768 5116 27588 16% Interleaved /dev/sd2b 32768 5120 27584 16% Interleaved /dev/sd3b 32768 5104 27600 16% Interleaved Total 200448 20460 179988 10% The NCR SCSI controller I'm using in this machine is the ASUS SC-200 NCR SCSI controller, and the SCSI drives are all internal currently. I know there have been others that are reporting the same problem, so it isn't limited to my machine alone :( Now, CTL-ALT-ESC does get me down to DDB, and I can do a trace from there, so don't know if that will help any when it does it. If so, please let me know and I'll grab as much info out of that next time as possible. I'm really not using anything that can be construed as "odd", I don't think. Thanks... Marc G. Fournier | POP Mail Telnet Acct DNS Hosting System | WWW Services Database Services | Knowledge, Administrator | | Information and scrappy@ki.net | WWW: http://www.ki.net | Communications, Inc