From owner-freebsd-smp Thu Jul 22 11:49: 8 1999 Delivered-To: freebsd-smp@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 8DDA814BF8 for ; Thu, 22 Jul 1999 11:49:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA01257; Thu, 22 Jul 1999 11:42:37 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907221842.LAA01257@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert Cc: nate@mt.sri.com (Nate Williams), scheper@beast.toad.net, freebsd-smp@FreeBSD.ORG Subject: Re: SMP + XDM = keyboard lockup In-reply-to: Your message of "Thu, 22 Jul 1999 18:39:10 -0000." <199907221839.LAA10550@usr05.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Jul 1999 11:42:37 -0700 From: Mike Smith Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > The xdm program, among other things, starts X. > > > > > > I believe the issue is one CPU running X doing inb/outb's while > > > the other CPU is in the kernel -- doing the same. > > > > Why would the other CPU doing the same inb/outb's as X? By the time > > init is run, the kernel is done 'setting up' the kernel. > > It wouldn't be. > > It would merely be trying to latch different addresses on the I/O > bus and/or write data to the previously latched address, at the > same time. This comment demonstrates that you're out of your depth. Back to the other end of the pool, and take your squeaky toys with you... (It doesn't work like that.) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message