Date: Sun, 10 Jun 2007 16:24:58 -0700 From: "Chris Lee" <clee@kde.org> To: "Greg Rivers" <gcr+freebsd-current@tharned.org>, freebsd-current@freebsd.org Subject: Re: AMD64 panic on boot Message-ID: <db69205d0706101624w64e1f3d1kcd8f488f5f704237@mail.gmail.com> In-Reply-To: <20070610122840.T71148@nc8000.tharned.org> References: <db69205d0706100924h595a9d1dwac3cf42c3935546b@mail.gmail.com> <20070610122840.T71148@nc8000.tharned.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/10/07, Greg Rivers <gcr+freebsd-current@tharned.org> 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?db69205d0706101624w64e1f3d1kcd8f488f5f704237>