From owner-freebsd-smp Thu Jul 22 11:46:37 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp03.primenet.com (smtp03.primenet.com [206.165.6.133]) by hub.freebsd.org (Postfix) with ESMTP id 4795814BF8 for ; Thu, 22 Jul 1999 11:46:34 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp03.primenet.com (8.8.8/8.8.8) id LAA23663; Thu, 22 Jul 1999 11:45:49 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp03.primenet.com, id smtpd023636; Thu Jul 22 11:45:44 1999 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA10738; Thu, 22 Jul 1999 11:45:41 -0700 (MST) From: Terry Lambert Message-Id: <199907221845.LAA10738@usr05.primenet.com> Subject: Re: SMP + XDM = keyboard lockup To: scheper@beast.toad.net (Richard Scheper) Date: Thu, 22 Jul 1999 18:45:41 +0000 (GMT) Cc: freebsd-smp@FreeBSD.ORG In-Reply-To: from "Richard Scheper" at Jul 22, 99 02:17:07 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 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