From owner-freebsd-current Sun Jun 18 22:45:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat204.200.mpoweredpc.net [142.177.204.200]) by hub.freebsd.org (Postfix) with ESMTP id EF88437B6D1 for ; Sun, 18 Jun 2000 22:45:08 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id CAA01553; Mon, 19 Jun 2000 02:43:49 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 19 Jun 2000 02:43:49 -0300 (ADT) From: The Hermit Hacker To: Bosko Milekic Cc: freebsd-current@FreeBSD.ORG Subject: Re: FOLLOWING config changes? : Kernel profiling support In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG that did her, thanks ... should this maybe be mentioned in /usr/src/UPDATING? I've gotten into the habit of pretty much checking there first, and saw no mention of this (could be blind too, its happened before) ... On Mon, 19 Jun 2000, Bosko Milekic wrote: > > Yes, this is what I initially got. Although I'm not quite interested in > this particular problem. What I need is profiling to work. > > Still, what you should look at is adding the `hints' directive to your > kernel configuration file, if you haven't done so already. See if that > fixes your problem. > > On Mon, 19 Jun 2000, The Hermit Hacker wrote: > > > > > Ya know, I never thought about checkign /var/log/messages on mine to see > > if it was, in fact, booting (I thought it was, it sounded like it was, but > > I couldn't think of a way to check) ... > > > > Using kernel sources up-to-date as of a few hours ago, I've tried to pare > > my optimzatins down to a simple '-O -pipe', and I'm getting the same thing > > as you, where I effectively get: > > > > Booting kernel ... > > \ > > > > on my screen, and that's the end of it. Looking at /var/log/messages, it > > looks like I am getting a full reboot happening, right down to > > initializing 'vmmon', but nothing to my screen. > > > > I've been trying to follow the -current list to see if any ideas/solutions > > pop up, but the only things I've noticed so far have revolved around > > optimization issues, but its more then possible that I missed a message > > ... > > > > My last good kernel, that boot'd fine, is: > > > > @(#)FreeBSD 5.0-CURRENT #0: Wed Jun 14 01:03:00 ADT 2000 > > > > With every other one since resulting in the above ... > > > > > -- > Bosko Milekic * Voice/Mobile: 514.865.7738 * Pager: 514.921.0237 > bmilekic@technokratis.com * http://www.technokratis.com/ > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message