Date: 01 Sep 1997 18:54 EDT From: "Andrew Atrens" <atrens@nortel.ca> To: freebsd-hackers@FreeBSD.ORG Subject: Help! keyboard lockups - could be kernel bug ? Message-ID: <199709012257.PAA24747@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
Hi Folks, Last week I was happily running FreeBSD-2.2.2 on my Pentium system with an ASUS T2P4 motherboard ( has PCI 430HX chipset ). But unfortunately I got the upgrade itch, and moved up (?) to an ASUS TX97 ( has PCI 430TX chipset ). To make a long story short, 2.2.2 consistently locked up on boot - a real showstopper. After much trial and error I discovered the culprit to be AUTO_EOI_X kernel option(s). When I built a kernel without these options it booted and appeared (initially at least) to function properly. Then, occasionally I noticed that my xdm login window was dropping characters and locking up. Enough of that, so I downloaded the sources and built/installed the August 08 3.0-SNAP. Xdm login was still dropping characters, so I went out and got Xfree86-3.3.1 sources and rebuilt X. Xdm login was *still* dropping characters and occasionally locking up the keyboard, so I began to look at this symptom more closely. While the xdm login banner is displayed, I run an xlock -inroot -mode random process in the background. Depending on how graphics/cpu intensive the particular screen saver is, the lock up behaviour worsens. For example, the lock ups are worse when running xlock in `galaxy' mode. Furthermore, if I get past the xdm login window, xterms and rxvts in my session cause keyboard lockup when xlock is running `galaxy' in the root window. So here's the strange thing: IF I DON'T RUN XDM, and instead just use startx then the system behaves normally - no keyboard lockups regardless of how hard I pound X. So what the heck is going on? -- What do I try next ? Any help would be appreciated :) Andrew ( opinions are mine, not Nortels )
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709012257.PAA24747>