From owner-freebsd-smp Mon Apr 12 19:17:59 1999 Delivered-To: freebsd-smp@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 4E7FB14FDB for ; Mon, 12 Apr 1999 19:17:53 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id WAA14794; Mon, 12 Apr 1999 22:13:30 -0400 (EDT) Date: Mon, 12 Apr 1999 22:13:30 -0400 (EDT) From: Chuck Robey To: "William S. Duncanson" Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP broken in -CURRENT? In-Reply-To: <4.1.19990412202347.009bf790@imap.colltech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 12 Apr 1999, William S. Duncanson wrote: > 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? After the timecounter, and the pnp config data gets registered in from kernel.conf, then the IOApic gets checked, and the 2nd cpu fires up. If your data is that recent, I have nothing here to contradict you, my kernel is likely older. I'm building world now, but I won't have data tonight. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message