From owner-freebsd-hackers Sat Dec 2 20:24:00 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA17321 for hackers-outgoing; Sat, 2 Dec 1995 20:24:00 -0800 Received: from bubba.tribe.com ([205.184.207.7]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id UAA17314 for ; Sat, 2 Dec 1995 20:23:54 -0800 Received: (from archie@localhost) by bubba.tribe.com (8.6.12/8.6.12) id UAA04607 for freebsd-hackers@freebsd.org; Sat, 2 Dec 1995 20:23:13 -0800 From: Archie Cobbs Message-Id: <199512030423.UAA04607@bubba.tribe.com> Subject: Strange crash To: freebsd-hackers@freebsd.org Date: Sat, 2 Dec 1995 20:23:12 -0800 (PST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2687 Sender: owner-hackers@freebsd.org Precedence: bulk Hi, I've been testing a 486DX2-66 Texas Intstruments chip, and it has been working fine except for a strange crash on bootup that happened once: FreeBSD 2.1.0-951104-SNAP #0: Thu Nov 30 15:11:59 PST 1995 root@bubba:/a/bubba/home/archie/ia/src/sys/compile/TIA CPU: Cy486DLC (486-class CPU) Origin = "Cyrix" real memory = 4194304 (4096K bytes) avail memory = 2707456 (2644K bytes) Probing for devices on the ISA bus: ed1 at 0x300-0x31f irq 5 on isa ed1: address 00:00:e8:cd:1e:08, type NE2000 (16 bit) eth0 not found at 0x240 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 fdc0: direction bit not set fdc0: cmd 3 failed at out byte 1 of 3 fdc0 not found at 0x3f0 wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 257MB (528192 sectors), 917 cyls, 12 heads, 48 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface swapon: adding /dev/wd0b as swap device Automatic reboot in progress... /dev/rwd0a: clean, 3176 free (0 frags, 794 blocks, 0.0% fragmentation) /dev/rwd0e: clean, 14924 free (12 frags, 3728 blocks, 0.1% fragmentation) /dev/rwd0f: clean, 53066 free (106 frags, 13240 blocks, 0.2% fragmentation) /dev/rwd0g: clean, 26060 free (4 frags, 6514 blocks, 0.0% fragmentation) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1249b4 fault code = supervisor read, page not present instruction pointer = 0x8:0x1249b4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 13 (mount) interrupt mask = panic: page fault syncing disks... done Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Keyboard reset did not work, attempting CPU shutdown (The "eth0 not found" line is from the the ET frame relay card driver.) I did a "nm kernel | sort" on the kernel image and found this: f01248e8 T _chdir f012493c T _chroot f01249b4 t _change_dir <-- f0124a4c T _open f0124ce8 T _ocreat f0124d14 T _mknod On the next reboot, it booted up fine as it has before many times. Can we assume with high probability that this is some kind of hardware bug? Is this chip bogus? Any insights would be greatly appreciated!! Thanks, -Archie _______________________________________________________________________________ Archie L. Cobbs, archie@tribe.com * Tribe Computer Works http://www.tribe.com