From owner-freebsd-current@FreeBSD.ORG Fri May 11 07:48:54 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9489A16A402 for ; Fri, 11 May 2007 07:48:54 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.freebsd.org (Postfix) with ESMTP id 744DF13C447 for ; Fri, 11 May 2007 07:48:54 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout3.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l4B7mrWE031245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 11 May 2007 00:48:54 -0700 X-Auth-Received: from [192.168.10.45] (c-67-187-164-17.hsd1.ca.comcast.net [67.187.164.17]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l4B7mrrN026519 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 11 May 2007 00:48:53 -0700 Message-ID: <46441FE2.80604@u.washington.edu> Date: Fri, 11 May 2007 00:48:50 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <463EED96.50303@u.washington.edu> <29403.217.221.237.206.1178532673.squirrel@krisma.oltrelinux.com> <463F302B.7030704@u.washington.edu> <4643E000.7010203@u.washington.edu> In-Reply-To: <4643E000.7010203@u.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.5.11.3135 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: Re: Kernel panics on boot: can't allocate interrupts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2007 07:48:54 -0000 Garrett Cooper wrote: > Garrett Cooper wrote: >> Paolo Pisati wrote: >>>> I just rebuilt the kernel today, and it appears that the kernel can't >>>> allocate interrupts anymore (for whatever reason). I've posted my >>>> kernel >>>> config here: >>>> , and my >>>> screenshots of the boot process here: >>>> . >>>> >>>> I'm using the amd64 version of 7-CURRENT via VMWare in XP-x64. >>> >>> can you go back to Sat 05 May with the src and try again? >>> >> >> Sure. I just synced only the kernel section (src-sys) and rebuilt >> / installed the kernel and I still receive the same failure. Should I >> do the same for the userland as well? >> The only other thing is that I was testing out some code mods last >> night in the libc directory with db, and some of the code was >> partially built. At what point does the interrupt allocation occur? >> Userland or kernel? Can you point me to the source directory? >> Thanks! >> -Garrett > > Well, so far I can say that a checkin between April 14th and April 28th > most likely caused the panic issues. Need to do some more investigating. > -Garrett I synced and rebuilt world and everything appears to be perfectly fine. The issue may have layed in the fact that I was using partially built objects (NO_CLEAN=yes), or the fact that some build dependencies weren't compiled properly (by myself). Back to work on a 'stable' version of CURRENT again.. Yay! -Garrett