Date: Thu, 14 Apr 2005 23:09:43 -0400 From: Adam Gregoire <ebola@psychoholics.org> To: cvs-src@FreeBSD.org Subject: Re: cvs commit: src/sys/amd64/conf GENERIC Message-ID: <1113534583.768.7.camel@S010600deadc0de00.su.shawcable.net> In-Reply-To: <425EE2BE.8060503@root.org> References: <200504091700.j39H0H5X060998@repoman.freebsd.org> <200504141402.36352.jhb@FreeBSD.org> <86d5sxxfm4.fsf@xps.des.no> <200504141416.50884.peter@wemm.org> <425EE2BE.8060503@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2005-04-14 at 14:38 -0700, Nate Lawson wrote: > Peter Wemm wrote: > > On Thursday 14 April 2005 01:33 pm, Dag-Erling Smørgrav wrote: > > > >>John Baldwin <jhb@FreeBSD.org> writes: > >> > >>>On Thursday 14 April 2005 01:37 pm, Dag-Erling Smørgrav wrote: > >>> > >>>>Peter Wemm <peter@wemm.org> writes: > >>>> > >>>>>[local apic timer] makes mixed mode and the entire problem set > >>>>>disappear. > >>>> > >>>>No, it doesn't. > >>> > >>>Actually, it does (with lapic timer we no longer use IRQ0). > >> > >>Empirical evidence says it doesn't... > >> > >>DES > > > > It had better not, because the code is going away..... > > > > -Peter > > While we all appreciate a droll, rambling conversation with no > specifics, how about you help us out by backing up your statement, DES? > At any rate, my problematic nForce based board now boots with APIC enabled in BIOS and without device atpic in the kernel. I'm happy. Regards, -- Adam Gregoire <ebola@psychoholics.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1113534583.768.7.camel>