From owner-freebsd-hardware Fri Dec 26 12:45:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA03099 for hardware-outgoing; Fri, 26 Dec 1997 12:45:52 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from proxy3.ba.best.com (root@proxy3.ba.best.com [206.184.139.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA03091 for ; Fri, 26 Dec 1997 12:45:46 -0800 (PST) (envelope-from bsampley@best.com) Received: from shell9.ba.best.com (bsampley@shell9.ba.best.com [206.184.139.140]) by proxy3.ba.best.com (8.8.8/8.8.BEST) with SMTP id LAA13634 for ; Fri, 26 Dec 1997 11:41:07 -0800 (PST) Date: Fri, 26 Dec 1997 11:41:07 -0800 (PST) From: Burton Sampley X-Sender: bsampley@shell9.ba.best.com To: hardware@freebsd.org Subject: Re: NCR810 (or 875) & Asus P55T2P4 & Overclocking ? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I've purchased the NCR810 controller, but I've noticed some strange things while running my system at the 83MHz (3.0X, 83Mhz = 250) bus speed. Make -k world from clean 2.2.5 source on hardware that's known to build (with the exception of this controller) keeps rebooting in the early stages of make world. As best as I can tell it is rebooting during libg++ (started with "time make -k world >& /home/bsampley/mk_world.250.83"). At first I thought the problem was the second hard drive (ST43400). When I first installed the new controller, I noticed the "little green light" on the front of the drive was flashing rapidly after the controller found the drive. I tried adjusting the jumpers, but I couldn't find a setting that made the drive happy. I later changed my mind when I received similar signal 11 errors while attempting to build cvsup from the ports collection (which is mounted on the other drive). All of the ports I have tried have been able build without errors (like afterstep, xlockmore, staroffice, filerunner, tcl-8.0, ssh and xv) except cvsup. Any ideas, or is my hardware telling me it's not going to fly at 83MHz? BTW, Windoze95 (which is only kept for games runs fine at 83MHz on sd0. Tom's hardware page says if Win95 will run overclocked without blowing up, then your chances are good at overclocking the board/cpu). Here's /etc/fstab: root(110)# cat /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/sd0s2b none swap sw 0 0 /dev/sd0a / ufs rw 1 1 /dev/sd0s2g /usr ufs rw 2 2 /dev/sd0s2f /usr/obj ufs rw,noatime,async 22 /dev/sd1s1e /usr/src ufs rw,noatime,async 22 /dev/sd0s2e /var ufs rw 2 2 proc /proc procfs rw 0 0 /dev/wcd0c /cdrom cd9660 ro,noauto 0 0 root(111)# Here's the tail of mk_world.250.83: root(106)# tail /home/bsampley/mk_world.250.83 cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitany.c -o bitany.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitblt.c -o bitblt.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitclear.c -o bitclear.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitcopy.c -o bitcopy.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitcount.c -o bitcount.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitinvert.c -o bitinvert.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitlcomp.c -o bitlcomp.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitset1.c -o bitset1.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/bitxor.c -o bitxor.so cc -fpic -DPIC -O2 -pipe -I/usr/src/gnu/lib/libg++/../../../contrib/libg++/include -I/usr/obj/usr/src/tmp/usr/include/g++ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/lib/libg++/../../../contrib/libg++/libg++/src/timer.c -o timer.so root(107)# In reviewing /var/log/messages I noticed the following: Dec 24 21:17:30 myname /kernel: pid 17796 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:18:07 myname /kernel: pid 17873 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:18:13 myname /kernel: pid 17884 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:18:31 myname /kernel: pid 17919 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:18:56 myname /kernel: pid 17948 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:19:31 myname /kernel: pid 18037 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:19:43 myname /kernel: pid 18051 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:21:07 myname /kernel: pid 18202 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:21:18 myname /kernel: pid 18207 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:21:35 myname /kernel: pid 18252 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:21:47 myname /kernel: pid 18277 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:21:51 myname /kernel: pid 18292 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:21:52 myname /kernel: pid 18297 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:22:30 myname /kernel: pid 19688 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:22:31 myname /kernel: pid 19689 (as), uid 0: exited on signal 11 (core dumped) Dec 24 21:22:31 myname /kernel: pid 19696 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:22:31 myname /kernel: pid 19704 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:22:49 myname /kernel: pid 20132 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:23:00 myname /kernel: pid 20280 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:23:05 myname /kernel: pid 20369 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:23:06 myname /kernel: pid 20378 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:23:17 myname /kernel: pid 20517 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:23:19 myname /kernel: pid 20541 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:23:20 myname /kernel: pid 20565 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:24:18 myname /kernel: pid 21526 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:24:20 myname /kernel: pid 21540 (cc1), uid 0: exited on signal 11 (core dumped) Dec 24 21:24:24 myname /kernel: pid 21569 (cc1), uid 0: exited on signal 11 (core dumped) Here's dmesg: FreeBSD 2.2.5-RELEASE #0: Tue Oct 21 14:33:00 GMT 1997 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC CPU: Pentium (250.57-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping=3 Features=0x8001bf real memory = 134217728 (131072K bytes) avail memory = 127172608 (124192K bytes) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 2 int a irq 12 on pci0:9 ncr0 rev 18 int a irq 10 on pci0:11 ncr0 waiting for scsi devices to settle (ncr0:0:0): "COMPAQ ST15150N 5216" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) 4094MB (8386000 512 byte sectors) (ncr0:2:0): "SEAGATE ST43400N 1028" type 0 fixed SCSI 2 sd1(ncr0:2:0): Direct-Access sd1(ncr0:2:0): 10.0 MB/s (100 ns, offset 8) 2777MB (5688447 512 byte sectors) de0 rev 34 int a irq 11 on pci0:12 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:40:a2:37 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 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: medium type unknown, unlocked nca0 at 0x1f88-0x1f8b irq 10 on isa nca0: type ProAudioSpectrum-16 nca0 waiting for scsi devices to settle npx0 flags 0x1 on motherboard npx0: INT 16 interface changing root device to sd0a