From owner-freebsd-smp Thu Jul 22 18:37:21 1999 Delivered-To: freebsd-smp@freebsd.org Received: from mercury.toad.net (mercury.toad.net [205.197.182.105]) by hub.freebsd.org (Postfix) with ESMTP id 97845156DA for ; Thu, 22 Jul 1999 18:36:53 -0700 (PDT) (envelope-from scheper@toad.net) Received: from toad.net (core10d30.dynamic-dialup.toad.net [209.150.114.30]) by mercury.toad.net (8.8.8/8.8.8) with ESMTP id VAA20936 for ; Thu, 22 Jul 1999 21:36:53 -0400 Message-ID: <3797C66E.B9382583@toad.net> Date: Thu, 22 Jul 1999 21:33:34 -0400 From: "Richard A. Scheper" X-Mailer: Mozilla 4.08 [en] (X11; I; FreeBSD 3.1-RELEASE i386) MIME-Version: 1.0 To: freebsd-smp@FreeBSD.ORG Subject: Re: SMP + XDM = keyboard lockup References: <199907221845.LAA10738@usr05.primenet.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It looks like your suspiscions are correct. After further attempts at starting xdm from a root seesion, it does in fact hang more often than not. Perhaps I was just "lucky" and it only worked with a quiet system. I'll try the ps test and see what I get -Rich Terry Lambert wrote: > > Wow! That's a lot to chew and mostly over my head, but a couple of > > questions.. > > > > If what you say is true, then wouldn't I have toruble running xdm even > > from a root login after the boot process is over? I don't. > > No, not if the system is relatively quiescent. > > As I told Nate, you should be able to easily test this by loading > the I/O system (preferrably *not* your disks) and bouncing the > console in and out of X using ctrl-alt-F1/[ctrl-]alt-F4. If it > locks up, the problem has been identified. > > > How could I delay the startup of one of the processors, as you suggest in > > your last point? > > There is a sysctl which controlls the startup of the auxillary > processors. If you were to delay starting the processors until > after X was running, you would be able to see if this were related > to the SMP code path differences if it still locks up without the > other processors running (I don't believe it will) or to an I/O > space conflict (It may lock up following the AP's starting up, > but it probably won't, since when you do the manual start, the > system will be relatively quiescent). > > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message