Date: Mon, 12 Apr 1999 20:38:35 -0500 From: "William S. Duncanson" <caesar@starkreality.com> To: Chuck Robey <chuckr@mat.net> Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP broken in -CURRENT? Message-ID: <4.1.19990412202347.009bf790@imap.colltech.com> In-Reply-To: <Pine.BSF.4.10.9904122055220.372-100000@picnic.mat.net> References: <4.1.19990412191627.009b3100@imap.colltech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:00 PM 4/12/99 -0400, Chuck Robey wrote: >On Mon, 12 Apr 1999, William S. Duncanson wrote: > >> I haven't been able to get a working SMP kernel out of -CURRENT recently. >> I don't know exactly when it broke, because I usually rebuild on a weekly >> basis. The kernel hangs after: >> APIC_IO: Testing 8254 interrupt delivery >> and doesn't ever come back (panic or otherwise). >> >> The one thing that I noticed is that on the older kernels, CPU#1 is >> launched after the APIC_IO Testing and Routing. On the newer kernels, >> CPU#1 is launched far earlier. >> >> Anybody have any ideas? > >Tell us how recent ... I built my last kernel on last Saturday, and it >works fine (freshly cvsupped sources). If yours is not more recent than >that, it might be your config or your hardware. > I tried late Saturday (4/10), Sunday (4/11) and today (4/12). The working kernel that I have is from 4/4. I'm using the same config as from the working kernel, and there doesn't appear to have been any relevant changes in LINT. I'm going to try blowing away my source tree completely and re-cvsupping, but... Does your CPU#1 launch right after the kernel loads, or does it wait until the "normal" time? William S. Duncanson caesar@starkreality.com The driving force behind the NC is the belief that the companies who brought us things like Unix, relational databases, and Windows can make an appliance that is inexpensive and easy to use if they choose to do that. -- Scott Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19990412202347.009bf790>