From owner-freebsd-stable Wed Sep 6 7:27:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from groenquist.com (cx636606-b.santab1.ca.home.com [24.15.127.91]) by hub.freebsd.org (Postfix) with ESMTP id 0317837B422 for ; Wed, 6 Sep 2000 07:27:39 -0700 (PDT) Received: from localhost (root@localhost) by groenquist.com (8.11.0/8.9.3) with ESMTP id e86ERca02661; Wed, 6 Sep 2000 07:27:38 -0700 (PDT) (envelope-from root@groenquist.com) Date: Wed, 6 Sep 2000 07:27:37 -0700 (PDT) From: Matt Groener To: freebsd-stable@FreeBSD.org Cc: freebsd-stable@FreeBSD.org Subject: "profiling timer expired" on new kernel builds in 4.1-R and 4.1-S In-Reply-To: <20000906100747.A2116@rjk191.rh.psu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have recently begun to receive "profiling timer expired" errors at boot time (specifically at /etc/rc initialization) on any new kernel I build. This includes stock GENERIC kernel builds. I have synced up the OS with very recent (within 24 hours) builworld's and installworld's apparently without problems. However, the only way to boot is with /kernel.GENERIC, since all of my kernel compiles report the above profiling errors. I searched the archives for errors of this type but did not find anything relevant. To the best of my knowledge, this behavior began in mid-August, and I have wrestled with it ever since (close to 10 reinstalls to try different ideas). My questions: Could this be hardware related? No changes recently but still who knows?... If I build a new GENERIC kernel after a fresh install of 4.1-R, the kernel works. Only after syncing up /usr/src with cvsup to -stable do I incur the wrath of profiling errors. Should I not sync up anymore? Thanks in advance, -matt ------------ Matt Groener qad, inc. matt@groenquist.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message