Date: Fri, 24 Sep 2004 22:41:44 -0700 From: Nate Lawson <nate@root.org> To: David Syphers <dsyphers@u.washington.edu> Cc: freebsd-current@freebsd.org Subject: Re: 5.3-BETA5-i386-disc1 bootstrap failures Message-ID: <41550518.6000105@root.org> In-Reply-To: <200409240132.33577.dsyphers@u.washington.edu> References: <200409211736.i8LHajfK000463@mist.nodomain> <200409211206.03632.dsyphers@u.washington.edu> <200409240059.47087.dsyphers@u.washington.edu> <200409240132.33577.dsyphers@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
David Syphers wrote: > On Friday 24 September 2004 12:59 am, David Syphers wrote: > >>The list has been quiet about this, so I assume it's a rare problem. But >>I've got a couple questions about it. First, does anyone have any idea >>what's actually wrong? My computer is running -CURRENT from August 3 fine. >>(I don't have APIC in that kernel.) Anything having to do with ACPI is >>default. My computer is some generic HP, not quite three years old. More >>info available if it would help. > > > I just did one simple test I should have done first - it's APIC that's the > problem. Booting with ACPI disabled panics (even earlier than with nothing > disabled), but booting with hint.apic.0.disabled="1" gets me to the > installation screen. I thought this would be the case, as I currently run > ACPI with no problems. > > I actually have no idea what APIC is. I assume it's okay if I install with > that hint set, and then just compile a custom kernel with no APIC? But since > it's in GENERIC, I really don't think it should be panicking... It's always safe to use the system with APIC disabled. It only means that you may get less performance in UP systems or no MP support for MP systems. APIC is an advanced interrupt router. -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41550518.6000105>