Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Jul 1999 12:45:33 -0600
From:      Nate Williams <nate@mt.sri.com>
To:        Terry Lambert <tlambert@primenet.com>
Cc:        nate@mt.sri.com (Nate Williams), scheper@beast.toad.net, freebsd-smp@FreeBSD.ORG
Subject:   Re: SMP + XDM = keyboard lockup
Message-ID:  <199907221845.MAA03196@mt.sri.com>
In-Reply-To: <199907221839.LAA10550@usr05.primenet.com>
References:  <199907221812.MAA02907@mt.sri.com> <199907221839.LAA10550@usr05.primenet.com>

index | next in thread | previous in thread | raw e-mail

> > > 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.
> 
> Basically, user space code should keep its cold, wet nose out of
> the kernels crotch.
> 
> 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.

> You could guess that the init and the X server might be running
> on different CPU's, but then you would expect the /etc/ttys file
> based xdm startup to work.

Right.

> 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'. :)



Nate


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message



home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907221845.MAA03196>