From owner-freebsd-current@FreeBSD.ORG Mon Dec 8 12:24:51 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F12316A4CE for ; Mon, 8 Dec 2003 12:24:51 -0800 (PST) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D8AC43D41 for ; Mon, 8 Dec 2003 12:24:23 -0800 (PST) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 3C26C72DB5; Mon, 8 Dec 2003 12:24:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 39AA472DAD; Mon, 8 Dec 2003 12:24:23 -0800 (PST) Date: Mon, 8 Dec 2003 12:24:23 -0800 (PST) From: Doug White To: Mark Dixon In-Reply-To: <200312072334.24275.mark@markdnet.demon.co.uk> Message-ID: <20031208122223.L15361@carver.gumbysoft.com> References: <20031207214736.75886.qmail@web40807.mail.yahoo.com> <200312072334.24275.mark@markdnet.demon.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Andrew Lankford cc: freebsd-current@freebsd.org Subject: Re: keyboard lock-up. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 20:24:51 -0000 On Sun, 7 Dec 2003, Mark Dixon wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sunday 07 Dec 2003 21:47, Andrew Lankford wrote: > > On to another topic. Is anyone having trouble with > > keyboard lockups (every 3rd or 4th boot) in -CURRENT > > lately? I find that booteasy responds ok, but by the > > time xdm starts up, my keyboard doesn't respond to > > anything apart from the number lock key and the old > > "three finger salute". > > I've seen this recently as well - I use gdm. The only time I've been able to > reproduce it every time was when I had spamd (from spamcop) enabled in /usr/ > local/etc/rc.d - this led me to believe it was an rc problem. There is a known race between X and getty that's been around for ages. If X and getty on vty0 crank up simultaneously, syscons will drop the keyboard. The workaround is to insert a delay into your xdm startup so it jumps into X after vty0 has started. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org