[TriLUG] Input lockup problem

Mike M linux-support at earthlink.net
Fri Jan 31 11:47:21 EST 2003


I am running vanilla Debian 3.0, KDE 2.2, and KDM.  This system locked its 
input twice since I built it in December last year.  Today, when it happened, 
I tried to telnet in but the box would not respond to a ping.

To regain control of the system I've been hitting the hardware reset.  Both 
times I've had to run fsck manually to clean up problems.

I found that /var/log/kdm.log gave some information that I don't know how to 
interpret..  I noticed that everytime X does its startup, the Generic Mouse 
configuration fails.  I've tried in the past to correct this problem, but 
I've had no success.

There is also a PEX Font file problem indicated.

Could the input lockups I am experiencing be related to the Generic Mouse 
problems reported in the logs below?

Most of the time the mouse behaves as expected.

I've been googling around for help but so far I haven't found the silver 
bullet.  Any help would be appreciated.

Thanks.

-- 

Lots of stuff follows.....


Excerpts from /var/log/kdm.log with my comments added between tags: 
<mycomment>...</mycomment>

%%%%%%%%%%%%%%%%%    Sample 1    %%%%%%%%%%%%%%%%

<mycomment>X being configured - BEGIN</mycomment>
(==) Log file: "/var/log/XFree86.0.log", Time: Thu Dec 26 23:44:48 2002
...
...
...
...
...
(==) TRIDENT(0): Silken mouse enabled
(**) TRIDENT(0): DPMS enabled
(WW) TRIDENT(0): Option "UseFBDev" is not used
PEXExtensionInit: Couldn't open default PEX font file  Roman_M
(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Configured Mouse: Protocol: "PS/2"
(**) Configured Mouse: Core Pointer
(==) Configured Mouse: Buttons: 3
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Generic Mouse: Protocol: "ImPS/2"
(**) Generic Mouse: always reports core events
(EE) xf86OpenSerial: Cannot open device /dev/input/mice
	No such file or directory.
(EE) Generic Mouse: cannot open input device
(EE) PreInit failed for input device "Generic Mouse"
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)

<mycomment> 
X being configured - END

BEGIN Problem indications?
</mycomment>

GE timeout
GE timeout
GE timeout
GE timeout
GE timeout
GE timeout
GE timeout
GE timeout
GE timeout
<mycomment>
long line of unprintable chars
</mycomment>
warning: process set to nice value 0 instead of -10 as requested
<mycomment>
Problem indications? - END

This is where I realized the system stopped taking input and hit the reset 
button.  Sent email on problem to list 
(http://www.trilug.org/pipermail/trilug/Week-of-Mon-20030113/013629.html).

A similar situation occurred today.  In the following excerpt you can see 
that the X session began on 1/29/2003.

%%%%%%%%%%%%%%%%%    Sample 2    %%%%%%%%%%%%%%%%

Other X sessions have been ommited for the sake of brevity - BEGIN
</mycomment>
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Jan 29 15:08:14 2003
...
...
...
...
...
(==) TRIDENT(0): Silken mouse enabled
(**) TRIDENT(0): DPMS enabled
(WW) TRIDENT(0): Option "UseFBDev" is not used
PEXExtensionInit: Couldn't open default PEX font file  Roman_M
(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Configured Mouse: Protocol: "PS/2"
(**) Configured Mouse: Core Pointer
(==) Configured Mouse: Buttons: 3
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(**) Generic Mouse: Protocol: "ImPS/2"
(**) Generic Mouse: always reports core events
(EE) xf86OpenSerial: Cannot open device /dev/input/mice
	No such file or directory.
(EE) Generic Mouse: cannot open input device
(EE) PreInit failed for input device "Generic Mouse"
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
<mycomment>
X being configured - END
Problem indications? - BEGIN
</mycomment>
(==) TRIDENT(0): Write-combining range (0xd5800000,0x400000)
(II) TRIDENT(0): Initializing int10
(II) TRIDENT(0): Primary V_BIOS segment is: 0xc000
(**) TRIDENT(0): DPMS enabled
PEXExtensionInit: Couldn't open default PEX font file  Roman_M
(==) TRIDENT(0): Write-combining range (0xd5800000,0x400000)
(II) TRIDENT(0): Initializing int10
(II) TRIDENT(0): Primary V_BIOS segment is: 0xc000
(**) TRIDENT(0): DPMS enabled
PEXExtensionInit: Couldn't open default PEX font file  Roman_M
(==) TRIDENT(0): Write-combining range (0xd5800000,0x400000)
(II) TRIDENT(0): Initializing int10
(II) TRIDENT(0): Primary V_BIOS segment is: 0xc000
(**) TRIDENT(0): DPMS enabled
PEXExtensionInit: Couldn't open default PEX font file  Roman_M
<mycomment>
long line of unprintable chars
</mycomment>
warning: process set to nice value 0 instead of -10 as requested


-- 
Mike M.



More information about the TriLUG mailing list