From owner-freebsd-current Sat Nov 22 22:07:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA21492 for current-outgoing; Sat, 22 Nov 1997 22:07:43 -0800 (PST) (envelope-from owner-freebsd-current) Received: from shell.dragondata.com (toasty@shell.dragondata.com [204.137.237.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA21487 for ; Sat, 22 Nov 1997 22:07:41 -0800 (PST) (envelope-from toasty@shell.dragondata.com) Received: (from toasty@localhost) by shell.dragondata.com (8.8.7/8.8.7) id AAA01152; Sun, 23 Nov 1997 00:07:46 -0600 (CST) (envelope-from toasty) From: User Toasty Message-Id: <199711230607.AAA01152@shell.dragondata.com> Subject: Re: Repeated system crashes with 110897 snap. In-Reply-To: <19971122220349.53823@micron.mini.net> from Jonathan Mini at "Nov 22, 97 10:03:49 pm" To: j_mini@efn.org Date: Sun, 23 Nov 1997 00:07:46 -0600 (CST) 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 X-Loop: FreeBSD.org Precedence: bulk > Other issues aside, the best way to give a hardware profile is to include > a copy of the COMPLETE dmesg output. This gives the kernel's messages > (including boot and errors) which are more much more informative that the info > you gave. :) > (Note I said _complete_. An edited dmesg is often next to useless, since the > user mistakenly identifies vital information as irrelivent and edits it out) Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-971108-SNAP #0: Tue Nov 11 17:12:16 CST 1997 root@shell.dragondata.com:/usr/src/sys/compile/SHELL CPU: Pentium (586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x3bf real memory = 92274688 (90112K bytes) avail memory = 86564864 (84536K 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 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found mse0 not found at 0x23c fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: utp[*UTP*] address 00:60:97:6b:88:f4 npx0 on motherboard npx0: INT 16 interface APIC_IO: routing 8254 via 8259 on pin 0 SMP: AP CPU #1 Launched! WARNING: / was not properly dismounted. nfs send error 55 for server home:/home The only thing that looks sorta weird is the nfs error, which I get a lot. :) Anything else I can do to help, I'd be glad to do. Kevin