From owner-freebsd-current@FreeBSD.ORG Sun Jun 10 23:24:59 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 31C0016A41F for ; Sun, 10 Jun 2007 23:24:59 +0000 (UTC) (envelope-from clee@mg8.org) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id 1560A13C44B for ; Sun, 10 Jun 2007 23:24:58 +0000 (UTC) (envelope-from clee@mg8.org) Received: by wa-out-1112.google.com with SMTP id j37so2076915waf for ; Sun, 10 Jun 2007 16:24:58 -0700 (PDT) Received: by 10.114.14.1 with SMTP id 1mr4890765wan.1181517898426; Sun, 10 Jun 2007 16:24:58 -0700 (PDT) Received: by 10.114.66.10 with HTTP; Sun, 10 Jun 2007 16:24:58 -0700 (PDT) Message-ID: Date: Sun, 10 Jun 2007 16:24:58 -0700 From: "Chris Lee" Sender: clee@mg8.org To: "Greg Rivers" , freebsd-current@freebsd.org In-Reply-To: <20070610122840.T71148@nc8000.tharned.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070610122840.T71148@nc8000.tharned.org> X-Google-Sender-Auth: 3b6fdab4e4cc08b3 Cc: Subject: Re: AMD64 panic on boot 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: Sun, 10 Jun 2007 23:24:59 -0000 On 6/10/07, Greg Rivers wrote: > On Sun, 10 Jun 2007, Chris Lee wrote: > > > I built a custom kernel and it says that it can't map interrupts for > > certain devices (like my ATA controller), which prevents it from being > > able to find my disks and mount my root fs. > > > > I *think* my kernel configuration is fairly standard. It's available > > at http://c133.org/freebsd-7.conf if anybody would mind taking a look > > and offering some pointers. I cvsup'd yesterday around midnight, and > > my hardware is a pretty standard nforce4 mobo with a dual-core Opteron > > for the main CPU. > > > > Your config lacks a "machine" directive. I think you want "machine amd64" > above "cpu HAMMER". It turns out I'm just an idiot. With 6.2-RELEASE, I had to boot without ACPI in order to avoid kernel panics under load; I have a USB keyboard and apparently USB events can cause kernel panics while the kernel is heavily loaded down (like, say, during a 'make buildworld' or a 'make buildkernel'). So I instinctively booted the new 7.0-CURRENT kernel with ACPI disabled as well, and it couldn't map any of my device interrupts. When I rebooted with ACPI enabled, it actually booted and let me log in. Now the only issue that I have is that sending SIGINFO to a 'dd' process causes a kernel panic. Any ideas about that one?