From owner-freebsd-stable Sun Jul 13 18:27:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA19096 for stable-outgoing; Sun, 13 Jul 1997 18:27:39 -0700 (PDT) Received: from nexgen.hiwaay.net (max7-250.HiWAAY.net [208.147.145.250]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA19091 for ; Sun, 13 Jul 1997 18:27:33 -0700 (PDT) Received: from nexgen (localhost [127.0.0.1]) by nexgen.hiwaay.net (8.8.6/8.8.4) with ESMTP id UAA00397 for ; Sun, 13 Jul 1997 20:27:19 -0500 (CDT) Message-Id: <199707140127.UAA00397@nexgen.hiwaay.net> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-stable@freebsd.org Subject: Problems with new kernel From: dkelly@HiWAAY.net Mime-Version: 1.0 Content-Type: text/plain Date: Sun, 13 Jul 1997 20:27:17 -0500 Sender: owner-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk nexgen: {9} uname -a FreeBSD nexgen.hiwaay.net 2.2-STABLE FreeBSD 2.2-STABLE #0: Fri May 30 22:41:29 CDT 1997 dkelly@nexgen.hiwaay.net:/usr/src/sys/compile/NEXGEN i386 Am guessing 2.2 is now stable and this is the right place to ask? I don't feel I know my problem well enough to properly ask with send-pr. Sometime last month I decided it was time for "make world" using cvsup'ed sources from RELENG_2_2, was already running a 2.2.2-RELEASE that had the same thing done to it earlier. After getting past the "make include" hurdle which stymied others I got "world" to complete. But now I'm not able to create a new kernel that works on my system. The kernel I'm using was built May 30 from a source of about that time. New kernels (using the exact same config file I used before) reset just after the initial memory load line and before the "BIOS Basemem..." line (the first one in bold VGA text). I'd include my config file, but GENERIC does exactly the same. System is a NexGen P90-PCI. Said to be Pentium 90 in performance but lacks FPU. CPU ID's as a 386 so I've been compiling without I486_CPU and I586_CPU except for the GENERIC test, which was un-edited. Last cvsup was about noon on Sunday. One other thing to add, my system is no longer rock-solid, the way it was for the past year or so. Am hoping its due to the more recent "world" and the older kernel. The way to bring it down is to netsurf with Netscape 3.01 and open a window for most every link followed. Suddendly the mouse freezes. And several moments the system reboots. Have 32M core, 64M swap. When this happened this afternoon I had top running in an xterm and kept the %-in-use field visible thinking I was experiencing poor handling of out of swap, but it locked up at 67% in-use (of 64M) so thats probably not it. Its more like the kernel clock stopped and a watchdog reset the system. No error messages. Am wondering if my new kernel problem could be related to discussions about using the FPU (which I don't have) for memory copy tasks? -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.