From owner-freebsd-smp Fri Jul 23 16:44:52 1999 Delivered-To: freebsd-smp@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id DB46514F11 for ; Fri, 23 Jul 1999 16:44:50 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA28422; Fri, 23 Jul 1999 16:43:35 -0700 (PDT) (envelope-from dillon) Date: Fri, 23 Jul 1999 16:43:35 -0700 (PDT) From: Matthew Dillon Message-Id: <199907232343.QAA28422@apollo.backplane.com> To: Terry Lambert Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA), jedgar@fxp.org, freebsd-smp@FreeBSD.ORG Subject: Re: SMP + XDM = keyboard lockup References: <199907232321.QAA14822@usr09.primenet.com> Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org :3) Why does it only happen in SMP? : : : Terry Lambert : terry@lambert.org I'm sure the answer to #3 is simply that the startup order winds up being different w/SMP due to there being two cpu's. I've had the X/keyboard/getty problem occur on UP machines and, in fact one of my first UP machines had this race condition unknowingly and *never* had a failure, but the same configuration on a faster UP box a little later led to the getty winning the race and I spent a few hours scratching my head trying to figure out what was wrong with X :-) -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message