From owner-freebsd-smp Thu Jul 22 11:51:42 1999 Delivered-To: freebsd-smp@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 3D5A114BF8 for ; Thu, 22 Jul 1999 11:51:35 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id MAA10102; Thu, 22 Jul 1999 12:15:04 -0700 (MST) Received: from usr05.primenet.com(206.165.6.205) via SMTP by smtp04.primenet.com, id smtpd009968; Thu Jul 22 12:14:47 1999 Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id LAA10852; Thu, 22 Jul 1999 11:50:24 -0700 (MST) From: Terry Lambert Message-Id: <199907221850.LAA10852@usr05.primenet.com> Subject: Re: SMP + XDM = keyboard lockup To: nate@mt.sri.com (Nate Williams) Date: Thu, 22 Jul 1999 18:50:24 +0000 (GMT) Cc: tlambert@primenet.com, nate@mt.sri.com, scheper@beast.toad.net, freebsd-smp@FreeBSD.ORG In-Reply-To: <199907221845.MAA03196@mt.sri.com> from "Nate Williams" at Jul 22, 99 12:45:33 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 > > I believe the issue is the system is still starting up, and thus > > has the kernel poking at things. > > It shouldn't be. The kernel is completely done 'starting up', else all > the /etc/rc.* files wouldn't have been run and init wouldn't have > started spawning off gettys. I'm referring to things that result in a lot of I/O activity which are started in the rc files (NFS, DNS, sendmail, etc.). The system isn't quiescent until a while _after_ the rc files are run (long enough to log in). > > This jibes with his statement that manually starting the xdm from > > a root shell prompt on a relatively quiescent system "works". It > > is likely that it "works" only because there is not simultaneous > > activity. > > Or there is a a race in the video/keyboard driver that is causing > problems. X calls into the driver, so it's possible a missing spl() or > somesuch is causing problem. > > I doubt very much the problem is related to inb/outb, and is instead a > just a 'bug'. :) Maybe. I think we should hold off investing too much of ourselves into our respective theories until after he has done some of the tests I suggested. You should feel free to suggest tests, too, of course, since I could be wrong, no matter how "right" it feels to me. 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