From owner-freebsd-current@FreeBSD.ORG Sun Dec 7 15:34:05 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 7165B16A4CE for ; Sun, 7 Dec 2003 15:34:05 -0800 (PST) Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04CB643FE5 for ; Sun, 7 Dec 2003 15:34:00 -0800 (PST) (envelope-from mark@markdnet.demon.co.uk) Received: from lizacnet.demon.co.uk ([80.177.208.105]) by anchor-post-30.mail.demon.net with esmtp (Exim 3.35 #1) id 1AT8PX-000HgX-0U; Sun, 07 Dec 2003 23:33:59 +0000 From: Mark Dixon To: Andrew Lankford Date: Sun, 7 Dec 2003 23:34:11 +0000 User-Agent: KMail/1.5.4 References: <20031207214736.75886.qmail@web40807.mail.yahoo.com> In-Reply-To: <20031207214736.75886.qmail@web40807.mail.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200312072334.24275.mark@markdnet.demon.co.uk> 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: Sun, 07 Dec 2003 23:34:05 -0000 =2D----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 t= o=20 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. I do get the occasional one now, but is more an annoyance than a problem. I= =20 found out that whe it does it, before the X display appears, the console do= es=20 not fall through to the login prompt, simply stopping somewhere after=20 starting gdm (possibly before inetd, which usually chucks out an error=20 message on my system because of a bad config file, which I don't remember=20 seeing when it hangs). It is usually possible to log in remotely with ssh when this happens as wel= l,=20 but I found that doing a kill -9 on gdm-binary seemed to cause the whole=20 system to lock up when it was in this state. Other than that, everything=20 works over ssh. These are just my observations of the problem - hope they could be useful t= o=20 someone who knows how this end of the boot sequence works. Mark =2D --=20 I apologise for my English - its my first language and i've spoke it all my= =20 life, but I still don't always make sense. =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/07j+LqgJ90OcaiARAsW4AKCzLLwAS3LXpsIJm2bJaj2Rv9CzQgCfR2xx 3yFg5oTw8OlfGl0JosqRtxU=3D =3DRb9g =2D----END PGP SIGNATURE-----